FCC Permissive Changes: When You Can Modify a Certified Product

TL;DR -- After your product gets an FCC grant, modifications don't automatically require full recertification. 47 CFR Section 2.1043 defines three classes of "permissive changes" that let you modify a certified device without obtaining a new FCC ID. But the boundaries are strict: change the wrong thing and you're looking at a new application, new test reports, and 8 to 16 weeks of delay. Only the grant holder (grantee) can make permissive changes.

What permissive changes are

You've spent $5,000 to $15,000 and 8 to 16 weeks getting your device through FCC certification. Now you need to swap an antenna, update firmware, or redesign the enclosure. Do you start the whole process over?

Usually, no. The FCC's permissive change rules (47 CFR Section 2.1043, elaborated in KDB Publication 178919 D01) create a framework for modifying certified equipment without obtaining a new FCC ID. The framework defines three classes of changes, plus a fourth category -- changes so significant they require starting from scratch.

The logic is straightforward: the FCC cares about RF performance. If your change doesn't affect RF behavior, you're fine. If it degrades RF performance but stays within limits, you file paperwork. If it pushes the device outside its certified operating parameters, you start over with a new certification.

The decision framework

Work through these in order and stop at the first match.

flowchart TD
    A["Proposed modification\nto certified device"] --> B{"Does it change basic frequency\ncircuitry, modulation stages, or\nincrease max power/field strength?"}
    B -->|Yes| C["New FCC ID Required\nFull recertification"]
    B -->|No| D{"Is this an SDR and does the\nsoftware change alter frequency range,\nmodulation, or max power outside\napproved parameters?"}
    D -->|Yes| E["Class III\nFile + await FCC acknowledgment\nbefore shipping"]
    D -->|No| F{"Does the change degrade any\npreviously reported performance\ncharacteristic?"}
    F -->|Yes| G["Class II\nFile with Commission\nFCC ID unchanged"]
    F -->|No| H{"Does it affect any reported\ncharacteristic at all?"}
    H -->|Yes, but improved or unchanged| I["Class I\nNo filing required"]
    H -->|No RF impact| J["No Action Needed"]
    style C fill:#7f1d1d,color:#fff
    style E fill:#92400e,color:#fff
    style G fill:#1e3a5f,color:#fff
    style I fill:#14532d,color:#fff
    style J fill:#14532d,color:#fff

Class I permissive change: no filing required

A Class I change is any modification that does not degrade the characteristics reported to the Commission at the time of certification. RF performance stays the same or improves relative to what was originally reported.

Typical Class I scenarios:

• Cosmetic enclosure redesign (new color, shape, material) with no measurable effect on RF emissions
• Updated labeling or user manual text
• Firmware updates with zero effect on RF emissions -- bug fixes, UI changes, security patches unrelated to radio operation
• Substituting an equivalent antenna of the same type and gain

No paperwork. No filing. No cost beyond your own internal verification that the change genuinely doesn't degrade RF performance. But there's a catch: only the grantee (the company whose name is on the FCC grant) can make a Class I change. If you're an OEM customer who had someone else certify the device, you cannot unilaterally make even a Class I change. You must coordinate with the grantee or obtain your own authorization.

Class II permissive change: file with the Commission

A Class II change is a modification that degrades a previously reported performance characteristic, but the degraded performance still meets the minimum applicable rule requirements. Because you're filing worse numbers than what's on the grant, the Commission needs to verify the device still complies.

What you file:

1. Complete test results for all affected characteristics (not the full test suite -- only what changed)
2. A signed certification that the equipment is not prohibited from receiving authorization (Section 2.903)
3. An affirmative or negative statement about whether the applicant appears on the FCC Covered List

The FCC ID does not change. You keep your existing grant. The cost is dramatically lower than full recertification because you're only retesting the characteristics that changed.

Typical Class II scenarios:

• Adding a new antenna type or a higher-gain antenna (Section 15.203 requirements apply)
• Hardware changes that alter spurious emission levels while remaining within limits
• Output power reductions below the originally certified level (counterintuitively, this is still a Class II because the reported power value changes)
• Enclosure changes that measurably affect RF shielding or emissions but remain within regulatory limits

