Questions manufacturers ask
What counts as sufficient evidence?
The Commission does not say. Its guidance states that an applicant must have sufficient evidence that the device was not produced in a foreign country, and that no specific documentation is required. Part IV of the Protocol specifies a complete file for that certification. Whether a given file suffices in a given case remains the Commission's judgment.
Source: FCC Covered List FAQs, retrieved September 8, 2026; Protocol Part IV.
Do COTS components count?
Yes. The Commission's guidance states that COTS components are still counted toward whether a device is foreign-produced, and that the off-the-shelf exception is inapplicable to domestic-end-product status under 25.101(a).
Source: FCC Covered List FAQs, retrieved September 8, 2026; Protocol 4.2.3.
How old can evidence be?
From document date to the file's revision date: twelve months for registry extracts and standing certificates, five-percent ownership statements, site attestations and deep-trace Annex C declarations; twelve months for the Annex E screen, which re-runs on any Part VI trigger; twenty-four months for photographic and production-flow evidence. The SBOM matches the shipping build, and the concentration summary and sole-source register are recomputed at each revision.
Source: Protocol 4.7.3.
What must a supplier declaration say?
Annex C names the declaring supplier and its country, the part numbers covered, the production sites by name, city and country, the site operator where that differs, and a verification contact. The declarant certifies that the parts are produced at those sites, that it will notify the recipient within thirty days of any change of site, and that the declaration may be relied upon. One in another language needs a certified translation.
Source: Protocol Annex C; 4.7.2.
Who signs the attestation?
An officer, which Part II defines as a person with authority to bind the attesting entity and knowledge of, or verified reports covering, the facts attested. For a file supporting a Conditional Approval submission, an authorized corporate officer within the meaning of the July 27, 2026 guidance. Annex A is executed per file revision.
Source: Protocol Part II and Annex A; Conditional Approval guidance, July 27, 2026.
What changes force a re-attestation?
Nine, each within thirty days: a new, changed or discontinued production, assembly, testing or firmware-loading site; a change of contract manufacturer or ODM; a sourcing change on a deep-trace component; a change in the corporate chain or five-percent ownership; a change in board or executive leadership; a new, changed or terminated foreign-government arrangement; a change of the entity responsible for IP or software updates; a sole-source supplier becoming unavailable; any Covered List addition or guidance change touching the file.
Source: Protocol Part VI.
Can we verify our own file?
At Level 1, yes, because Level 1 is self-declared on the Annex A attestation. Level 2 requires a qualified verifier, which Part II defines as a party competent in supply-chain documentation and the Covered List regime, independent in judgment, who runs the Part V methodology and discloses any assistance it gave in assembling the file.
Source: Protocol Parts II, III and V; Annexes A and F.
Start the file.
Working forms and the standard
Annex A attestationAnnex B templateAnnex C declarationVersion 1.0, full text
To have the file assembled and taken to a verifier, request a diagnostic.