Gatewell Group
Buyer's kit

What to require from a vendor of routers, drones, inverters or robots under the FCC Covered List

Require a stated conformity level of the Gatewell Protocol for Origin Evidence, a current date, and the right to inspect the file behind it. The level names who stands behind the origin evidence, and it fixes how long a dated claim stays current.

The reason sits in the Commission's own guidance. An applicant for equipment certification “will need to be able to have sufficient evidence that the device in question was not produced in a foreign country to make this certification, but there is no specific documentation or evidence required.” Your vendor holds an obligation whose contents the Commission has not specified, which leaves a buyer free to specify them in the solicitation.

Source: FCC Covered List FAQs on advanced robotic devices and power inverters, as retrieved September 8, 2026.

Levels

Which level to ask for.

A manufacturer may claim any level it satisfies. What to require is the buyer's choice.

Level 1 · Documented

A file the manufacturer signs

A complete Origin Evidence File under Part IV, every element officer-attested on Annex A, declared by the manufacturer itself. Current twelve months from the file's revision date.

Level 2 · Verified

An outside examination of it

Level 1 plus an independent examination under Part V, closing with a qualified verifier's Annex F statement of what was examined and confirmed. Current twelve months from that date.

Level 3 · Monitored

Verification that keeps running

Level 2 plus standing Part VI change control and annual re-verification. Continuous, and it lapses automatically if re-verification is missed. Under a Conditional Approval carrying an onshoring plan, it adds the quarterly onshoring module at 3.3.

Source: Gatewell Protocol, Version 1.0, Part III, 3.1, 3.2.1, 3.3; Part V; Annexes A, F.

Clause language

Five pieces of text, ready to paste.

This language is a template for your counsel to adapt to your contract and jurisdiction. Gatewell Group is not a law firm and this page is not legal advice.

The clause text and the questionnaire below are dedicated to the public domain under CC0 1.0, with no attribution asked.

1. Solicitation requirement, for an RFP or RFQ

Origin evidence. Offeror shall state, for each offered model in a covered equipment category, its conformity level under the Gatewell Protocol for Origin Evidence, Version 1.0 (gatewellgroup.com/protocol/v1.0), and the date of the claim. [Buyer] requires [Level 2], claimed not more than [twelve] months before submission. Offeror shall deliver the Part VII conformity statement, the Annex A attestation and, at [Level 2] or above, the Annex F verification statement, and shall state whether each model is covered equipment and, if so, identify the Conditional Approval relied on.

2. Supply agreement, clause set

(a) Representation. Supplier represents that each model in Schedule [__] is not covered equipment under the FCC Covered List, or is covered equipment subject to a current Conditional Approval identified in Schedule [__] by holder, date, scope and any termination date.

(b) The file. Supplier shall maintain, per scheduled model, an Origin Evidence File conforming to the Gatewell Protocol for Origin Evidence, Version 1.0 (gatewellgroup.com/protocol/v1.0), at [Level 2] or above.

(c) Deliverables. On award, and on each renewal or extension, Supplier shall deliver the Part VII conformity statement, the Annex A attestation and, at [Level 2] or above, the Annex F verification statement.

(d) Change notice. Supplier shall notify [Buyer] in writing within thirty days of any Part VI material change affecting a scheduled model, and re-attest the affected sections in the same period.

(e) Inspection. Supplier shall make the file and the documents it references available for inspection by [Buyer] or its designated reviewer, under the confidentiality terms of Section [__], on [ten] business days' notice.

(f) Flow-down. Supplier shall impose paragraphs (b) through (e) on each contract manufacturer and ODM performing final assembly, principal subassembly, firmware loading or compliance testing, and obtain from each the 4.3 site attestation.

(g) Lapse. If a conformity claim lapses, or paragraph (a) ceases to be accurate, Supplier shall notify [Buyer] within [five] business days. [Buyer] may suspend orders for the affected models until conformity is restored, and terminate for cause if it is not restored within [sixty] days.

3. Purchase order, short form

Seller states that each item on this order conforms to the Gatewell Protocol for Origin Evidence, Version 1.0 (gatewellgroup.com/protocol/v1.0), at Level [2] as of [date], and that no Part VI material change has occurred since. Seller shall furnish the Annex A attestation and, at Level 2 or above, the Annex F statement on request.

