FCC testing: certification and SDoC explained

FCC testing starts with a routing decision, not a quotation. Different radio-frequency devices use different equipment-authorisation procedures. Intentional radiators such as Wi-Fi and Bluetooth devices commonly need Certification; some unintentional radiators can use Supplier's Declaration of Conformity. The test work may look similar at a distance, but the filing route, FCC ID and documents are not interchangeable.

TL;DR

FCC testing assesses radio-frequency devices against FCC rules. The appropriate route is generally Certification, SDoC or an exemption depending on the device and rule part. The responsible party must be able to connect final hardware, antenna, firmware and operating modes to the evidence retained. The useful rule is simple: decide the scope before commissioning work, retain evidence that identifies the actual product, and review it whenever the product or supply chain changes.

What the decision is really about

FCC testing assesses radio-frequency devices against FCC rules. The appropriate route is generally Certification, SDoC or an exemption depending on the device and rule part. The responsible party must be able to connect final hardware, antenna, firmware and operating modes to the evidence retained. Teams get into trouble when they treat the visible label, certificate or checklist as the beginning of compliance. It is the end of a chain that starts with an accurate product description. Write down the model, intended use, users, markets, components and functions. That short note gives engineering, purchasing and whoever approves packaging the same facts to work from. It also stops a perfectly good report being attached to a slightly different product six months later.

The European regulatory framework is deliberately product-specific. A decision that is sound for one product can be wrong for the next even when they share a supplier or a casing. That is not a reason to overcomplicate every launch. It is a reason to record the boundary of the decision, the evidence used and the owner who will revisit it after a meaningful change.

The questions worth answering before release

The table is a working aid, not legal advice. Its value is in making assumptions visible early, when changing a part or updating an instruction is still easy. Keep it next to the bill of materials and the product record rather than letting it disappear into a quotation email.

A practical working sequence

• List radios, antennas, ports, power sources and intended modes.
• Determine Certification, SDoC or another route from official FCC rules.
• Give the lab final configurations, high-power modes and accessories before the chamber slot.
• Keep reports, photos, manuals and label data connected to the tested product.
• Assess RF-relevant changes before release rather than assuming an old report carries over.

Do those steps in that order. Starting with a lab quote, a label proof or a supplier certificate can feel productive, but it can also hard-code the wrong assumption into the project. The better sequence is to establish what the finished product is and which route applies, then ask for the exact evidence that route needs. That makes quotes clearer and makes it much easier to explain why a particular report, declaration or record is in the file.

Evidence that holds up when someone asks

A useful report identifies the device, configuration, method and results clearly enough to connect it to production. Change control is the difficult part: antenna gain, enclosure changes or firmware that changes transmit behaviour can alter the evidence basis. A named owner does not need to be the RF engineer, but they need a gate that asks whether a proposed change needs review before it reaches the line.

The best files are boring in the best sense: each document has a date, version, product link and owner. An engineer who was not part of the original project should be able to follow the trail without guessing which attachment is final. A retailer, customs officer or market-surveillance authority is not looking for an enormous folder; they need a clear account of why the product meets the requirements claimed. See what goes in a technical file for a useful shared structure.

Keep the decision live after launch

The FCC testing decision should not become invisible after the first shipment. Build a short review into ordinary product change control. Ask whether a proposed change affects the product description, market, intended user, materials, radio function, supplier, software, lab evidence, declaration or label. Most changes will not require starting again. The point is to make a considered decision before the change is released, with a note that someone can find later.

This is also where the person closest to the product needs a route to raise uncertainty without being treated as a blocker. A buyer may see a new material first. A support colleague may hear that a customer uses the product in a way the instructions never anticipated. An engineer may know that a firmware release alters a performance limit. Each observation can be recorded as a review trigger, checked against the original evidence, and closed with a short explanation. That approach is simpler than a giant annual audit because it catches changes while the people who understand them are still in the room.

For FCC testing, give that review a named owner and a realistic deadline. A task assigned to ‘compliance’ is usually a task assigned to nobody. A small, visible record of decisions is better than a perfect-looking dashboard that cannot explain why a product is green.

Mistakes that create avoidable rework

• Booking a test before identifying intentional radiators.
• Testing a module and assuming the host needs no further assessment.
• Omitting worst-case modes or antenna details from the lab brief.
• Changing RF-relevant hardware after testing without review.

None of these errors are fixed by adding more confident wording to a declaration. The manufacturer or responsible economic operator still needs to understand the claim and have evidence for the exact configuration placed on the market. Supplier documents, test reports and software records are valuable inputs, but responsibility does not move just because a PDF has a reassuring title.

A realistic pre-launch moment

A device launches with an internal antenna, then a distributor asks for an external-antenna version. The team checks before tooling and learns the gain is central to its authorisation analysis. The change takes days before release rather than becoming a recall risk after stock ships.

The point is not that every change needs a panic. It is that a named review gate makes the sensible response routine: record what changed, ask whether the evidence remains representative, update the file if it does not, and only then release the product. That is calmer than rediscovering the issue when stock is already in a warehouse.

What to do next

Write the antenna inventory first, then compare FCC Certification and SDoC. Start by mapping one live product in the requirements checker. Once the underlying work is complete, the Declaration of Conformity generator can turn the verified details into a consistent document.