Best Practices for Designing FCC-Certifiable Hardware

15 min read  ·  RF Engineering  ·  Regulatory Compliance  ·  PCB Design  ·  CE Marking  ·  Global Markets

FCC certification is not a final step — it is a design constraint that must be woven into every layer of your hardware from day one. Teams that treat it as an afterthought face costly board respins, failed chamber tests, and months of schedule slip. This guide covers the engineering practices that separate hardware that sails through certification from hardware that doesn’t — and extends to CE marking and international certification stacking for products targeting global markets.

1. Understand which FCC rules apply to your device

Before a single schematic symbol is placed, you need to know exactly which FCC Part your product falls under. The most common for IoT and embedded hardware are Part 15 (unintentional and intentional radiators) and Parts 22/24/27 for licensed cellular bands. Getting this wrong wastes months — a device with an integrated radio module classified under Part 15B instead of Part 15C will fail certification regardless of how clean its emissions are.

Key classifications to resolve at architecture stage:

• Part 15B — unintentional radiators (digital devices with no intentional radio, e.g. MCU boards, power supplies)

• Part 15C — intentional radiators (devices with Wi-Fi, BLE, Zigbee, LoRa, or any unlicensed RF transmitter)

• Part 15E — unlicensed U-NII devices operating in 5 GHz bands

• Part 18 — industrial, scientific and medical (ISM) equipment using RF energy for non-communication purposes

• Parts 22/24/27 — licensed cellular (LTE-M, NB-IoT, CAT-M); these require additional carrier approvals

If your device uses a pre-certified module (e.g. a certified BLE SoC module), you may qualify for a Declaration of Conformity (DoC) or SDoC rather than a full FCC ID application — provided you follow the module’s integration instructions precisely and do not alter its antenna or RF path.

2. Make RF architecture decisions before PCB layout begins

Radiated emissions problems are almost always born in architecture and amplified by layout. The decisions that most commonly cause certification failures are:

Clock frequency selection

Every clock harmonic is a potential emission. Choose oscillator frequencies whose harmonics fall away from your operating RF band and away from FCC measurement frequencies (30 MHz to 1 GHz for Part 15B, up to 40 GHz for Part 15C). A 48 MHz USB clock produces harmonics at 96, 144, 192 MHz — map these against your band plan early.

Harmonic mapping — 48 MHz system clock:

  H2  →  96 MHz    check: proximity to FM band (88–108 MHz)

  H3  → 144 MHz    check: aviation nav band (108–137 MHz)

  H4  → 192 MHz    check: generally clear

  H10 → 480 MHz    check: proximity to LTE Band 12/17

Antenna selection and placement

For devices using a pre-certified module, the antenna listed in the module grant is the only antenna you can use without triggering a Class II Permissive Change (which requires new testing). If you need a custom antenna, budget for full RF testing with that antenna from the start, and test multiple antenna placements during prototyping. Proximity to metal enclosures, battery packs, and display assemblies will detune the antenna in ways that are very hard to predict analytically.

Do not swap antennas between prototypes without retesting. Even changing cable length or connector type on a certified antenna path can void the module certification and require a new FCC ID application.

Power supply topology

Switching regulators are among the most common sources of conducted and radiated emissions failures. A buck converter running at 500 kHz with poor layout produces harmonics that extend well into the VHF range. Where emissions budget is tight, consider LDO regulators for noise-sensitive rails (ADC reference, RF supply), or choose switcher ICs with spread-spectrum modulation that distributes emissions energy across a wider bandwidth, reducing peak amplitude at any single frequency.

3. Schematic practices that prevent emission problems

Bypass capacitor strategy

Place bypass capacitors at every IC power pin. Use a parallel combination: a 100 nF ceramic for mid-frequency decoupling and a 10 µF bulk capacitor for low-frequency supply stiffness. For RF ICs, add the manufacturer’s recommended pi-network filter on the supply rail — these are not optional.

Bypass strategy per power domain:

  Digital logic (3.3 V):   100 nF + 10 µF per IC cluster

  RF supply (1.8 V):       10 nF ‖ 100 nF ‖ 1 µF + ferrite bead isolation

  ADC reference:           10 nF + 1 µF + RC low-pass filter

  Crystal oscillator:      100 nF directly at supply pin, no shared via

Ferrite bead selection

