Certification timeline: the durations set by the texts

Hugues Orgitello updated 7 Oct 2026 8 min read

Most certification timelines published online, this page's own earlier version included, are tables of "6 to 8 weeks" and "8 to 10 months" with no source behind them. This rewrite keeps only durations that a text actually fixes: a regulation, a regulator's published service standard, or the scheme owner's own process document. Those clocks are fewer than people expect, and most of them start only once a complete file is filed. Testing in an ISO/IEC 17025 lab, sample logistics, retests and translation sit outside every one of them. The rest of your schedule has to come from your own lab, TCB and notified body quotes, and this page says where those gaps are.

How to read a regulatory clock

Three questions decide whether a duration in a text helps your plan:

1. When does the clock start? Almost always at a complete application, not at the start of testing. Korea, China and ISED all say so explicitly, and China excludes testing time from its 15 working days.
2. Who is bound? Some clocks bind the authority (Korea, China, Peru), some only state a target (ISED service standards), and some bind you (FCC Grantee Code fee, PTCRB TAC reservation).
3. What does it cover? A 5-day certification in Korea excludes the time spent verifying the test report; T-Mobile five business days applies only "if you meet all of T-Mobile requirements and there are no certification issues".

Durations fixed by a text, regime by regime

Regime	Step	Duration	When the clock starts, what it excludes	Source
FCC	Grantee Code fee	30 days	From issuance of the code; unpaid code is removed and a new one must be obtained	47 CFR 2.926(c)
FCC	TCB review of a certification	None	No rule sets a review time; TCB fees are set by each TCB (2.962(e))	47 CFR 2.962
FCC	PAG review (listed equipment only)	"Typically 2 to 6 weeks"	A description in the order, not a rule; since June 15, 2026 the PAG list prioritizes equipment tested in Trusted Test Labs (2.964(a))	FCC 26-28, para. 65
FCC	Set-aside of a grant	30 days	From the date of grant; the TCB or the FCC may set aside a non-compliant grant, after which only the FCC can revoke it under 2.939	47 CFR 2.962(f)
FCC	Short-term confidentiality	180 days at most	From the grant date	KDB 726920
FCC	TCB report on corrective action after post-market surveillance	30 days	The TCB reports the grantee actions to the Commission	47 CFR 2.962(i)(4)
EU (RED, Decision 768/2008/EC)	EU-type examination by a notified body	None	Neither text sets a time limit for module B	RED Annex III
EU (RED)	Keeping technical documentation and EU DoC	10 years	After the radio equipment is placed on the market	RED Article 10(4)
EU (Decision 768/2008/EC)	Start of a newly notified body	2 weeks or 2 months	Objection window after notification, with or without accreditation	Article R23(5)
EU (MDR)	Designation of a medical device notified body	28 days	Objection window for Member States and the Commission	MDR Article 42(6)
EU (CRA)	Reporting an actively exploited vulnerability	24 hours, 72 hours, 14 days	Early warning, notification, then final report within 14 days after a corrective measure is available; applies from September 11, 2026	CRA Articles 14(2) and 71
Canada (ISED)	Wireless equipment certification by ISED	14 calendar days	Service standard, from a complete application	ISED service standards (June 2025)
Canada (ISED)	Age of the test report	12 months at most	At application	RSS-Gen section 3.4.1
PTCRB	IMEI TAC reservation	120 days	From the TAC request; revoked if the device is not certified by then	PPMD 8.6
PTCRB	NAPRD03 version	Latest or previous	Version current when test reports are uploaded; four releases a year	PPMD 11.7, 5.2
PTCRB	Delayed public listing	1 to 365 days	After certification, at the manufacturer's choice	PPMD 11.3.1.12
AT&T	Device with an unapproved module	PTCRB testing "can take 8-12 weeks", AT&T lab and field testing "can take 4-6 weeks"	Published by AT&T	AT&T Get Certified
AT&T	New eUICC through ASAP	"Approximately 8 weeks"	Published by AT&T	AT&T SIM page
T-Mobile	Technical Acceptance	"As little as five business days"	Only with all requirements met and no certification issues	T-Mobile process page
South Korea (RRA)	Registration / certification / interim certification	Immediately / 5 days / 30 days, extendable once by 15 days	From filing; time spent verifying the test report not counted for certification	RRA Notice 2026-4, Article 29
China (SRRC)	Type approval decision	15 working days	From acceptance; testing, organized by the radio administration, not counted	MIIT Order 57, Articles 9 and 10
Brazil (ANATEL)	Choice of a lab lower in the priority order	7 working days	A lab that does not quote, or cannot start, within 7 working days may be passed over	Ato 4091/2020, item 5.4
Argentina (ENACOM)	Homologation	Immediate	Once the file with the Certificate of Conformity is complete; regime applies from September 1, 2026	Res. 57/2026, Annex I
Colombia (CRC)	Mobile terminal homologation	15 working days	CRC answer time; free of charge	CRC FAQ, revision 14
Peru (MTC)	Homologation	30 working days at most	From the VUCE request	DS 001-2006-MTC Art. 13, as amended by DS 019-2019-MTC
Thailand (NBTC)	SDoC	3 days	Processing time stated by the Office of the NBTC; none stated for Class A or Class B	NBTC presentation, November 2025

