Borrowed FCC Grants and the Grantee Who Owns Them

Custody

Federal Communications Commission equipment authorizations tie a radio frequency device to a specific grantee code issued to a single legal entity. That three- or five-character alphanumeric prefix sits at the root of every regulatory record in the Commission Registration System. When a hardware team integrates an off-the-shelf wireless module into a host product, commercial documentation usually talks about using the vendor’s certified radio.

Legally, though, the host manufacturer doesn’t hold that authorization. The original component vendor retains full ownership of the Grant of Equipment Authorization issued under Title 47 of the Code of Federal Regulations Part 2. The host integrator is simply a downstream user of someone else’s regulatory asset.

The difference between holding an equipment authorization and operating under an existing modular grant marks the real boundary of commercial risk. The Grantee of Record listed in the FCC database carries sole responsibility for initial certification test data, periodic factory audits, and the transmitter design’s ongoing compliance. A host manufacturer drop-in integrating a pre-certified radio module onto their printed circuit board relies entirely on the grantee keeping that filing current.

Grant ownership dictates regulatory authority. If the module vendor misses annual FCC administrative fees, ignores inquiry notices from a Telecommunication Certification Body, or goes through corporate dissolution, the underlying grant can be suspended. Downstream manufacturers relying on that radio identifier lose market authorization overnight, with no direct recourse to the agency.

Modular approvals operate under 47 CFR Section 15.212 alongside detailed guidance in Office of Engineering and Technology Knowledge Database Publication 996369. Achieving Full Modular Approval requires satisfying eight physical and technical conditions during initial laboratory evaluation.

The eight criteria in 15.212 dictate how completely the transmitter circuit isolates itself from surrounding hardware. First, the radio needs its own RF shielding to stop coupling between host digital traces and the module synthesis loop. The transmitter must use buffered modulation and data inputs so invalid host logic levels can’t cause over-modulation.

Internal power supply regulation on the board isolates radio performance from host voltage swings. Antenna connections must follow unique coupling standards or rely on a permanent trace, and laboratory testing takes place in a standalone configuration extended away from test jigs. Finally, the module housing must carry a permanent label showing its identifier, the vendor must supply explicit installation instructions covering operational limits, and the transmitter must satisfy RF exposure limits for its deployment class.

Grantee Code Mechanics and Authorization Boundaries

To get an initial grantee code, a corporate entity registers its legal representation, physical headquarters address, and executive contact details with the Commission. This creates a permanent administrative link between the prefix and the legal entity. When a vendor markets an integrated circuit assembly under an FCC ID like 2AB3C-MODULE1, the characters before the hyphen mark the grantee code owner, while those after it represent the product code assigned by that grantee.

Host manufacturers often mistake buying a radio component for buying regulatory rights. Purchasing ten thousand wireless microcontrollers gives title to physical silicon, but zero rights over the underlying equipment authorization dossier. The supplier hands over a datasheet and integration manual, while legal authority to submit technical modifications remains firmly in their hands.

The host company cannot update the filing, add new antenna configurations to the grant, or alter maximum radiated output power. Any technical change requiring regulatory review relies completely on the component vendor agreeing to file with an accredited certification body.

A host manufacturer relying on a supplier’s modular filing assumes full market exposure for physical enclosure shielding while holding zero legal authority to alter certified radio firmware parameters.

Limited Modular Approval scenarios bring extra constraints. If a radio module misses any of the eight standard requirements ~ like lacking onboard power regulation or an integrated RF shield ~ the testing laboratory issues a limited grant instead. The grantee code owner must then restrict installation to specific host configurations or evaluate every host enclosure individually.

Under an LMA, using the grant requires the module vendor to review host test reports and issue formal approval letters for each host product iteration. That leaves the host manufacturer tied to the vendor’s engineering team even for routine mechanical updates.

Integration Scenarios across OEM Module Sourcing