4. The statement a vendor returns

“[Company]'s Origin Evidence File for [models] conforms to the Gatewell Protocol for Origin Evidence, Version 1.0, at Level [1/2/3], as of [date].”

A Part VII claim names the level and the date, may not reach models outside the schedule, and may not imply government endorsement.

5. Public entity spending a federal award: solicitation requirement, subaward condition, category attachment

Origin evidence. (a) For each offered model of connected equipment in a category listed in Attachment [__], Offeror shall deliver with its offer an origin-evidence file conforming to the Gatewell Protocol for Origin Evidence, Version 1.0 (gatewellgroup.com/protocol/v1.0), at [Level 2], or an equivalent documented method that [Agency] accepts as meeting paragraph (b).

(b) An equivalent method shall, for each model, (1) identify the device, its manufacturer, and the place of final assembly and of each principal subassembly; (2) record component origin at the bill-of-materials level in enough detail to support any domestic-content percentage Offeror certifies under this solicitation; (3) screen the manufacturer, its owners and its principal suppliers against the entities named under Section 889 of Pub. L. 115-232 and the FCC Covered List; (4) identify the entities that supply and update the device's firmware and software; (5) carry an attestation signed by an officer of the manufacturer and dated not more than [twelve] months before the offer; and (6) be retained by Offeror and made available to [Agency] and its auditors on request.

(c) The file supports each origin certification Offeror makes under this solicitation, including any certification under [the Build America, Buy America provisions] [2 CFR 200.216] [state statute]. An offer that certifies without the file is nonresponsive.

Origin evidence for connected equipment (subaward condition, pass-through entity). Subrecipient shall include the origin-evidence requirement at Attachment [__] in each solicitation, contract and purchase order under this subaward for connected equipment in a listed category, shall retain each file with its procurement records for the period 2 CFR 200.334 requires, and shall make it available to [Pass-through entity] on request. This condition is imposed under 2 CFR 200.332(b)(3).

Attachment [__], categories (a starting point). Unmanned aircraft systems; routers; power inverters; advanced robotic devices; telecommunications and video surveillance equipment.

Paragraph (b) states the features an equivalent method has to have, which is what 2 CFR 200.319 asks of a requirement that names a brand or a method. The six features are the Origin Evidence File's own sections and its currency rule, so a file under the Protocol meets them as written. “Nonresponsive” in (c) is the strong form; a buyer may write “may be found nonresponsive.”

Source: Gatewell Protocol, Version 1.0, Parts IV, VI, VII; 4.3; Annexes A, F; 2 CFR 200.319, 200.332(b)(3), 200.334.

Vendor questionnaire

Fourteen questions, and what a complete answer looks like.

Send it with the solicitation. A vendor holding a conforming file answers from that file.

QuestionA complete answer includesProtocol reference
Which models are covered, with what FCC IDs?Model numbers, FCC IDs or SDoC status, equipment classes and authorization dates, reconciled to FCC records.4.1
What is the coverage determination per model?The definition text quoted with its retrieval date, the analysis citing document IDs, the conclusion and preparer.4.2
Where is each model produced, step by step?Every assembly, subassembly, firmware-loading and test site, with operator, step and a signed attestation.4.3
Where does each BOM line come from, and where was the device designed?A BOM on the Annex B.1 schema, an Annex C declaration one tier up per deep-trace component, design origin.4.4.1, 4.4.2, Annexes B, C, D
How concentrated is the chain, by country?Per country, the share of BOM value and of production volume, on a stated basis.4.4.3, Annex B.2
Which lines are sole-sourced?Each supplier and country, with a contingency plan naming an alternate, buffer stock or redesign path.4.4.4, Annex B.3
Who owns you, and who runs the company?Ownership to the ultimate parent, five-percent beneficial owners, board and executives with nationality and residence.4.5.1 to 4.5.3
Does any foreign government own, control or finance you?Any such arrangement, including influence over operations, decisions or technology access. A negative stated expressly.4.5.4
When did you last screen against the Covered List?The Annex E screen across chain, owners, officers, site operators and deep-trace manufacturers, with result and reviewer.4.5.5, Annex E
What is in the firmware, and who pushes updates?An SBOM in SPDX or CycloneDX matching the shipping build, the update and IP-owning entities, software origin.4.6.1 to 4.6.3
How old is the evidence, and is any of it foreign-language?Twelve months for registry extracts, ownership statements, attestations, declarations and the screen; certified translations.4.7.2, 4.7.3
Who signed the attestation, and what has changed since?An officer able to bind the entity signing Annex A, and any Part VI trigger re-attested within thirty days.4.8, Part VI, Annexes A, G
What level do you claim, as of what date?The Part VII sentence, with the Annex F statement at Level 2 or above.Part VII, Annex F
If covered, what is the Conditional Approval status?Holder, grant date, scope, any termination date, the onshoring point of contact.Part II, 3.3.2