Every row assumes a complete, correct file. A file returned for correction usually restarts or suspends the clock, so the practical lever is file quality, not the regulatory duration itself.

What no text fixes

These are the steps that decide the real schedule, and no regulator or scheme owner publishes a figure for them:

• Lab queue and test campaign. No regulation sets how long an EMC, LVD or radio test campaign takes. Ask each lab for a dated slot and a report delivery date in the quote.
• Retests after a failure. No published, sourced first-pass failure rate exists for EMC or radio testing; the previous version of this page quoted one without a source and it has been removed.
• TCB review. The FCC rules let each TCB set its own fees and do not set a review time. Only PAG items carry the FCC "2 to 6 weeks" description.
• Notified body examination under the RED. Needed when harmonised standards are not applied in full for Article 3(2) or 3(3) (RED Article 17), including the restricted parts of EN 18031 for 3(3)(d)(e)(f) since August 1, 2025. The body quotes its own timing.
• PTCRB overall. ptcrb.com says certification time depends on the device type and on whether results from related devices can be leveraged; the only fixed clocks are in the table above.
• Verizon and other operators not listed here. Their process documents were not used for this page; ask the operator.

Dated changes that moved a clock (2025 to 2026)

Date	Change	Source
June 2025	ISED service standards updated; wireless equipment certification remains 14 calendar days	ISED service standards
August 1, 2025	RED Article 3(3)(d)(e)(f) applies, RED 3.3 cybersecurity becomes part of the conformity assessment	Delegated Regulation (EU) 2022/30
June 15, 2026	FCC PAG list prioritizes equipment tested in Trusted Test Labs	47 CFR 2.964(a), FCC 26-28
July 24, 2026	RRA Notice 2026-4 in force, Article 29 processing times	RRA Notice 2026-4
September 1, 2026	ENACOM certification-agency regime applies in Argentina, homologation granted once the file is complete	Res. 57/2026
September 11, 2026	CRA reporting obligations (24 hours, 72 hours, 14 days) apply	CRA Article 71
October 2026	PTCRB PPMD V4.2 and NAPRD03 V6.26 published	PTCRB

Planning with these clocks