Ferrite beads are not generic — their impedance curves vary dramatically across frequency. Always use a ferrite bead with a peak impedance in the frequency range you are trying to attenuate, and check the impedance curve at your operating current. Many ferrite beads lose 80% of their impedance under DC load. The datasheet curve is measured at zero current; your application is not.

Crystal oscillator layout in schematic

Define the crystal, its two load capacitors, and any series resistor as a tight sub-schematic block. The load capacitors must be placed within 1–2 mm of the crystal body in layout — flag this in your schematic notes so it is not overlooked during component placement.

4. PCB layout: where most certification failures originate

The majority of radiated emissions failures at the test chamber trace back to PCB layout decisions — not component selection. Get layout right and you solve most problems before they exist.

Ground plane continuity

A solid, unbroken ground plane beneath all digital circuitry is non-negotiable. Voids, slots, and traces routed through the ground plane create partial antennas that radiate at frequencies determined by their physical length. If you must route a trace through a layer that would otherwise be continuous ground, route the signal and its return path together using a differential pair or a guard trace with stitching vias every 1/20th of the wavelength of your highest-frequency signal.

High-speed trace routing rules

• Keep high-speed clock traces as short as possible; every mm of unterminated clock trace is a potential antenna

• Route differential pairs with matched length and constant spacing — use your EDA tool’s differential pair router, not manual routing

• Avoid routing high-speed signals near board edges — edge currents radiate efficiently and are hard to filter

• Do not route signals across split planes or over plane voids — return current will detour, creating a loop antenna

• Add series termination resistors (22–33 Ω) at the source of each high-speed clock or data line to damp reflections

• Keep trace impedance consistent; impedance discontinuities cause reflections that generate harmonics

RF trace design

All RF signal traces must be designed as controlled-impedance transmission lines — typically 50 Ω microstrip or coplanar waveguide with ground (CPWG). Calculate the required trace width for your stackup using your PCB manufacturer’s impedance calculator, not a generic formula.

50 Ω microstrip — approximate trace widths (FR4, εr ≈ 4.4):

  4-layer 1.6 mm board (7 mil dielectric):   W ≈ 13–14 mil

  6-layer 1.0 mm board (4 mil dielectric):   W ≈  8–9 mil

  Always confirm with your fab’s impedance-controlled stackup spec.

Antenna keep-out zones

Define antenna keep-out areas in your PCB design rules and enforce them. No copper pours, no vias, and no signal traces should appear in the keep-out zone beneath or adjacent to an antenna element. For chip antennas and PCB trace antennas, the keep-out extends to the ground plane layer immediately beneath the antenna.

For compact IoT products, place the antenna at a board corner or edge, extend it beyond the PCB outline if possible, and use a notch in the ground plane to feed it. This is the single layout practice that most reliably improves antenna efficiency in small form factor designs.

5. Pre-compliance testing: find problems before the chamber does

Pre-compliance testing is the single highest-ROI activity in an FCC certification program. A day of pre-compliance testing at a local EMC facility costs a fraction of a full certification test, yet catches the vast majority of issues that would otherwise cause a formal test failure. Do it early — ideally on your first functional prototype, not your DVT build.

What to measure in pre-compliance

• Radiated emissions — compare against Part 15 Class B limits with 6 dB margin

• Conducted emissions — measure on AC mains input if mains-powered; Part 15B Table 8 limits apply

• Antenna port power — for intentional radiators, verify output power is within band limits

• Spurious emissions — measure harmonic and spurious output across 30 MHz–6 GHz

• Frequency accuracy and stability — for licensed band devices, verify frequency error against Part specification

Building a low-cost in-house pre-scan setup

A near-field probe set, a spectrum analyser covering 30 MHz–3 GHz, and a laptop running free EMC software enables continuous emission monitoring throughout development. Near-field probes do not give absolute dBµV/m readings, but they are invaluable for identifying emission sources and verifying that a fix works before returning to a formal chamber.

6. Documentation and test report readiness

A complete FCC application requires more than passing test results. The following documentation must be in order before submitting to an accredited test laboratory or filing directly with the FCC:

• Block diagram showing all signal paths, intentional radiators, and interconnections

• Schematics for all RF sections (required for Part 15C devices)

• Bill of materials identifying all active and RF components

• Antenna specifications and, for custom antennas, gain and pattern plots

• Operational description covering all device operating modes

• Tune-up procedure describing any field-adjustable parameters