Class III permissive change: SDR software modifications

Class III was introduced specifically for software defined radios -- transmitters where software controls the operating parameters. A Class III change is any software modification to an SDR that:

• Changes the frequency range outside previously approved parameters
• Changes the modulation type outside previously approved parameters
• Changes maximum output power (conducted or radiated) outside previously approved parameters
• Changes the circumstances under which the transmitter operates in compliance with the rules

Here's what separates Class III from Class II: the modified software must not be loaded into equipment and the equipment must not be marketed under the existing grant until the Commission acknowledges the change. File-and-wait, not file-and-proceed.

This matters for release planning. You cannot ship firmware updates that fall under Class III until the FCC gives the green light. That means 2 to 4 additional weeks on top of the filing itself, and there's no way to expedite it.

What you file:

• A description of the software changes
• Test results demonstrating compliance with all applicable rules under the new software, including RF exposure (SAR/MPE)

When you need a new FCC ID

None of the permissive change classes cover these. A new FCC ID -- new application, new test reports, new grant -- is mandatory when:

• Frequency-determining circuitry changes -- modifications to the basic frequency determining and stabilizing circuitry (including clock and data rates) or frequency multiplication stages
• Basic modulator circuit changes -- changes to the fundamental modulation architecture
• Maximum power or field strength increases -- any increase in the maximum conducted output power or maximum radiated power listed on the existing grant
• Change in device identification -- any modification that results in a change to the device ID

No shortcuts. You're filing through a TCB with the full package: test reports, photos, block diagrams, operational descriptions, user manuals.

Firmware updates: the question everyone asks

This is the question hardware engineers ask most often, and the answer is annoying: it depends on what the firmware touches.

Firmware that requires no filing at all

Software changes that do not affect radio frequency emissions require no filing and can be made by parties other than the grantee:

• Security patches fixing application-layer vulnerabilities
• UI or feature changes in the host processor
• Protocol stack updates that don't alter RF parameters (updating TLS version, not radio duty cycle)
• Bluetooth application profile fixes that don't touch the radio layer

The FCC's 2015 blog post "Clearing the Air on Wi-Fi Software Updates" confirmed this explicitly: ordinary security and feature updates to WiFi devices do not require recertification. But this is not a blanket firmware exemption. It only applies when the firmware has no effect on RF behavior.

Firmware that triggers a permissive change review

Any software change that could alter the following requires at minimum a Class II or Class III evaluation:

• Transmit power levels
• Channel selection or frequency range
• Duty cycle or dwell time (especially in frequency-hopping systems)
• Spurious or out-of-band emission behavior
• Security protections that gate which radio configurations are accessible

SDR firmware: the strictest rules

For any device certified as an SDR, firmware changes touching radio operation are Class III permissive changes. The manufacturer must file with the Commission and cannot ship the updated firmware until the Commission acknowledges the change. This has real implications for release cadence -- you can't push OTA radio firmware updates the way you push application updates.

The TP-Link precedent

When the FCC tightened rules requiring WiFi routers to prevent third-party firmware from unlocking higher transmit power or additional channels (2015-2016), TP-Link responded by locking the radio configuration partition on consumer routers. This prevented open-source firmware (DD-WRT, OpenWrt) from modifying RF parameters. It's a concrete example of a manufacturer implementing technical controls to prevent end-users from making unauthorized changes that would put the manufacturer in violation.

Quick reference: common modifications classified

Cost and timeline comparison

Classifying your change correctly can save you tens of thousands of dollars. These are approximate industry norms -- actual costs vary by product complexity, band count, and lab queue times.

The cost gap between Class II and full recertification comes down to scope: Class II only requires retesting the affected characteristics, not the entire device. Class III adds a waiting period for Commission acknowledgment on top of testing -- not a rubber stamp, so budget 2 to 4 extra weeks. Full recertification through a TCB averages 8 to 12 weeks at standard priority; rush processing (1 to 2 weeks) is available but roughly doubles the lab fee. And the FCC application fee for a new grant is separate from TCB fees.

The grantee-only rule

