Certification timeline, how long should you plan for?

Author Hugues Orgitello Last updated 25 May 2026

Guide · Project planning

Certification timelines published online almost all describe the same imaginary scenario: no lab queue, no test failure, no dossier corrections. Industrial reality looks different. A moderately complex cellular IoT product typically takes 8 to 10 months between hardware freeze and market launch, and the gap between that figure and marketing announcements is entirely explained by three factors: lab availability, first-pass failure rates, and the chronic underestimation of the PTCRB critical path. This page gives realistic ranges by regime and complexity, and identifies the bottlenecks engineering teams almost always discover too late.

The honest baseline

Any certification timeline estimate must make two assumptions explicit:

1. First hidden assumption, first-pass success. Most schedules assume tests pass on the first attempt. In the field, 30 to 40 percent of products fail EMC on their first campaign (consistent industry surveys over the past decade). For article 3.2 radio or OTA testing, the initial failure rate sits in the same range.
2. Second hidden assumption, immediate lab availability. In 2026, the queue at an ISO/IEC 17025 lab for radio testing runs 4 to 8 weeks on average, up to 12 weeks for specialized 5G OTA chambers. A schedule that ignores this queue is wrong by construction.

A realistic estimate therefore applies a 30 to 50 percent margin to the best-case timeline depending on complexity and the number of regimes involved. The rest of this page gives the raw numbers; the Recommended margins section near the bottom indicates how to weight them.

Baseline durations by regime

The table below gives best-case timelines by regime, from the decision to launch certification through market launch. These durations assume an experienced team, a prepared dossier, and a booked lab slot.

Certification	Simple product	Typical IoT	Complex (cellular/5G)
CE: EMC + LVD only	6–8 wks	10–12 wks	14–20 wks
RED (article 3.1 + 3.2)	8–12 wks	12–16 wks	16–24 wks
RED 3.3 cybersecurity	+ 4–8 wks	+ 6–12 wks	+ 12–24 wks
FCC SDoC (Part 15B)	4–6 wks	6–8 wks	n/a
FCC Certification (TCB)	8–12 wks	12–16 wks	16–20 wks
PTCRB Modular Certification	n/a	n/a	24–40 wks
PTCRB End-Product	n/a	8–16 wks	n/a

A few essential remarks on this table:

• CE alone is shorter than commonly believed, but rarely alone. A purely non-radio product (toy, mechanical accessory with simple electronics) can indeed pass in 6 to 8 weeks. As soon as a radio is present, RED kicks in and the duration doubles.
• RED 3.3 cybersecurity is additive: these weeks add to standard RED, they do not replace any of it. In 2026, lab capacity for RED 3.3 remains immature; real timelines sit at the top of the range.
• FCC SDoC vs Certification is not a free choice. As soon as an intentional radiator is present (Wi-Fi, BLE, cellular), Certification with a TCB is mandatory.
• PTCRB Modular Certification is the longest order of magnitude in the ecosystem: 6 months minimum, 10 months frequently, up to 12+ for 5G SA. On any cellular product this path dominates the overall schedule.

The critical path

On any multi-regime project, the total timeline is dominated by a critical path whose decomposition is almost always the same:

1. Lab queue ............................. 4 to 12 wks
2. Lab test campaign ..................... 2 to 6 wks
3. Modifications + partial retests ....... 2 to 8 wks (1 to 3 iterations)
4. Dossier assembly and review ........... 2 to 3 wks
5. TCB or NB review and certificate ...... 4 to 8 wks
6. PTCRB PVG (if applicable) ............. 4 to 8 wks
7. Carrier homologation (each) ........... 4 to 12 wks

That already sums to 22 to 57 weeks for a full cellular product with no anomalies. Since the typical margin on this timeline is 30 to 50 percent, the operational result is 8 to 14 months for a complete project, which matches observed industry data points.

The dominant factor changes by product nature:

• Simple non-radio product → pre-testing and lab campaign dominate.
• Consumer Wi-Fi/BLE product → lab queue dominates.
• Multi-radio industrial IoT + RED 3.3 → cybersecurity review dominates.
• Cellular product → PTCRB + carrier homologations dominate, and everything else becomes subordinate.