• Label location drawing showing where the FCC ID will be permanently affixed

• User manual draft with required FCC compliance statements (Part 15.19, 15.21, 15.105)

FCC ID label requirements changed in 2015 to permit electronic labelling (e-labelling) for devices with displays. If your product has a screen, you may display the FCC ID in a settings menu rather than on a physical label — but the method must be disclosed in the application and accessible within 3 menu steps.

7. Modular certification strategy

If your hardware platform will spawn multiple SKUs — different antenna configurations, different enclosures, different regional markets — design your certification strategy as modularly as your hardware. Obtain an FCC ID for the radio module subsystem independently of the host board wherever possible. This allows future product variants, enclosure changes, and accessory additions to be handled via a Declaration of Conformity or a Class II Permissive Change rather than a full new certification, saving significant time and cost on each iteration.

8. CE marking for the European market

CE marking is not a certification issued by a third-party body — it is a self-declaration by the manufacturer that the product conforms to all applicable EU directives. For wireless IoT hardware, the primary directives are the Radio Equipment Directive (RED, 2014/53/EU) and the Electromagnetic Compatibility Directive (EMCD, 2014/30/EU). Products that connect to mains power also fall under the Low Voltage Directive (LVD, 2014/35/EU).

Radio Equipment Directive (RED) essentials

Under RED, any device that intentionally transmits or receives radio waves must demonstrate conformity with three essential requirements:

• Article 3.1(a) — health and safety (equivalent to LVD requirements for electrical safety)

• Article 3.1(b) — electromagnetic compatibility: the device must not cause harmful interference and must be immune to interference that would degrade operation

• Article 3.2 — effective use of radio spectrum: the device must operate within its designated frequency band at declared power levels, without causing interference to other radio equipment

For Bluetooth and Wi-Fi devices, conformity to 3.2 is typically demonstrated using harmonised standards — principally EN 300 328 for 2.4 GHz band devices and EN 301 893 for 5 GHz band devices. Always check the Official Journal of the EU for the current list of harmonised standards applicable to your frequency band and device type, as these are updated periodically.

Technical construction file (TCF)

Unlike FCC, CE marking does not require submission of documentation to a regulatory body for most device categories. Instead, you must compile and retain a Technical Construction File (TCF) for a minimum of 10 years after the last product is placed on the market. The TCF must include:

• A description of the product and its intended use

• Design and manufacturing drawings, schematics, and circuit descriptions

• List of harmonised standards applied, or descriptions of the solutions adopted to meet essential requirements where no harmonised standard exists

• Test reports — either from an accredited Notified Body or from a competent in-house test facility

• A copy of the signed EU Declaration of Conformity

You do not send the TCF to any authority when you CE mark a product. You are, however, legally obliged to produce it within 10 days if a Market Surveillance Authority requests it. Inability to produce the TCF is grounds for removal from sale across all EU member states.

CE vs FCC: key differences at a glance

	FCC (USA)	CE (EU)
Framework	Government approval / filing	Manufacturer self-declaration
Issued by	FCC or Telecommunication Certification Body (TCB)	Manufacturer (Notified Body for some categories)
RF standard	FCC Parts 15, 22, 24, 27 etc.	RED 2014/53/EU + harmonised ENs
EMC standard	FCC Part 15 B/C	EMCD 2014/30/EU + EN 55032 / EN 55035
ID marking	FCC ID on product / e-label	CE mark on product; no individual ID
File retention	Test reports at TCB / FCC database	TCF held by manufacturer for 10 years
Renewal	Not required (modular changes via PCh)	Not required (unless product changes materially)

UKCA marking post-Brexit

Since January 2021, products placed on the Great Britain market (England, Scotland, Wales) require UKCA marking rather than CE marking. The technical requirements are currently aligned with the EU directives, but UK authorities may diverge over time. Northern Ireland continues to accept CE marking under the Windsor Framework. Products marketed in both the EU and Great Britain may carry both CE and UKCA marks simultaneously.

As of 2024, the UK government has extended the period during which CE-marked products can be sold in Great Britain for most product categories. Always verify the current transition timeline on the UK government website before assuming CE acceptance in GB.

9. International certification stacking

A product targeting multiple markets must carry the regulatory approvals of each jurisdiction. This is known as certification stacking — and planning it upfront dramatically reduces total cost compared to running each certification sequentially and independently.

