People ask me to recommend labs. I can't.

Lab A is solid on Bluetooth. Lab B excels at automotive EMC. Give them a different category – they could trip as badly as anyone. But after following over 100 projects, some patterns are consistent.

1. Certificates on the Wall Don't Mean Much

·Ignore the framed logos on the wall. CNAS, CMA, A2LA, NIST‑VLAP (formerly NVLAP) – you can look them up on official websites. The question isn't whether they have them – it's whether the specific standards and specific test items you need are listed in their scope annex.

·Every CNAS lab's scope annex lists exactly what they're accredited for – which standards, which test items, up to what parameters. Both "EMC labs" – Lab A's radiated emissions only goes to 6 GHz – Lab B goes to 18 GHz. Your product needs testing at 12.5 GHz – Lab B can issue a CNAS‑stamped report – Lab A cannot.

·Check item by item. If a test item isn't in the accredited scope – the report issued is not CNAS‑accredited – it's just a test report. Some clients and certification bodies do not accept such reports. Check before submitting samples.

·Certification authorisations work the same way. FCC – check the FCC database for lab listing. If they're listed, they're an FCC‑ATL recognised lab. Report format compliant – any TCB will accept it. Claims of "exclusive TCB channels" – take with a grain of salt. CE‑RED NB projects – check NANDO for Notified Body authorisation. Korea KC – check if it's an RRA‑designated or registered test lab – both can do RF – it's not only the designated ones.

  2. People Matter More Than Chambers

Chambers – R&S or ETS? Receivers – ESR or FSV? The hardware gap between mainstream labs is shrinking. The price difference is in the engineers.

How many projects have they done in your category? How many remediation traps have they hit? Have they worked with your chip platform? You'll find out when things go wrong. Good ones can point to the root cause. Bad ones – hand you a spectrum plot and tell you to figure it out.

Case in point: a 4G T‑Box with a 6 dB exceedance around 700 MHz – wide, flat noise – client confused. An engineer with automotive experience spotted it immediately: DC‑DC converter switching noise coupled through the antenna feedline – add a common‑mode choke at the antenna input – first‑pass fix. Another engineer who'd never done automotive – would have you re‑route PCB traces – consumer‑electronics thinking – rounds and rounds, time gone.

When interviewing, ask directly:

·"How many similar projects have you done in the past year?"

·"Have you worked with this exact chip platform?"

·"Have you encountered similar spectrum signatures?"

Look for specifics – "when, which platform, how many units" – those are credible. "We have extensive experience" – meaningless.

  3. Scheduling and Communication

Scheduling can vary enormously. Some labs give you exact dates – sample receipt, test start, report issue. Others say "two weeks" – and a month later you're still waiting. Choose a lab with a scheduled system. Before submitting samples, get a firm timeline from the project manager – don't accept "I'll expedite for you."

Communication style also affects timelines. All‑English emails, two‑day reply times – fine for standard processes. For complex projects requiring frequent discussion – domestic labs where you can directly chat with the test engineer in Chinese – direction set before entering the chamber – turnaround can be several times faster.

  4. "One‑Stop Shop" – Usually a Trap

"Full category coverage" – Bluetooth, Wi‑Fi, FCC, CE, in‑vehicle – all in one. One lab doing everything across all categories – physically impossible.

Stick to specialists:

·Bluetooth BQB – find labs with ATL accreditation. (BQC is an advisor – people are people, labs are labs – mixing them up gets you the wrong contact.)

·Automotive EMC – find labs that have run tests against your target OEM's test specifications. OEMs don't issue lab certifications – they just know who's actually done it.

Multi‑country certification – find someone who can coordinate. One T‑Box needing FCC + ISED + CE‑RED + UN‑R144 – which data can be reused, how to test once without repeated sample shipments – you need someone to manage that. It doesn't have to be one lab for everything – but you need someone who knows who's doing what and how data flows.

  5. Low Prices – What's Behind Them?

If test fees are half the market rate – something is probably wrong.

Chamber NSA (Normalised Site Attenuation) not meeting requirements – forcing distance‑conversion reports – I've seen it more than once. The standard does allow different distances with far‑field inverse‑ratio normalisation – provided the site is qualified. The trap isn't the 3‑metre method – it's the site.

"All‑in‑one fixed price" sounds convenient. Remediation and retesting – mostly not included. Before signing, ask:

·Retesting charges?

·Re‑queuing for chamber time after fixes?

·Who pays if samples are damaged?

Agent fees, sample shipping, translation, supplementary testing for standard updates – unlisted items add up. Reputable labs itemise them. If they don't, ask.

  6. Before Submitting Samples

·Write a clear spec sheet. RF parameters, antenna, power supply, operating temperature – these determine which standards and configurations apply. Clear specifications reduce errors.

·Request the Test Plan in advance. Before submission, ask the lab for the test plan – which tests, which standards, which configurations – listed. If anything is unclear, discuss it before testing starts.

·Pre‑testing is worth it. If budget allows, do a pre‑scan before formal certification.

Warning: for some overseas certifications, pre‑test samples must have the same hardware and firmware versions as formal samples – under some rules, pre‑test samples cannot be directly used as formal submission samples – check before sending. Pre‑testing data is not formal data – but it catches failure points early.

·Prepare test firmware in advance. Production firmware runs in user mode – no continuous transmit/receive. Labs need test mode – AT commands for band, power, modulation. Some RF chips only support continuous transmission in engineering debug mode – production firmware can't enable it – you'll need a separate compilation. This trap catches many on sample‑submission day.

·Don't forget accessories. Chargers, cables, antennas – all affect EMC and RF. If you change any RF or EMC‑related component – antenna, PCB, firmware parameters – most certifications require assessment and filing – regardless of how "minor" the change seems.

Accreditation is the baseline. But whether you pass – depends on the people.

For third‑party lab selection, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.