Integrating third-party radio hardware into an end device generally follows one of three paths. The first is direct modular integration, where the host packaging simply states that the unit contains a certified transmitter module. The host team runs Part 15 Subpart B verification testing for unintentional digital emissions, compiles a Supplier’s Declaration of Conformity dossier, and ships.

This route keeps upfront certification costs low, but leaves the product entirely exposed to the health of the vendor’s grant.

The second option uses a Change in Identification filing under 47 CFR Section 2.933. This administrative process lets a host manufacturer establish its own FCC ID based entirely on the supplier’s original test data. The host applies for a grantee code, gets a formal Grantee Permission Letter from the module vendor, and submits an administrative filing to a Telecommunication Certification Body.

The resulting child grant carries the host company’s grantee code, making the radio look internally owned to the market. Underlying schematics, technical baselines, and primary test reports remain tied to the parent grant in the federal database.

The third path bypasses borrowed grants altogether by filing a standalone equipment authorization under the host’s own grantee code. Engineering puts the module silicon or reference layout straight onto the main motherboard and books time in a semi-anechoic chamber. The company then submits complete schematics, bills of materials, block diagrams, operational descriptions, and radiated spurious emission reports directly to the certification body.

It takes significant upfront capital and stretches the launch schedule, but yields total legal ownership and control over the certification dossier.

Transfer Protocols and Change in Identification

Executing a 2.933 Change in Identification takes tight alignment between legal agreements and regulatory filings. It starts when the original grant owner signs a Grantee Permission Letter on corporate letterhead. This letter explicitly authorizes the Federal Communications Commission and the certification body to reference original test data on file for the parent FCC ID, confirming that hardware under the new identifier remains electrically identical to the certified design, with zero structural or firmware changes.

Filings submitted under Section 2.933 need external photos of the rebranded device, clear artwork of the new label showing the child FCC ID, and an updated operational description if marketing language changes. The certification body checks that the parent grant is active, unrevoked, and clear of outstanding surveillance actions before issuing a new Grant of Equipment Authorization with the child identifier.

Child grants created this way retain a permanent dependency on the parent filing. If the original module vendor loses its grantee registration through administrative default, every child grant tied to that parent comes under immediate review. Likewise, if the parent grantee tweaked firmware parameters in production silicon without filing permissive changes, invalidation at the parent level flows straight down to the child grant.

Host teams often assume a 2.933 filing insulates their product from vendor regulatory stumbles, only to find an administrative issue at the parent level stopping customs clearance overnight.

When trace layout changes caused out-of-band emissions to spike during host evaluation, the radio vendor asserted that host housing geometry falls outside their technical support obligations and advised lowering transmitter output power independently.

Lock

Relying on an external grantee code introduces a major structural vulnerability across a product’s lifecycle. When engineering puts a borrowed wireless module inside a host enclosure, hardware or layout changes during mass production often trigger regulatory update requirements. Under federal rules, only the Grantee of Record has standing to submit permissive change applications to a Telecommunication Certification Body.

If integration calls for a Class II Permissive Change because of antenna gain differences or proximity to the human body, the host manufacturer can’t file on its own. The launch timeline stays stuck until the module vendor agrees to review host chamber data and process the submission under their grantee code.

Modifications to certified radio hardware or host operating conditions fall under rules defined in 47 CFR Section 2.932 and Office of Engineering and Technology Knowledge Database Publication 178919. Class I Permissive Changes cover physical or layout tweaks that keep RF characteristics, occupied bandwidth, and radiated spurious emissions strictly within original granted limits. A Class I change requires no formal filing with the agency, though the grantee must keep internal engineering data proving baseline performance.

Class II Permissive Changes apply when circuit modifications, swapped components, or enclosure interactions degrade RF performance or increase emissions while remaining within statutory caps. A Class II filing requires accredited lab data, formal forms, and certification body review before updated units can ship.