1. Sequence by file readiness, not by authority. Every administrative clock above starts at a complete file. Lock the documentation (test reports, user manual, labels) before the first filing.
2. Request the PTCRB TAC late enough. The 120-day reservation runs from the request; a TAC requested before testing is booked can lapse.
3. Watch the NAPRD03 version. With four releases a year and only the latest two accepted at upload, a slipping campaign can force a retest against a newer version.
4. Keep the FCC 30-day set-aside window in mind before shipping volume on a fresh grant (2.962(f)).
5. Keep ISED test reports fresh. A report older than 12 months at application is not accepted (RSS-Gen 3.4.1).
6. Choose SDoC or certification by the rules, not by speed. Part 15 intentional radiators such as BLE or Wi-Fi transmitters must be certified by a TCB before marketing, unless exempted (47 CFR 15.201(b)); SDoC is not an option for them.
7. Get dated quotes from labs, the TCB and any notified body, and put them in the schedule as the only source for the steps no text fixes.

See also the FCC procedure, the RED procedure, the CE procedure, CE tests and the PTCRB procedure.

Claims the texts contradict

Claim (including the previous version of this page)	What the texts say
"A TCB takes 2 to 6 weeks to review an FCC application"	No FCC rule sets a TCB review time. The "2 to 6 weeks" figure in FCC 26-28 describes PAG review only
"A complete 4G module takes 6 to 9 months of PTCRB, 5G 8 to 12 months"	No PTCRB or CTIA Certification document gives a duration. The fixed clocks are the 120-day TAC reservation and the NAPRD03 version window (PPMD 8.6, 11.7)
"PVG validation comes before TAC/IMEI allocation" and "the PVG meets bi-monthly"	The TAC is requested at the start, from certify.ptcrb.com, and reserved for 120 days (PPMD 8.6). CTIA Certification reviews requests; the PVG is a technical group that validates test cases
"30 to 40 percent of products fail EMC on the first campaign"	No source was given and none was found; removed
"In 2026 radio lab queues run 4 to 8 weeks, up to 12 for 5G OTA"	No published source; lab queues vary by lab and must come from a dated quote
"Add 30 to 50 percent margin to the best case"	No source; removed
"Carrier homologations add 4 to 12 weeks each"	T-Mobile states "as little as five business days" under conditions; AT&T states 8 to 12 weeks of PTCRB testing and 4 to 6 weeks of AT&T testing for a device on an unapproved module, while a device built on an AT&T approved module follows a three-step process at no AT&T certification cost
"eSIM agreements take 2 to 6 months"	No source. AT&T states approximately 8 weeks for a new eUICC approval under ASAP
"Module B+C adds 6 to 16 weeks under the RED"	Neither the RED nor Decision 768/2008/EC sets a duration for EU-type examination
"A C2PC takes 2 to 6 weeks"	No FCC rule sets a duration for a Class II permissive change
"An MRA lab saves 30 to 40 percent of cost"	No source; removed. Mutual recognition lets one recognised lab test for several regulators, the saving depends on the quotes
"Korea, China or Peru take weeks to issue a certificate"	The texts set 5 days (Korea, certification), 15 working days (China, after acceptance, testing excluded) and 30 working days (Peru)

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. 47 CFR Part 2, Subpart J: Equipment Authorization Procedures (eCFR, 2.926, 2.962, 2.964), FCC (eCFR) www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-2/subpart-J
2. 47 CFR 15.201, Equipment authorization requirement for intentional radiators (eCFR), FCC (eCFR) www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-C/section-15.201
3. FCC 26-28, Second Report and Order (adopted April 30, 2026), para. 65 on PAG review times, FCC docs.fcc.gov/public/attachments/FCC-26-28A1.pdf
4. FCC 26-28 final rule, 91 FR 27843 (May 15, 2026), effective June 15, 2026 except delayed paragraphs, Federal Register www.federalregister.gov/documents/2026/05/15/2026-09822/promoting-the-integrity-and-security-of-telecommunications-certification-bodies-measurement
5. OET Knowledge Database (KDB 388624 PAG, KDB 726920 confidentiality), FCC apps.fcc.gov/oetcf/kdb/index.cfm
6. Decision No 768/2008/EC, common framework for the marketing of products (Article R23), EUR-Lex eur-lex.europa.eu/eli/dec/2008/768/oj
7. Directive 2014/53/EU (RED), Articles 10 and 17, Annexes II to IV, EUR-Lex eur-lex.europa.eu/eli/dir/2014/53/oj
8. Delegated Regulation (EU) 2022/30, RED Article 3(3)(d)(e)(f), EUR-Lex eur-lex.europa.eu/eli/reg_del/2022/30/oj
9. Regulation (EU) 2024/2847 (Cyber Resilience Act), Articles 14 and 71, EUR-Lex eur-lex.europa.eu/eli/reg/2024/2847/oj
10. Regulation (EU) 2017/745 (MDR), Article 42, EUR-Lex eur-lex.europa.eu/eli/reg/2017/745/oj
11. ISED, Spectrum and Telecommunications Service Standards (updated June 2025), ISED Canada ised-isde.canada.ca/site/spectrum-management-telecommunications/en/learn-more/key-documents/spectrum-and-telecommunications-service-standards
12. RSS-Gen, General Requirements for Compliance of Radio Apparatus (section 3.4.1), ISED Canada ised-isde.canada.ca/site/spectrum-management-telecommunications/en/devices-and-equipment/radio-equipment-standards/radio-standards-specifications-rss/rss-gen-general-requirements-compliance-radio-apparatus
13. PTCRB Program Management Document (PPMD) V4.2, October 2026, PTCRB www.ptcrb.com/wp-content/uploads/2026/10/PTCRB-PPMD-V4.2.pdf
14. PTCRB Certification Program, PTCRB www.ptcrb.com/
15. AT&T, Get Certified (Get Network Ready programme), AT&T iotdevices.att.com/wp/get-certified.aspx
16. AT&T, SIM and eSIM (ASAP eUICC approval), AT&T iotdevices.att.com/wp/sim.aspx
17. T-Mobile, Start Your IoT Certification (process and FAQ), T-Mobile www.t-mobile.com/business/solutions/iot/device-certification/process
18. RRA Notice 2026-4 on Conformity Assessment of Broadcasting and Communications Equipment (Article 29), National Radio Research Agency (Korea) www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/%EB%B0%A9%EC%86%A1%ED%86%B5%EC%8B%A0%EA%B8%B0%EC%9E%90%EC%9E%AC%EB%93%B1%EC%9D%98%EC%A0%81%ED%95%A9%EC%84%B1%ED%8F%89%EA%B0%80%EC%97%90%EA%B4%80%ED%95%9C%EA%B3%A0%EC%8B%9C
19. MIIT Order 57, Radio Transmitting Equipment Management Provisions, in force July 1, 2023, State Council Gazette (China) www.gov.cn/gongbao/content/2023/content_5745288.htm
20. ANATEL Ato 4091/2020, selection, assessment and habilitation of test laboratories, ANATEL informacoes.anatel.gov.br/legislacao/atos-de-certificacao-de-produtos/2020/1452-ato-4091
21. ENACOM Resolución 57/2026, RAMATEL regulation (Boletín Oficial, February 26, 2026), Boletín Oficial (Argentina) www.boletinoficial.gob.ar/detalleAviso/primera/338750/20260226
22. CRC, mobile terminal homologation FAQ (revision 14), CRC (Colombia) tramitescrcom.gov.co/Documents/PreguntasFrecuentesHomologacionVF.pdf
23. Decreto Supremo 019-2019-MTC, amending the homologation regulation DS 001-2006-MTC, MTC (Peru) portal.mtc.gob.pe/comunicaciones/control_supervision/homologacion_equipos/documentos/DS%20019-2019%20modifica%20DS%20001-2006%20Reglamento%20Homologaci%C3%B3n.pdf
24. Overview of NBTC Standards and Conformity Assessment, Office of the NBTC, November 11, 2025 (IEEE 802.18-25/0113r0), Office of the NBTC (Thailand) mentor.ieee.org/802.18/dcn/25/18-25-0113-00-0000-overview-of-nbtc-standards-and-conformity-assessment.pdf