FCC KDB Publications: The Engineer's Guide to FCC Guidance Documents

TL;DR -- The FCC's Knowledge Database (KDB) contains guidance documents that fill the gap between what 47 CFR says and what test labs and TCBs actually need you to do. KDB publications are technically "just guidance," but deviating from them without strong justification will get your application rejected. If you're going through FCC certification, you need to know which KDBs apply to your product and what they require.

What the KDB is

The FCC Office of Engineering and Technology (OET) Laboratory Division maintains a collection of staff guidance documents, measurement procedures, and inquiry responses called the Knowledge Database. It lives at apps.fcc.gov/oetcf/kdb/ and is the bridge between the Code of Federal Regulations and the practical reality of getting a device certified.

47 CFR defines the rules. KDB publications tell you how to follow them.

The distinction matters legally. The FCC states that KDB guidance "does not necessarily represent the only acceptable methods for demonstrating compliance." In theory, you could propose an alternative approach. In practice, TCBs and test labs treat KDB procedures as mandatory. A test report that ignores applicable KDB guidance will be rejected by the reviewing TCB, and you'll resubmit with the KDB-compliant approach anyway.

The analogy that works best: the CFR is building code, and KDB publications are the inspector's manual. The building code says a structure must withstand a certain wind load. The inspector's manual says exactly how you measure that wind load, what instruments to use, where to place them. You can argue your alternative measurement is equivalent, but the inspector has a checklist, and the checklist comes from the manual.

Why KDB publications matter

They add specificity the CFR lacks. The CFR often defines requirements in general terms. KDB publications fill in the operational details: exact test setups, separation distances, antenna configurations, power measurement methods, and pass/fail thresholds that the CFR text leaves open. Without KDB guidance, two test labs could run the same test on the same device and get different results.

They narrow CFR scope. The CFR may allow something broadly, but a KDB document adds constraints. The clearest example: 47 CFR 15.212 defines requirements for modular transmitter approval, but KDB 996369 introduces the "Limited Module" concept with additional host-level testing requirements. That distinction does not exist in the CFR text. If you only read the CFR, you'll miss requirements that TCBs will enforce.

They change without formal rulemaking. When the FCC updates 47 CFR, there's a Notice of Proposed Rulemaking, a public comment period, and a Report and Order. When the FCC updates a KDB publication, it just updates it. No Federal Register notice. No comment period. The document gets a new version number, and anyone relying on the previous version needs to catch up. If you have products in the certification pipeline, KDB tracking is not optional.

How KDB publications are structured

Each KDB publication has a six-digit identifier (e.g., 996369, 178919, 447498). Within a single KDB number, there may be multiple documents designated D01, D02, D03, and so on. Each document is independently versioned with a format like "v06r02" (version 6, revision 2).

flowchart TD
    A["KDB Publication Number\ne.g., 996369"] --> B["D01 — General Guidance\nv03r01"]
    A --> C["D02 — FAQ / Supplemental\nv02"]
    A --> D["D04 — Host Integration\nv01r03"]
    A --> E["D05 — Split Modules\nv01"]
    style A fill:#1e3a5f,color:#fff

The numbering is not sequential and carries no inherent meaning -- 996369 is not "newer" than 447498. The numbers are internal identifiers assigned when the publication was first created in the FCC's system.

Some KDB publications are publicly accessible through the KDB search tool. Others are restricted to TCBs and accredited test labs. If you can't find a specific KDB document through the public search, it may be TCB-access-only. In those cases, your test lab or TCB can provide the relevant guidance.

Essential KDB publications

The table below covers the KDB documents that come up most often in FCC certification. If your device falls into any of these categories, read the corresponding KDB before you start testing.

KDB 447498: RF exposure and SAR

This is the KDB publication you'll encounter first and reference most. It covers RF exposure evaluation for all transmitting devices, including:

• SAR exclusion thresholds -- power and separation distance combinations that exempt a device from full SAR testing. Getting below these thresholds saves $5,000 to $15,000 in SAR test costs and 2 to 4 weeks of lab time.
• Simultaneous transmission evaluation -- how to assess RF exposure when a device has multiple radios operating at once (WiFi + Bluetooth + cellular, for instance). The methodology for combining exposure from multiple antennas is here, not in the CFR.
• Test procedures -- specific SAR measurement setups, tissue-simulating liquid compositions, and device positioning requirements.

If your device transmits RF energy at any power level, start with KDB 447498 to determine whether you need full SAR testing or qualify for an exemption. The SAR testing requirements guide walks through this evaluation in detail.

KDB 996369: modular transmitter certification

The go-to guidance for certifying RF modules under 47 CFR 15.212. Contains multiple documents:

• D01 -- General modular certification guidance. Covers the eight requirements for full modular approval, limited modular approval conditions, and the overall framework.
• D04 -- Host integration guidance. Specifies what testing a host manufacturer must perform when integrating a pre-certified module. This is the document that tells you whether your specific integration needs additional RF measurements.
• D05 -- Split module guidance. For modules where the radio components are physically separated (baseband on one board, RF front-end on another). Split modules always require Pre-Approval Guidance.

This KDB introduces the "Limited Module" concept that does not appear in the CFR text. A limited module fails to meet one or more of the eight full-module requirements -- say it uses a standard SMA antenna connector instead of a proprietary one. Limited modules come with grant conditions that restrict how they can be installed, and host integrators must follow those conditions precisely.

KDB 178919: permissive changes

This is the FCC's guidance on 47 CFR 2.1043 -- what happens when you need to modify a certified device. D01 is the Permissive Change Policy document; D02 is the FAQ for edge cases.

Clarifications that come from this KDB rather than the CFR:

• Only the original grantee can file a Class II permissive change. Host integrators using a certified module who need different RF exposure conditions must go through the grantee. This is not obvious from reading Section 2.1043 alone.
• Detailed worked examples for each change class.
• Module-specific permissive change rules and antenna substitution guidance under Section 15.203.

Our permissive changes guide covers this KDB in depth.

KDB 388624 and 641163: Pre-Approval Guidance

These two KDBs work together to control what TCBs can and cannot certify independently.

KDB 641163 maintains the PAG list -- the technologies and device types that are new, complex, or policy-sensitive enough that a TCB cannot issue a grant without first getting FCC approval. KDB 388624 provides the procedural framework, including the "MODLIM" item that governs limited module conditions requiring FCC pre-approval.

If your device or technology appears on the PAG list, budget extra time. The TCB packages your application and submits it to the FCC for review, adding weeks to the certification timeline. A TCB with PAG experience for similar devices will navigate this faster than one encountering the process for the first time.

The PAG list is a moving target. As a technology matures and the FCC becomes comfortable with how it should be evaluated, the device class typically comes off PAG. Monitoring the PAG list is one way to track what the FCC considers genuinely novel in RF technology.

How TCBs use KDB publications

TCBs are the private, accredited organizations that review test reports and issue FCC grants. KDB publications are their procedural reference -- the playbook they follow when reviewing your application.

flowchart LR
    A["Applicant submits\ntest reports + docs"] --> B["TCB reviewer\nchecks against:"]
    B --> C["47 CFR\n(the rules)"]
    B --> D["KDB publications\n(the procedures)"]
    B --> E["PAG list\n(KDB 641163)"]
    E -->|Device on PAG| F["Submit to FCC\nfor pre-approval"]
    E -->|Device not on PAG| G["TCB reviews\nindependently"]
    C --> H["Grant issued\nor deficiency letter"]
    D --> H
    F --> H
    G --> H
    style H fill:#1e3a5f,color:#fff

A typical TCB review checks against KDB guidance at each step:

1. PAG list first. If the device or technology appears on KDB 641163's PAG list, the TCB cannot grant independently. The application goes to the FCC for pre-approval.
2. Measurement procedures. Did the test lab follow the methods in the applicable KDB publications? A radiated emissions test that doesn't follow KDB 558074's procedures will be flagged.
3. RF exposure evaluation. For transmitting devices, the TCB checks the RF exposure assessment against KDB 447498. Wrong SAR exclusion calculation? Deficiency letter.
4. Module integration. For products using certified modules, the TCB verifies compliance with KDB 996369 D04 host integration requirements.
5. Labeling. KDB 784748 specifies labeling requirements that go beyond the CFR text, including electronic labeling provisions and FCC ID placement rules.

When a TCB issues a deficiency letter, the cited references are almost always KDB publications rather than raw CFR sections. Knowing the applicable KDBs before submission reduces deficiency rounds and saves 1 to 4 weeks per round.

When KDBs override or supplement the CFR

KDB publications do not technically override 47 CFR. The FCC is clear that they are guidance, not rules. But in practice, the effect is often indistinguishable from rulemaking:

Adding requirements the CFR doesn't contain. KDB 996369's Limited Module concept imposes requirements (host-level testing, specific grant conditions) that have no basis in the text of 15.212. The CFR defines eight conditions for modular approval. The KDB adds a whole category of approval for modules that don't meet all eight, with its own obligations.

Specifying test methodologies. The CFR says a device must comply with emission limits. KDB publications specify exactly how those emissions are measured -- antenna positioning, measurement distances, detector types, frequency step sizes, test configurations. The measurement method determines the result, so specifying the method is the same as defining the requirement.

Interpreting ambiguous rules. When the CFR text is ambiguous, the KDB interpretation becomes the operative standard. TCBs don't have discretion to reinterpret. They follow KDB guidance, and that guidance becomes the working definition of compliance.

Setting thresholds the CFR leaves open. KDB 447498 specifies SAR exclusion thresholds -- specific power and distance combinations that determine whether full SAR testing is required. These thresholds directly affect certification cost and timeline, and they come from the KDB, not the CFR.

Finding and accessing KDB publications

The FCC KDB search tool at apps.fcc.gov/oetcf/kdb/ lets you search by publication number, keyword, or rule part. Keyword search is unreliable -- searching by the specific six-digit number works better if you know it.

Each KDB document also has a direct URL in the format apps.fcc.gov/kdb/GetAttachment.html?id=[encoded-id]. These links are stable and bookmarkable. Test labs and TCBs often share direct links to specific document versions.

Some KDB materials are only accessible to designated TCBs and FCC-recognized test labs. If you can't find a document through the public search, ask your test lab or TCB. They have access to the full set.

For understanding what changed between KDB versions, the semi-annual TCB Workshop presentations (typically April and October) are your best resource. The slide decks, published on the FCC website, provide context and worked examples that the KDB documents themselves rarely include. The FCC also provides an RSS feed for KDB updates, worth monitoring if you have products in active certification.

Common gotchas

KDB publications change without notice

CFR amendments go through formal rulemaking with public notice and comment. KDB updates just happen. A document version you relied on last month may have been superseded. No email notification, no Federal Register entry, no grace period. If your test report was generated under a previous KDB version and the document was updated before TCB review, the TCB may apply the new version.

Check the current version of all applicable KDB publications right before TCB submission. If you're in the middle of a long testing cycle, check again when testing wraps up.

Not all KDB publications are public

The FCC restricts some KDB content to TCBs and recognized test labs. This creates an information asymmetry: the rules your application will be judged against may not be fully visible to you as the applicant. Your test lab should flag any restricted KDB requirements that affect your product during the test planning phase.

Version tracking is manual

KDB publications use a versioning scheme (e.g., "D01 v06r02") but there is no changelog, no diff tool, and no way to subscribe to updates on a specific document. When a new version appears, you have to compare it against the previous version manually to identify changes. TCB Workshop slides are the closest thing to release notes.

KDB narrows your options