Host manufacturers operating under a 2.933 Change in Identification run into real operational hurdles when Class II updates come up. Even though the child grant displays the host company’s identifier, Office of Engineering and Technology rules require hardware modifications on the underlying module circuit to be handled by the parent grantee. The child grant holder can’t submit Class II Permissive Changes for hardware adjustments made by the primary radio vendor.

If that vendor updates silicon steppings or changes passive component suppliers on the module board, the parent grantee has to file a Class II update on the baseline grant before the child grant holder can legally sell updated inventory.

Host Integration Boundaries and Permissive Change Triggers

Dropping a certified radio module into an end-product enclosure changes its radiated electromagnetic profile. Metal traces, structural ribs, battery packs, and ground planes inside the housing distort antenna patterns. If engineering picks a custom patch antenna with higher peak directional gain than the reference dipoles on the module’s original grant sheet, radiated power can easily exceed approved limits.

That invalidates the modular grant scope, and the company can’t ship finished units until a Class II Permissive Change covers the new antenna in official records.

RF exposure rules are another frequent trigger for permissive changes during host development. Modular grants often restrict deployment to mobile applications where the antenna stays more than 20 centimeters from the human body. The moment engineering puts that module into a handheld terminal or wearable device, the product moves into the portable exposure category governed by 47 CFR Section 2.1093.

At 5.8 GHz radiating through a 4 dBi patch antenna, a 1.5 dB attenuation shift across a modified trace drops the compliance margin below the 3 dB laboratory threshold.

Portable use rules out simple Maximum Permissible Exposure calculations, forcing physical Specific Absorption Rate testing with an accredited tissue phantom setup. If the original modular grant doesn’t include portable SAR test data covering the host’s specific mechanical shape, the host team can’t ship under that grant. The original grantee has to submit a Class II filing with the host SAR report ~ or the host team must give up on the borrowed grant and file for independent standalone certification under its own code.

What Happens When a Module Vendor Revokes Authorization?

Relationships between host integrators and module suppliers break down for plenty of reasons ~ market competition, corporate acquisitions, or product obsolescence. A supplier might end-of-life a module line and decline to spend money maintaining regulatory filings. A vendor in financial trouble might let its registration in the Commission database lapse.

Or, in severe commercial disputes, a vendor can send formal written notice to the certification body revoking the Grantee Permission Letter previously issued to an integrator.

Revoking grantee permission pulls the rug out from under a child 2.933 grant. Once notified that authorization has been rescinded by the parent grantee, the certification body updates its records, leaving the child grant invalid for imports. Shipments arriving at ports face immediate entry denial under international trade enforcement rules.

Customs stops uncertified goods, leaving the host manufacturer holding assembled inventory that can’t be legally sold or transferred.

Fixing a revoked authorization forces an immediate change in strategy. Production using the borrowed identifier must stop right away while the host company starts an independent authorization campaign. Engineering has to pull together a full standalone filing under its own grantee code, submit host units to an accredited chamber for full testing, and pay primary filing fees.

Getting a standalone certification takes anywhere from four to ten weeks depending on chamber availability, causing costly supply disruptions in the interim.

Contractual Safeguards for Grant Ownership Maintenance

Protecting launch schedules means putting explicit regulatory covenants into component supply agreements before buying hardware. Standard purchase orders cover unit prices and delivery schedules, but completely ignore grant maintenance. A solid agreement obligates the module vendor to keep its grantee registration in good standing with the Federal Communications Commission throughout the host product’s commercial lifespan.

Supply contracts need to explicitly spell out Class II Permissive Change workflows and fees. The agreement should mandate that the vendor review host chamber data and submit Class II filings within a set window ~ say, thirty calendar days from receiving lab test dossiers. It should also cap administrative handling fees and require the vendor to keep complete schematics, block diagrams, and operational descriptions in secure escrow accessible to certified testing labs.