§ § §

Scenario A: Consumer Bluetooth speaker

Product: consumer BLE 5.3 speaker, Li-Ion battery powered, launched in EU + US. Applicable regimes: CE (EMC + LVD via EN 62368-1), RED (article 3.1, 3.2 on EN 300 328, and 3.3 cybersecurity from August 2025), FCC Certification Part 15C.

Wk 1     : Regulatory scoping + lab selection + TCB selection
Wk 2-3   : Internal pre-tests (radiated EMC, ESD immunity, BLE output)
Wk 4-5   : Lab booking (queue already negotiated in wk 1)
Wk 6-8   : Lab campaign CE + RED (EMC + radio + safety)
Wk 9     : Preliminary report received + gap identification
Wk 10    : Minor firmware fixes + partial retests
Wk 11    : Final CE + RED report + dossier drafting starts
Wk 12    : FCC submission to TCB + cybersecurity review for RED 3.3
Wk 13-14 : TCB review + corrections
Wk 15    : FCC ID issuance + EAS publication
Wk 16    : EU DoC drafting and signature + CE marking
Wk 17-18 : First marked production units (CE + FCC ID)

Total: 14 to 18 weeks or 3.5 to 4.5 months. Assumptions: experienced team, pre-booked lab, first-pass EMC success. If a PCB respin is required to fix EMC (typical first-pass failure case): add 4 to 8 weeks for the new board and second campaign.

Scenario B: Connected industrial IoT sensor

Product: industrial temperature/humidity sensor with BLE + LoRa 868 MHz + Cat-M, primary-cell powered, launched in EU + US + Canada. Regimes: full CE, RED 3.1/3.2/3.3, FCC Certification, PTCRB End-Product (integrated Quectel or similar module).

Month 1  : Multi-regime scoping + pre-certified cellular module analysis
           + cybersecurity audit for RED 3.3 positioning
Month 2  : Intensive internal pre-testing (EMC, LoRa radio, cellular OTA)
           + EN 18031 architecture review
Month 3  : EU lab booking + PTCRB-recognized US lab booking
           + parallel start of CE + RED 3.1/3.2 campaign
Month 4  : EU campaign continues + FCC Part 15 starts + PTCRB EPC OTA starts
Month 5  : Partial EMC retest (combined-mode failure, classic on multi-radio)
           + FCC submission to TCB
Month 6  : FCC ID issued + PTCRB End-Product submitted to PVG
           + RED 3.3 review begins with specialized body
Month 7  : PVG feedback + OTA adjustments + PTCRB End-Product certificate
           + RED 3.3 review finalized
Month 8  : Consolidated dossier drafting (RED annex V + CE technical file)
           + DoC signature + marking
Month 9-10: Verizon OPC homologation (4-8 wks)
           + production ramp

Total: 8 to 10 months. Assumptions: cellular module already PTCRB-certified (otherwise add 6+ months), team already familiar with RED 3.3 (otherwise +2 months). This is the most representative scenario for industrial IoT products in 2026.

Scenario C: Cellular module manufacturer

Product: 5G NSA Sub-6 + Cat-M + GNSS cellular module, targeting the North American market. Regimes: FCC Certification, full PTCRB Modular Certification, homologations with Verizon, AT&T, T-Mobile, Bell, Rogers.

Month 1   : Spec freeze + band definition + basic RF pre-tests
Month 2-3 : OTA + IMS + IOT pre-tests in dedicated laboratory
Month 4-6 : Full 3GPP RF Conformance testing TS 36.521 + TS 38.521
            (all Cat-M + 5G NSA bands, US + Canada)
Month 7   : Full OTA testing (TRP + TIS all bands)
Month 8   : IMS / VoLTE + IOT (Inter-Operability Testing)
Month 9   : PTCRB dossier compilation + parallel FCC submission to TCB
Month 9-10: PVG review + corrections (4 to 8 wks)
Month 10  : FCC ID issued + PTCRB certificate + TAC/IMEI allocation
Month 10-11: Parallel start of carrier homologations
Month 11-14: Verizon OPC (8-12 wks) — terminal critical path
            + AT&T NDD + T-Mobile 5G SA Working Group
            + Bell / Rogers (direct PTCRB adoption, 4-6 wks)