A common pattern: an engineer reads the CFR, concludes their approach is compliant, then discovers during testing or TCB review that a KDB publication imposes additional constraints. The KDB doesn't contradict the CFR -- it interprets it in a way that's narrower than a plain reading might suggest.

Example: 47 CFR 15.212 defines eight conditions for modular approval. An engineer designs a module meeting all eight and expects unrestricted modular approval. But KDB 996369 evaluates the module's antenna connector as a standard type (SMA), which triggers limited modular approval with host-level testing requirements. The CFR says the module must have a "permanently attached antenna" or "unique antenna connector." The KDB defines what "unique" means in practice.

RF exposure thresholds are in the KDB, not the CFR

Engineers sometimes assume they can determine RF exposure requirements from the CFR alone. The CFR (47 CFR 1.1307, 2.1091, 2.1093) establishes that RF exposure evaluation is required, but the specific exclusion thresholds, simultaneous transmission evaluation methods, and test procedures are in KDB 447498. Skipping this KDB and going straight to testing will either result in unnecessary SAR testing (expensive) or an incomplete RF exposure evaluation (rejected by TCB).

Staying current with KDB updates

The most reliable approach is a good relationship with your test lab and TCB. Labs that know your product category will flag relevant KDB changes before you have to ask. That's worth more than any monitoring tool.

The KDB in the certification workflow

Where KDB publications fit in the overall FCC certification process:

flowchart TD
    A["Product design\ncomplete"] --> B["Identify applicable\nrule parts"]
    B --> C["Pull applicable\nKDB publications"]
    C --> D["Design test plan\nper KDB procedures"]
    D --> E["Pre-compliance testing\n(optional but recommended)"]
    E --> F["Formal lab testing\nfollowing KDB methods"]
    F --> G["Test report references\napplicable KDB versions"]
    G --> H["TCB reviews against\ncurrent KDB guidance"]
    H -->|Deficiency| I["Address KDB-cited\nissues and resubmit"]
    H -->|Pass| J["Grant issued"]
    I --> H
    style C fill:#1e3a5f,color:#fff
    style H fill:#1e3a5f,color:#fff

Step 3 -- pulling applicable KDB publications -- is where many teams lose time. Doing this early, before test planning, prevents rework. Doing it late, after testing is complete, risks discovering that your test methodology doesn't match current KDB requirements.

KDB inquiry process

When existing KDB publications don't cover a situation -- a novel device category, an unusual test configuration, an ambiguity in existing guidance -- TCBs can submit a KDB inquiry to the FCC. The inquiry goes to OET staff, who respond. That response may:

• Become a new KDB publication
• Be incorporated into an existing KDB document at its next revision
• Remain a one-off response applicable only to the specific inquiry

Applicants can't submit KDB inquiries directly -- they go through a TCB. If your device is an edge case, work with your TCB to submit the inquiry early, during test planning, not during application review. An inquiry during review adds weeks. One during planning lets you build the answer into your approach from the start.

Related guides

• FCC Equipment Authorization -- the certification process that KDB publications guide
• FCC Permissive Changes -- deep dive on KDB 178919 and modification rules
• FCC Module Certification -- modular approval under 15.212, guided by KDB 996369
• FCC Part 15 Guide -- the rule part most KDB publications interpret
• SAR Testing Requirements -- RF exposure evaluation guided by KDB 447498

Key references

• FCC KDB Search Tool -- apps.fcc.gov/oetcf/kdb/ (public access to KDB publications)
• KDB 447498 -- RF Exposure / SAR guidance
• KDB 996369 -- Modular transmitter certification guidance
• KDB 178919 -- Permissive Change Policy
• KDB 784748 -- Labeling and notification guidance
• KDB 388624 -- Pre-Approval Guidance procedures
• KDB 641163 -- Pre-Approval Guidance list
• 47 CFR Part 2, Subpart J -- Equipment authorization procedures (the rules the KDB interprets)