Contracts also need clear remedies for unexpected component end-of-life decisions or corporate dissolution. The agreement should require at least twelve months’ advance written notice before a supplier terminates regulatory support for a certified module. Terms ought to compel the vendor to grant unrestricted permission for the host manufacturer to run independent standalone filings using original module schematics if the vendor goes under or discontinues the line.

Section 8.4 of the supply agreement mandates that the component vendor must execute a Class II Permissive Change within forty-five calendar days of receiving host laboratory radiated spurious emission test data, transferring all regulatory filing costs to the host manufacturer.

Paperwork

Verifying technical paperwork submitted to the FCC Equipment Authorization System takes careful cross-checking of original lab reports against physical host hardware. Integrators often accept supplier compliance statements without looking at the underlying test reports in the federal database. A module datasheet showing an FCC ID doesn’t mean the original lab evaluation covers the host’s exact operating parameters, antenna structures, or simultaneous transmission modes.

Auditing the primary filing dossier is the primary defense against non-compliance liability.

Reviewing a borrowed certification starts by opening the Office of Engineering and Technology portal and pulling up the original Form 731 application and its attached exhibits. Inspecting the original test report, schematics, block diagrams, operational descriptions, and grant condition notes is essential. Notes on the face of the authorization set explicit operational boundaries ~ restricting installation to certain duty cycles, capping antenna gain, or mandating minimum separation distances that directly constrain host design options.

Host integration teams have to evaluate radiated spurious emissions when a radio module operates inside an enclosure next to host digital processing hardware. Knowledge Database Publication 996369 D04 offers specific guidance here. The host manufacturer is responsible for proving that digital clocks, memory interfaces, display drivers, and power converters inside the assembly don’t interact with the integrated radio to produce non-compliant spurious radiation.

The failure modes listed below reflect technical oversights observed when host engineering teams integrate third-party certified radio hardware without verifying physical operating boundaries.

• Exceeded Antenna Peak Gain drops compliance when the host patch antenna delivers 5 dBi while the original grant caps maximum gain at 2.1 dBi.
• Unchecked Enclosure Resonances create harmonic radiated spikes in metal-trimmed plastic housings that exceed Part 15 Class B limits.
• Invalidated SAR Exclusions occur when a host shifts product mounting geometry below the 20-centimeter mobile threshold without executing a Class II update.
• Uncoordinated Multi-Transmitter Operation generates intermodulation distortion products in the 2.4 GHz industrial band when Wi-Fi and Bluetooth burst simultaneously.

Unintentional coupling between host digital buses and the embedded module antenna is a primary cause of host evaluation failures. High-speed switching signals on host PCB traces emit high-frequency noise. If the module antenna sits near unshielded memory traces or switching power converters, that digital noise corrupts radio reception and radiates out-of-band emissions through enclosure seams.

Catching this requires chamber testing across the full operating frequency range, up to the tenth harmonic of the highest fundamental frequency in the host system.

Technical Audit of OEM Test Evidence

Auditing a supplier’s certification dossier means checking the technical methodology used by the original testing lab. The host team needs to verify that testing followed current American National Standards Institute standards ~ specifically ANSI C63.10 for unlicensed wireless devices and ANSI C63.26 for licensed digital cellular transmitters. The report should clearly state measurement detector types, resolution bandwidth settings, antenna polarization angles, and calibrated frequency ranges.

Conducted output power figures in the primary report should be cross-checked against host firmware power tables. Vendors sometimes run initial modular certification at maximum silicon power under ideal thermal conditions in the lab. In real production, heat buildup inside a sealed host housing can force firmware to throttle transmitter power ~ or uncalibrated software might accidentally request power levels beyond granted parameters.

Operating above granted levels invalidates certification instantly, while running below granted limits reduces wireless range without violating regulatory ceilings.

The operational verification steps detailed below outline the sequential procedure host compliance engineers execute when validating borrowed modular test reports against host product requirements.

