Each one answers a different question
A pre-compliance test asks: is there a risk of failing, and where? A certification test asks: does it formally comply with the requirements of the standard? Confusing them leads to expecting an official result from a test that cannot give one, or to spending a formal test on a design that is not ready yet.
Pre-compliance
- It is done during design and with prototypes, at in-house facilities or at a laboratory.
- It uses lower-cost instruments and less strict conditions.
- It allows iteration on the same day: measure, modify, measure again.
- Its uncertainty is greater, so it demands a margin relative to the limit.
Certification
- It is done on a representative product, at a validated site and with calibrated, traceable instruments.
- It follows the method of the standard in detail, with defined detectors and configuration.
- It produces a report with uncertainty and test conditions.
- Its result supports the declaration of conformity, in accordance with the applicable market requirements.
What to expect from each
| Aspect | Pre-compliance | Certification |
|---|---|---|
| Goal | Discover and correct | Demonstrate conformity |
| Environment | Variable | Controlled and validated |
| Required margin | Wide | Whatever the standard sets |
| Timing | During development | With a stable design |
When one cannot replace the other
Passing a pre-compliance test does not guarantee passing the formal one: differences in environment, configuration or method can cost a few decibels. That is why a margin is left. Nor is it advisable to skip pre-compliance: a failure in the formal test forces the cycle to be repeated, with the cost of laboratory time and design changes.
In practice, the most efficient order is continuous pre-compliance during design and a formal test once the product is frozen.