FCC Testing Timeline: What to Expect from Lab to Approval

How long FCC certification actually takes

The honest answer: 4 to 16 weeks for most products, measured from the day you ship samples to the lab to the day you receive your FCC grant or complete your SDoC documentation. Cellular devices with carrier approval take 6 to 9 months.

The range is wide because the timeline depends on your device complexity, whether you pass testing on the first attempt, how complete your documentation is, and how busy the lab and TCB are when you submit.

This guide breaks down each phase with realistic durations, explains what causes delays at every stage, and gives you concrete steps to compress the timeline.

The six phases

Every FCC authorization -- whether SDoC or Certification -- moves through these phases. The timeline below assumes a single-radio device (WiFi or Bluetooth) using a pre-certified module for SDoC, or a custom RF design for full Certification.

Phase 1: Pre-compliance testing

Duration: 1 -- 4 weeks

Pre-compliance testing is not required by the FCC, but skipping it is the single most common cause of blown timelines and budgets. You run informal emissions measurements on your prototype to identify problems before booking an accredited lab.

What you are checking:

• Radiated emissions from your digital circuitry (clock harmonics, switching noise, cable radiation)
• Conducted emissions on the AC power line (switching power supply noise)
• For custom RF: output power, spurious emissions, occupied bandwidth

Pre-compliance can be done in-house with basic equipment (spectrum analyzer, LISN, near-field probes) or at a pre-compliance facility for $500 -- $2,000 per day. See our EMC Pre-Compliance Testing guide for details.

If pre-compliance reveals failures, you fix them now -- on your bench, with fast iteration cycles -- instead of paying $2,000 -- $10,000 for a retest at a formal lab weeks later.

Teams that skip pre-compliance have roughly a 50% first-pass failure rate at the formal lab. Teams that invest in pre-compliance reduce that to under 10%.

Phase 2: Lab booking and sample preparation

Duration: 2 -- 6 weeks (mostly waiting)

This phase is dominated by lab queue time. Accredited test labs schedule weeks in advance, and popular labs during peak season (January -- March post-CES, July -- September pre-holiday launch) may be booked 6 -- 8 weeks out.

What happens during this phase:

• You request quotes from 2 -- 3 labs and select one
• You book a test slot
• You prepare production-representative samples (labs typically need 2 -- 3 units)
• You prepare documentation: block diagram, operational description, photos (internal and external), user manual with FCC compliance statements, label artwork
• You ship samples to the lab

How to compress this phase:

• Start requesting lab quotes while you are still in pre-compliance. Do not wait for pre-compliance to finish.
• Have documentation 80% complete before booking the lab. The documentation checklist is known in advance -- there is no reason to start it the week before testing.
• Use a lab that also operates as a TCB (TUV SUD, Intertek, Bureau Veritas, Nemko). This eliminates the lab-to-TCB handoff in Phase 5.
• Avoid peak season if your launch timeline permits.

Phase 3: Formal testing

Duration: 3 -- 10 days (depending on device type)

This is the actual lab time. Your device is tested in an accredited facility against the applicable FCC standards.

SDoC path (unintentional radiator or host with pre-certified module)

Cost: $800 -- $5,500 depending on whether the product has a pre-certified module that requires RF exposure re-evaluation.

Certification path (custom RF, single-band)

Cost: $8,000 -- $20,000.

Certification path (multi-radio or cellular)

Cost: $15,000 -- $200,000 for complex multi-band cellular devices.

Phase 4: Test report preparation

Duration: 1 -- 3 weeks

After testing completes, the lab engineer writes the formal test report. This is not instant. The report must include measurement data, test configurations, equipment calibration records, photos, and a determination of pass/fail against each applicable limit.

For SDoC, this report is the end of the road -- once you have it, you self-declare compliance and your product is authorized. There is no Phase 5 or 6.

For Certification, the test report feeds into the TCB application package.

How to compress this phase:

• Ask the lab for their report turnaround time before booking. Some labs deliver in 3 -- 5 business days; others take 2 -- 3 weeks.
• If you need the report faster, most labs offer expedited report preparation for a surcharge (typically +25 -- 50%).
• Ensure your documentation package (photos, manuals, block diagrams) is complete before testing starts. Missing documentation after testing is a common cause of report delays because the lab engineer cannot finalize the report without it.

Phase 5: TCB review (Certification path only)

Duration: 1 -- 4 weeks

The TCB reviews the complete application package: test report, internal/external photos, label artwork, block diagram, operational description, user manual, and RF exposure evaluation. The TCB verifies that the test data demonstrates compliance with the applicable rule parts.

If the TCB has questions or finds deficiencies, it issues a review query. Each query-and-response cycle adds 3 -- 7 days. Common query triggers:

• Incomplete or inconsistent internal photos (most common)
• Label artwork that does not meet 47 CFR 2.925 requirements
• Missing or incorrect RF exposure evaluation
• Test report gaps (untested configurations, missing spurious measurements)
• Operational description that does not match the test setup