This trips people up regularly. All three classes of permissive change -- Class I, II, and III -- may only be made by the holder of the grant of certification. Not the manufacturer. Not the ODM customer who licensed the design. The grantee, period. You cannot independently make even a Class I change if your name isn't on the grant.

If you contracted with a manufacturer to certify a product under their FCC ID, and you now want to modify it, you have two options:

1. Coordinate with the grantee to make the change under their grant
2. Obtain your own FCC certification (new FCC ID, full cost)

This is one reason why owning your FCC grant matters for long-term product control, even when using a contract manufacturer.

Common misconceptions

"If I only change software, I never need to refile." False. Software changes that alter RF parameters -- power, frequency, modulation, or spurious emissions -- require a permissive change filing at minimum, and a Class III hold-and-wait if the device is an SDR.

"Reducing power is always safe -- it's a minor change." Not necessarily. A power reduction changes the values reported on the grant. Depending on the magnitude and what other characteristics are affected, it's a Class II permissive change requiring a filing with test results.

"A permissive change lets me change the FCC ID." No. By definition, none of the three classes of permissive change result in a new FCC ID. If the change is significant enough to need a new ID, you need a new application.

"The enclosure is just plastic, it can't affect the FCC certification." Enclosure changes can affect antenna radiation patterns, RF shielding, SAR proximity assumptions, and spurious emission levels. Significant enclosure redesigns warrant at least a Class I review and may rise to Class II.

"I can make these changes myself since I'm the manufacturer." Only if you are the holder of the original grant. If someone else certified the device under their FCC ID, you need their involvement or your own certification.

Enforcement: what happens when you get it wrong

The FCC does enforce this, and the fines are not small.

HobbyKing ($2.86M fine, 2020-2021): The FCC fined HobbyKing $2,861,128 for marketing 65 models of drone AV transmitters that transmitted in unauthorized radio frequency bands, some at excessive power levels. None had FCC certification.

Sound Around ($1.2M proposed fine, 2023): The FCC proposed a $1.2 million fine for repeatedly marketing noncompliant RF devices.

Inter Tech (unauthorized re-branding): Inter Tech combined certified exciters and amplifiers and marketed them under its own trade name without authorization from the original certification grantee. The FCC treated this re-branding as a "modification," making Inter Tech the responsible party.

Civil forfeiture can reach $20,731 per day per device under 47 U.S.C. Section 502. The FCC can also require product recalls and mandatory compliance programs.

The pattern: marketing uncertified devices, shipping devices modified beyond the scope of the grant, importing equipment certified only for other markets, and re-branding without grantee authorization.

KDB 178919: the authoritative guidance

KDB Publication 178919 D01 (Permissive Change Policy) is the FCC's own guidance on Section 2.1043, and it's what any TCB or compliance engineer will pull up when evaluating your proposed change. It walks through the three classes with worked examples, clarifies the grantee-only rule, covers module-specific permissive change rules, and addresses antenna substitutions under Section 15.203.

A companion document, KDB 178919 D02 (Permissive Change FAQ), answers specific edge-case questions. Both are publicly accessible through the FCC's KDB search tool at apps.fcc.gov/oetcf/kdb.

For module integrators, KDB 996369 governs how host manufacturers can use certified modules and what modifications to the host product do and do not affect the module's existing certification.

Related guides

• FCC Certification Hub -- the full authorization process from classification through grant issuance
• FCC Module Certification -- modular approval under 15.212, where permissive change rules intersect with module grants
• FCC Part 15 Guide -- how Part 15 classifies your device and determines authorization path
• SDoC vs Certification -- choosing between the two authorization paths
• FCC Certification Cost -- full cost breakdown including permissive change filing costs
• FCC Label Requirements -- labeling obligations that survive permissive changes

Key regulatory references

• 47 CFR Section 2.1043 -- Changes in certificated equipment (the regulation itself)
• KDB Publication 178919 D01 -- Permissive Change Policy (detailed FCC guidance)
• KDB Publication 178919 D02 -- Permissive Change FAQ
• KDB 996369 -- Modular certification guidance (relevant for module-level permissive changes)
• FCC Blog: Clearing the Air on Wi-Fi Software Updates (2015) -- official clarification on firmware update rules