Major market certifications at a glance

Market	Mark / ID	Body / Framework	Key standard
USA	FCC ID	FCC / TCB	47 CFR Part 15 / 22 / 27
EU	CE mark	Manufacturer / NB	RED 2014/53/EU + EN harmonised
UK	UKCA mark	UK CA	UK Radio Equipment Regs 2017
Canada	IC ID	Innovation, Science & EC	RSS-247 / RSS-Gen
Japan	MIC / Giteki	MIC / TELEC	Radio Law of Japan
South Korea	KC mark	NRA / KCC	Radio Waves Act + KC RF
Australia/NZ	RCM mark	ACMA / RSM	AS/NZS 4268; EIRP limits
India	BIS mark	WPC + BIS	WPC spectrum licence + BIS IS
Brazil	Anatel	Anatel	Resolucao 506 / 680
China	SRRC + CCC	SRRC + SAMR	SRRC type approval; CCC safety

Designing a stacked test plan

The most cost-efficient approach to multi-market certification is to align your test schedule around the markets with the most demanding requirements — typically FCC for radiated limits and Japan MIC for frequency accuracy — and use the resulting test data as the foundation for other submissions where test equivalence is accepted.

Key stacking efficiencies to plan for:

• FCC and IC (Industry Canada) share substantial test equivalency. A device with FCC approval can obtain Canadian IC certification using the same test data in most cases, with only a supplementary declaration and IC ID application required.

• ANSI C63.4 (FCC test methodology) and CISPR 32 (EN 55032, used for CE) are similar but not identical. Discuss with your test laboratory before the test run — a single test campaign can often generate data sufficient for both if the measurement distances and antenna heights are set to satisfy both standards simultaneously.

• For RCM (Australia/New Zealand), ACMA accepts ISED and FCC test reports as supporting evidence, significantly reducing independent test time.

• Japan MIC (TELEC) testing must be performed by a Japanese Registered Certification Body (RCB) or using a laboratory with TELEC accreditation. Factor in 6–8 weeks for TELEC-specific testing and document translation.

• SRRC (China) testing must be conducted in-country by a CNAS-accredited laboratory — foreign test reports are not accepted. Plan for a separate China-specific test campaign and budget 8–12 weeks.

Brazil (Anatel) and India (WPC + BIS) certifications are frequently underestimated in programme plans. Anatel requires local homologation via an accredited laboratory in Brazil with Portuguese-language documentation. India WPC spectrum licensing can take 12–16 weeks. Include these in your launch plan from the start.

Multi-market label strategy

When your product carries certifications from multiple jurisdictions, the labelling requirements compound. Key rules:

• FCC ID must be permanently affixed or electronically accessible (e-label) — the FCC ID format is FCC ID: [Grantee Code][Equipment Product Code]

• CE mark must be at least 5 mm in height, visible, legible, and indelible on the product or its packaging where the product is too small

• IC ID (Canada) must appear adjacent to the FCC ID statement on the label

• Giteki mark (Japan) must be affixed as a physical mark — electronic labelling is not accepted under Japanese Radio Law

• SRRC approval number must appear on the product label for China; a Chinese-language compliance statement is also required in the user documentation

Design your product label and enclosure with a multi-mark reserved area from the first mechanical prototype. Retrofitting label space after tooling is confirmed is expensive. A 15 × 25 mm reserved label zone is a reasonable minimum for a product targeting five or more markets.

Managing certificate validity and post-market obligations

FCC grants do not expire, but they can be voided by modifications to the device, antenna, or software that affects RF performance. CE conformity must be reassessed whenever a product change could materially affect compliance with the applicable essential requirements. Most other national certifications have similar variation procedures.

Establish a formal change management process that classifies every hardware and firmware change against its potential certification impact before the change is released. This prevents the common scenario where a cost-reduction component swap — a different crystal, a revised PMIC, a new PCB revision — unknowingly invalidates an existing certification.

Need help designing for FCC, CE, and global certification?

Our embedded hardware team has guided dozens of IoT products through FCC, CE, IC, TELEC, and RCM certification — from first schematic to approved grant. Get in touch to discuss your project.

Tags: FCC certification · CE marking · EMC design · PCB layout · RF hardware · Part 15 · RED directive · Pre-compliance testing · TELEC · IC Canada · SRRC · International certification · IoT hardware · Antenna design