Regulatory certification — FCC in the US, CE in the EU, UL for safety, and their regional equivalents — is one of the most reliable sources of late-stage schedule slip in hardware products, precisely because teams plan for it as a late-stage step. By the time certification testing actually starts, most of the design decisions that determine whether it passes on the first attempt were made months earlier, when nobody was thinking about compliance.
Why it lands late and hurts more for it
Certification requires a design that's functionally complete and, for most programs, in production-representative form — you can't meaningfully certify a prototype that's still changing. That naturally pushes certification testing toward the end of a project timeline. The problem is that a design flaw discovered during certification testing — excessive RF emissions, an unshielded high-speed trace, a power supply that doesn't meet safety isolation requirements — usually requires a hardware change, which means another PCB spin and another round of testing. A failure discovered in week one of a certification cycle that was scheduled to take a few weeks can turn into a multi-month delay once a redesign and retest cycle is added.
Decisions made early that determine certification difficulty
- Pre-certified radio modules vs. a custom RF design. A module that's already been through FCC/CE testing (as a modular certification) can shortcut a large portion of the radio-related testing, at the cost of a higher per-unit price versus a discrete chip-and-antenna design that has to be certified from scratch as part of the whole product.
- PCB layout and shielding decisions made during schematic capture and layout directly affect EMI/EMC emissions — a board that wasn't designed with emissions in mind is far more likely to need rework after a failed test.
- Power supply topology for anything with safety certification requirements (UL, IEC) — isolation requirements and creepage/clearance distances need to be designed in from the start, not retrofitted.
- Enclosure material and design can affect both EMI shielding effectiveness and safety classification, and is often finalized independently of the electrical design team, creating a coordination gap.
Pre-compliance testing catches problems while they're still cheap to fix
Pre-compliance testing — using the same measurement techniques as formal certification labs, but done earlier and informally, sometimes in-house with appropriate equipment or via a lab that offers pre-compliance scans — surfaces the same categories of problems formal certification would catch, but early enough that a fix is a design revision rather than a program-threatening delay. Teams that build a pre-compliance check into an early prototype milestone catch the majority of issues before they're expensive to fix.
Regional variation adds real complexity
A product launching in multiple regions faces different certification regimes with different requirements and timelines — FCC and CE in particular have meaningfully different testing scopes, and additional markets (Japan's MIC, Canada's ISED, and others) each add their own requirements. Planning for a single region's certification and assuming others will follow trivially is a common and costly underestimate for products with multi-region launch plans.
Building certification into the schedule, not after it
The practical fix isn't complicated: treat certification requirements as a design input from the schematic stage, budget a pre-compliance testing milestone into the prototype phase (not just before final certification), and build schedule buffer for at least one round of post-certification-test fixes, since even well-designed products sometimes need minor rework. Programs that do this reliably ship closer to their original timeline than programs that treat certification as a final checkbox.
How we approach this
Certification requirements get factored into schematic and layout decisions from the start of a hardware engagement, with pre-compliance testing built into the prototype schedule rather than left as a surprise before launch. See our embedded hardware work for how this fits into a full hardware build.