1. Download full grant notes and test reports from the FCC OET Equipment Authorization Search database using the module FCC ID.
2. Compare maximum conducted power levels and modulation modes in the report against host firmware settings.
3. Measure host board trace impedances and confirm matched 50-ohm microstrip geometry against the module reference layout design.
4. Execute radiated spurious emissions scans across all operational frequency bands in an accredited semi-anechoic chamber.
5. Document co-location compliance calculations using KDB 447498 formulas before signing the host Supplier’s Declaration of Conformity.

Documentation reviews should also audit frequency stability data across temperatures from negative twenty to positive fifty degrees Celsius, and supply voltage swings from eighty-five to one hundred and fifteen percent of nominal ratings. If the module relies on host voltage regulation rather than internal regulators, engineering must prove that host power delivery holds rail voltages stable within tolerances specified in the original modular filing.

Radiated Emissions and Co-Location Assessment

Co-location challenges arise when a host product puts multiple active transmitters inside a compact enclosure. A typical industrial build might pack a cellular modem, a Wi-Fi access transceiver, and a Bluetooth Low Energy radio into one housing. Operating these concurrently generates intermodulation products from non-linear mixing of fundamental carrier frequencies.

Under KDB 996369 D04 section 3.2, host manufacturers who integrate certified modular transmitters remain legally obligated to perform verification testing for radiated emissions across combined active radio modes.

Evaluating multi-transmitter RF exposure compliance involves calculating cumulative exposure ratios defined in Knowledge Database Publication 447498. The sum of individual transmitter power density ratios relative to their limits must stay at or below 1.0. If the combined ratio exceeds unity, mathematical exclusion fails, and the assembly must undergo physical SAR testing or RF exposure chamber measurement under simultaneous transmission conditions.

Radiated spurious emission scans for co-located transmitters require chamber testing with all active radios firing simultaneously at maximum output power across worst-case channels. Operators monitor intermodulation frequencies calculated from combinations of fundamental signals. If intermodulation products exceed general field strength limits in Part 15.209, the host fails.

Fixing this usually means modifying ground shielding, adding microstrip notch filters, or using software transmission blanking to prevent concurrent channel activity.

Verification Sequence for Borrowed Test Dossiers

Verifying third-party compliance evidence requires building a traceable laboratory record before commercial launch. The host team compiles a master technical construction file containing the module grant, original test reports, host schematics, PCB layout layers, and internal measurement logs. This folder proves due diligence if a post-market regulatory inquiry ever occurs.

Auditing the physical trace layout is a critical step in the verification sequence. Modular grants specifying external antenna connectors or microstrip trace connections include detailed reference layout drawings in the integration manual. The PCB trace connecting the module pin to the host antenna connector must match the reference design’s characteristic impedance, trace width, substrate dielectric constant, and ground clearance gap.

Deviating from that trace geometry turns the host board layout into an uncertified radiating element, invalidating the grant.

The final phase of the paperwork audit verifies labeling across all product levels. The host exterior must carry a permanent label stating that the device contains a certified transmitter module identified by the parent or child FCC ID. If the host features an electronic display, user interface software can follow e-labeling guidance in KDB 784748, provided users can access regulatory information in three steps without special access codes.

Uncovering an unfiled firmware modification in a supplier’s cellular module forced $14,200 in emergency semi-anechoic chamber re-testing while 8,000 finished host devices remained held at the customs port.

Audit

Market surveillance by Telecommunication Certification Bodies and regulatory inspectors carries ongoing commercial risk. Certification bodies accredited by the FCC must perform post-market surveillance on a minimum percentage of all granted authorizations each calendar year ~ covering both direct standalone certifications and modular approvals. When a certification body selects a radio module for random compliance auditing, the Grantee of Record gets formal notice to supply production samples, complete schematics, and test software within a tight window.