How to compress this phase:

• Use a lab that is also a TCB. The lab engineer who ran the tests prepares the application -- there is no information handoff and the TCB reviewer has direct access to the test engineer.
• Get your documentation right the first time. TCB review queries are the second most common cause of timeline delays (after test failures). A complete, accurate application sails through review in 5 -- 7 business days.
• Consider paying for expedited TCB review (+50 -- 100% surcharge) if your launch date is fixed.

Phase 6: Grant issuance (Certification path only)

Duration: 1 -- 3 days

Once the TCB approves the application, the FCC grant is issued and your FCC ID appears in the public EAS database. This step is essentially administrative and happens quickly.

Your product is now authorized to be marketed and sold in the United States.

Total timeline summary

"Best case" assumes pre-compliance was done, documentation is complete, the lab has immediate availability, testing passes on the first attempt, and TCB review has no queries.

"Worst case" includes a test failure with board re-spin, lab rebooking, retesting, and TCB queries requiring multiple response cycles.

What causes delays

Test failures (adds 4 -- 12 weeks)

This is the largest single source of timeline blowout. Roughly 50% of consumer electronics products fail EMC testing on their first formal lab attempt when no pre-compliance was done. A failure triggers:

1. Lab issues preliminary fail results (1 -- 2 days)
2. Your engineering team diagnoses the root cause (1 -- 2 weeks)
3. You implement a fix (PCB re-spin: 2 -- 4 weeks; shielding/filtering fix: 1 -- 2 weeks)
4. You rebook the lab (2 -- 4 weeks queue time)
5. Retest (2 -- 5 days)
6. New report (1 -- 2 weeks)

A single failure-and-retest cycle adds 4 -- 12 weeks and $2,000 -- $15,000 to your project. If the fix requires a board re-spin, it is on the longer end.

Incomplete documentation (adds 1 -- 4 weeks)

TCB review queries are the second most common delay. Each query requires a response from you (or your lab), and the TCB re-reviews after each response. Two rounds of queries can add 2 -- 4 weeks.

The documentation that most often triggers queries:

• Internal photos that are blurry, unannotated, or do not show all shielding and ICs
• Label artwork with incorrect FCC ID format or missing compliance text
• RF exposure evaluation that uses incorrect separation distances or omits simultaneous transmission analysis
• User manual missing the required Part 15 compliance statement from 47 CFR 15.19

Lab queue congestion (adds 2 -- 6 weeks)

Peak booking seasons are January -- March (post-CES rush) and July -- September (pre-holiday product launches). During these windows, popular labs may be booked 6 -- 8 weeks out. Off-peak, you can often get a slot within 2 -- 3 weeks.

Multiple test configurations (adds 1 -- 2 weeks)

If your product ships with different power supplies, cable types, or operating modes, the lab may need to test each configuration separately. Each additional configuration adds a partial day of testing and increases report preparation time.

How to accelerate the process

1. Invest in pre-compliance testing. This is the highest-ROI step you can take. A $500 -- $2,000 pre-compliance session can prevent a $5,000 -- $30,000 failure-and-retest cycle. See our EMC Pre-Compliance Testing guide.

2. Prepare documentation early. Start your internal photos, block diagram, operational description, label artwork, and user manual as soon as your design is frozen. Do not wait until the lab asks for them.

3. Use a combined lab/TCB. Organizations like TUV SUD, Intertek, Bureau Veritas, and Nemko run both test labs and TCBs. Using one organization eliminates the 3 -- 7 day lab-to-TCB handoff and often reduces total review time.

4. Book the lab before pre-compliance is complete. Lab slots fill up. Start the booking process in parallel with pre-compliance testing. If pre-compliance reveals a problem, you can push the lab date back. If it does not, you have not lost weeks waiting for a slot.

5. Use a pre-certified module. If your product includes WiFi, Bluetooth, or another radio technology, using a pre-certified module shifts you from the Certification path (6 -- 16 weeks) to the SDoC path (3 -- 6 weeks). The module vendor has already done the hard work. Cost savings: $5,000 -- $15,000. Time savings: 4 -- 10 weeks.

6. Run FCC and ISED together. ISED (Canada) accepts FCC test reports for most device types under the US-Canada MRA. Adding ISED to your FCC campaign costs $1,000 -- $3,000 incremental with zero additional testing time. Always bundle them.

7. Freeze your design before testing. Any hardware change after testing starts risks invalidating results. Lock your BOM, PCB layout, firmware version, enclosure design, and cable configurations before shipping samples to the lab.

Timeline planning checklist

Use this as a rough project plan. Adjust durations based on your device complexity.

For a product using a pre-certified module on the SDoC path, the realistic timeline from "we are ready to test" to "we can ship" is 6 -- 8 weeks with proper planning. For a custom RF design on the Certification path, plan for 10 -- 14 weeks.

Build 2 -- 4 weeks of buffer into your launch schedule for test failures or documentation queries. If you do not need the buffer, you ship early. If you do need it, you avoid slipping your launch.