Total: 10 to 14 months. Assumptions: team already certified 4G modules (otherwise add 3-4 months for 3GPP learning curve), unconstrained budget for maximum parallelization. Verizon OPC is almost always the terminal critical path, its validation cycle is independent of PTCRB and typically adds two to three months at the end of the project.

§ § §

Bottlenecks that destroy timelines

The majority of projects that slip slip for known reasons. Unordered list:

• Lab queue for radio testing. In 2026, 4 to 8 weeks typical, 12 weeks for 5G OTA chambers. Effect on schedule: pure delay waiting for a slot. Mitigation: book 8 to 12 weeks before need, on the basis of solid internal pre-tests.
• First-pass EMC failure. 30 to 40 percent of products on the market. Effect: hardware or firmware respin, new lab campaign. Mitigation: internal semi-anechoic chamber EMC pre-tests or rented day-rate chamber.
• Late discovery of RED 3.3 applicability. Very common in teams without RED history. Effect: 6 to 12 weeks delay for EN 18031 evaluation. Mitigation: systematic article 3.3 scoping in phase 1.
• User manual translation. For a multi-language launch (EU = 24 official languages), technical translation takes 4 to 8 weeks and blocks dossier finalization. Mitigation: start translation in parallel with the test campaign.
• PCB respin to fix EMC. 4 to 8 weeks for a new board (order, delivery, assembly, internal validation) plus 4 to 8 weeks for a new lab slot. Total: 8 to 16 weeks delay. Mitigation: dry-run pre-tests in pre-production, EMC-by-design.
• PVG meeting cadence. The PTCRB Validation Group meets typically bi-monthly. A response to a PVG comment waits for the next meeting: 2 to 4 weeks of latency per iteration.
• Carrier homologation cycles. Verizon OPC adds 6 to 12 weeks on average after PTCRB. AT&T NDD adds 4 to 8 weeks. These cycles are independent of PTCRB and cannot start before the PTCRB certificate is issued. Mitigation: prepare carrier dossiers upstream for immediate submission.
• eSIM provisioning agreements for cellular IoT. A product with eSIM requires agreements with SM-SR / SM-DP+ and target carriers. These commercial negotiations take 2 to 6 months and are often underestimated in engineering planning.

Recommended margins

Starting from the best-case timeline, apply the following margin by project profile:

Profile	Margin over best-case
Single-regime simple CE, experienced team	+ 20 %
Standard CE + FCC, experienced team	+ 30 %
Company's first RED certification	+ 50 %
Multi-regime CE + RED + FCC	+ 40 %
Any project including RED 3.3 in 2026	+ 50 %
Any cellular project with PTCRB	+ 40 %
Full multi-regime cellular	+ 50 %

These margins statistically absorb lab queue, one retest cycle, dossier corrections, and authority latency (TCB, NB, PVG). They do not absorb a full PCB rework or the late discovery of an applicable regime, these two events must be treated as standalone project risks.

What can run in parallel (and what cannot)

Parallelizable tasks:

• EMC emissions and LVD safety testing, often distinct labs.
• FCC submission and PTCRB submission, distinct entities, shared dossiers.
• Test campaign and technical dossier drafting, most of the dossier doesn't depend on final results.
• User manual translation and lab testing, start at documentary freeze.
• Carrier homologations across different countries: Verizon, AT&T, Bell can be launched in parallel.
• Internal pre-tests and lab slot booking, most cost-effective optimization available.

Mandatorily sequential tasks:

• TCB review → then FCC ID issuance.
• PVG validation → then TAC/IMEI allocation.
• PTCRB certification → then carrier homologations.
• Any test campaign → corrections → only then retest.
• PCB respin (order → delivery → assembly) → then new campaign.

Acceleration strategies

Actually effective levers to reduce the timeline:

1. Conformity assessment module choice. For RED, module A (self-declaration on harmonised standards fully applied) avoids the B+C EU-type examination that adds 6 to 16 weeks. See RED procedure.
2. Pre-certified radio module. Using a Wi-Fi/BLE/cellular module already FCC + RED + PTCRB certified turns an 8-month radio project into a 3-month integration project. The hardware premium is almost always lower than the time gained.
3. MRA labs for shared reports. An ISO/IEC 17025 accredited lab recognized under MRA can produce a report usable simultaneously for CE and FCC. Typical savings: 30 to 40 percent of cost and redundant testing avoided.
4. Systematic internal pre-testing. An in-house semi-anechoic chamber (or rented day-rate) for EMC drops first-pass failure rate from 30-40 percent to 10-15 percent. Pays for itself within a few projects.
5. Lab booking at hardware freeze. Book the slot before the product is even ready, at the cost of rescheduling if needed, to avoid the 4 to 8 weeks of queue otherwise endured.
6. Parallel scheduling FCC and PTCRB. Coordinate labs to produce reports usable in both submissions simultaneously. See PTCRB procedure and FCC procedure.
7. Module H for high-volume manufacturers. For manufacturers with many SKUs, module H amortizes the initial investment through reduced per-unit evaluation cost.

Common timing misconceptions

A few widely held beliefs that don't survive scrutiny:

• "CE marking is just paperwork, two weeks." False. Even for a purely non-radio product fully applying harmonised standards, the realistic minimum is 6 to 8 weeks, dominated by the test campaign and dossier assembly. See CE procedure and CE tests.
• "FCC ID is fast, just the TCB validating." The TCB itself takes 2 to 6 weeks of review, but the test campaign that precedes it takes 4 to 8 weeks, and the upstream lab queue 4 to 8 weeks. Realistic total: 12 to 16 weeks from decision.
• "PTCRB is just OTA." No. PTCRB includes full RF Conformance (TS 36.521 and TS 38.521), IMS/VoLTE, IOT (Inter-Operability), Data Throughput, plus OTA. For a complete module, that's typically 4 to 6 months of pure testing.
• "You can submit FCC without finishing RED tests." Possible, but the risk of dossier inconsistency is high. The final design must be frozen before testing, a change after FCC validation triggers a C2PC (2-6 weeks) and a RED retest.
• "Verizon OPC follows PTCRB automatically." False. Verizon imposes its own program with its own tests (specific NDD) and its own cycle. It's a project within the project, and it's almost always the terminal critical path on a North American cellular product.
• "If we fail tests, we just resubmit." False. A failure triggers: root cause analysis, design correction, new PCB or firmware, internal validation, new lab slot, new campaign. Realistic total: 8 to 16 weeks depending on correction nature.

Summary, target durations to remember

For realistic planning, retain these orders of magnitude:

Product type	Realistic duration (best-case + margin)
Simple non-radio product, CE only	2 to 3 months
Consumer Wi-Fi/BLE product, CE + RED + FCC	4 to 5 months
Wi-Fi/BLE product with RED 3.3	5 to 7 months
Multi-radio industrial IoT + PTCRB EPC	8 to 10 months
Full 4G cellular module, FCC + PTCRB + carriers	10 to 12 months
Full 5G cellular module, FCC + PTCRB + carriers	12 to 16 months

These durations assume an experienced team, an unconstrained budget for parallelization, and a product whose design does not need major redesign during certification. Any deviation from one of these three assumptions pushes the timeline toward the top of the range, or beyond.

Working on detailed planning for a multi-regime certification for a real product? AESTECHNO can audit your design and certification plan. Get in touch →

Sources & references

1. Decision No 768/2008/EC, conformity assessment modules , EUR-Lex eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32008D0768
2. Directive 2014/53/EU (RED): annexes II to V , EUR-Lex eur-lex.europa.eu/eli/dir/2014/53/oj
3. FCC Equipment Authorization: 47 CFR Part 2 Subpart J , FCC www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-2/subpart-J
4. PTCRB Certification Process , PTCRB www.ptcrb.com/
5. Delegated Regulation (EU) 2022/30: RED article 3.3 cybersecurity , EUR-Lex eur-lex.europa.eu/eli/reg_del/2022/30/oj