Surveillance audits often expose friction between component vendors and downstream integrators. If a module vendor receives an audit request for a component built into thousands of active host products, it must supply fully functional units configured for lab testing. If the vendor fails to respond or submits sample units that fail radiated emissions tests because of underlying silicon revisions, the certification body begins suspension proceedings.

Invalidate the parent grant, and every host product relying on that modular authorization loses its standing overnight.

Customs enforcement mechanisms cross-reference federal registration databases during entry inspections. Port inspectors use automated tracking systems to match imported product labels against active database records. If a shipment carries an FCC ID tied to a revoked, suspended, or administratively invalid grant, customs officers seize the goods at the port of entry.

The importer then faces steep demurrage charges, potential administrative fines, and destruction of non-compliant inventory.

Post-Market Surveillance and Regulatory Inspection Controls

Surveillance testing by accredited laboratories evaluates sample units against current technical standards rather than rules in effect when the original filing occurred. If standards change during a product’s production run, post-market audits apply the updated criteria. Devices that fail to satisfy newer harmonic suppression or out-of-band emission limits face immediate regulatory scrutiny.

Host manufacturers face real liability if post-market surveillance uncovers unapproved internal modifications. Altering component placement, thinning enclosure shielding, or swapping discrete filtering components without host re-verification puts the device in violation of federal marketing rules. The agency can issue formal Warning Letters, demand public product recalls, and levy civil monetary penalties against distributors under Title 47 of the United States Code Section 503.

The strategic criteria presented in the decision checklist below guide engineering executives in determining when to transition from borrowed modular grants to independent standalone certification.

• Annual Unit Volume Thresholds justify independent standalone certification fees when host production projections cross 25,000 units per year.
• Custom Antenna Geometry Needs dictate owning the primary filing whenever host packaging constraints preclude using standard off-the-shelf reference antennas.
• Long-Term Firmware Ownership requires complete control over the grantee code to allow continuous in-house radio software updates without vendor dependency.
• Multi-Market Release Schedules benefit from unified international filing dossiers compiled under a single corporate brand identity.

Surveillance testing quickly catches unfiled layout shifts. Establishing an internal compliance tracking system protects organizations from unexpected audit failures. Engineering teams should conduct periodic audits of production units, checking that physical component layouts, RF shield soldering, and host firmware power tables match approved laboratory baselines.

Transition Planning for Independent Equipment Authorization

Moving a mature product line from a borrowed modular grant to an internally owned equipment authorization takes structured project execution. Hardware teams start by securing full schematics, bills of materials, and board stackup files from the radio supplier. If the vendor considers schematics proprietary trade secrets, it must submit those exhibit files directly to the certification body under formal confidentiality requests pursuant to 47 CFR Sections 0.457 and 0.459.

The host team registers for an independent grantee code through the Commission Registration System and pays the standard fee. Engineering then books chamber time at an accredited testing lab for a complete standalone test suite. The lab evaluates conducted output power, occupied bandwidth, band-edge emissions, radiated spurious emissions, and RF exposure limits with the radio module mounted directly inside the final host enclosure.

Owning the grantee code eliminates supply chain vulnerability by giving the product manufacturer complete legal authority to submit permissive changes.

Once passing test reports come back from the lab, the host company submits a formal application for Equipment Authorization to a Telecommunication Certification Body under its new grantee code. The certification body reviews the exhibit package, verifies compliance with statutory rules, and issues a fresh Grant of Equipment Authorization. Production then updates exterior product labels, packaging artwork, and manuals to display the new FCC ID.

Direct ownership of the equipment authorization dossier gives complete operational autonomy over the product lifecycle. The host manufacturer can execute Class I and Class II Permissive Changes independently, modify firmware power parameters within statutory limits, integrate alternative antenna structures, and respond directly to regulatory surveillance inquiries without third-party vendor intermediation.

When host packaging dictates a custom PCB trace antenna, acquiring an independent grantee code and executing a standalone certification yields lower total regulatory risk than attempting to negotiate permissive change filings through a third-party module vendor.