Questions buyers ask

Does the FCC require buyers to do this?

No. The duty sits on the applicant for equipment authorization, who certifies in writing that the equipment is not prohibited under 47 CFR 2.903 and must hold sufficient evidence behind it. The Commission prescribes documentation for neither of you.

Source: 47 CFR § 2.911(d)(5); FCC Covered List FAQs, retrieved September 8, 2026.

Is a vendor's FCC ID enough?

Not by itself. An FCC ID identifies a grant of certification, which stays effective until it is set aside, revoked, withdrawn, rescinded or surrendered, or the Commission establishes a termination date. It rests on the applicant's own signed certification, behind which the Commission requires no particular evidence. A false covered-equipment certification is the predicate for revocation under 47 CFR 2.939(d), exercised in August 2026 against Odyssey Robot LLC.

Source: 47 CFR §§ 2.911(d)(5), 2.927(a), 2.939(d); Order of Revocation DA 26-839, August 11, 2026.

What about models authorized before the category was listed?

The grant stands. Equipment authorizations do not expire and there is no renewal procedure, so a certification granted before a category was listed remains valid.

Two limits belong in the answer. Importation and marketing of previously authorized covered equipment can be shut off under 47 CFR 2.939(e) without revoking the authorization, which happened for equipment listed in 2024 or earlier, effective July 16, 2026. Covered equipment is also excluded from the permissive-change procedures at 47 CFR 2.932(b) and 2.1043(b), which closes off hardware changes absent a waiver. Software and firmware updates that mitigate harm to consumers are permitted by waiver until at least January 1, 2029.

Source: 47 CFR §§ 2.927(a), 2.932(b), 2.939(e), 2.1043(b); DA 26-635, 91 FR 41023; DA 26-789, July 28, 2026.

Does this replace our Section 889 representations?

No. Section 889 travels through its own FAR machinery, and an offeror's representation under 48 CFR 52.204-24 answers a different question from the one the Covered List asks. Our crosswalk maps the file against each regime.

Source: 48 CFR §§ 4.2105, 52.204-24, 52.204-25.

May we change the clauses, and what does this cost?

The clause language and the questionnaire are dedicated to the public domain under CC0 1.0, with no attribution condition, so change what you like. The standard itself is published under CC BY 4.0; a modified text may not be called the Gatewell Protocol, and the designation and marks are reserved. Requiring it costs nothing. The Protocol is free to use, to cite and to require of counterparties.

Source: Gatewell Protocol, Version 1.0, status statement and licence terms.

How do we check a vendor's claim?

Start with the sentence. A claim must name the level and the date and may not reach models outside the schedule, so one missing either is not a claim under the Protocol. At Level 2 or 3 the Annex F statement identifies the verifier, the version applied and the revision examined, and carries an independence disclosure.

The registry lists verifications issued under the Protocol. Verification under Version 1.0 opens with the final text, so it holds no entries until then.

Source: Gatewell Protocol, Version 1.0, Parts V and VII; Annex F.

Put it in the next solicitation.

The clause set goes into an RFP as written, with the level and the currency period filled in. The standard, with every annex a vendor works from, is at Version 1.0.

To have a vendor bench assessed against the Protocol, request a diagnostic.

Request a Diagnostic