Testing Lab vs. Calibration Lab: What's the Difference in Scope?

Testing lab vs calibration lab: ask a quality manager which one their instrument supplier actually is, and you’ll often get a shrug. That confusion has a real cost: instruments get sent to the wrong provider, audits stall, and certificates come back listing the wrong kind of data entirely. ISO/IEC 17025 governs both lab types, but their accredited scopes are built to answer two different questions. Here’s where they overlap, where they split, and how to tell which one you actually need.

A calibration lab’s accredited scope lists a measurement quantity, a range, and a Calibration and Measurement Capability (CMC) uncertainty for every activity it’s approved to perform. In 2024, ILAC’s guidance on describing scopes of accreditation confirmed this structure applies globally (ILAC-G18:01/2024). That means two calibration labs holding the same accreditation can still have different capabilities depending on what’s actually published in their scope document.

This is why Micro Precision’s ISO/IEC 17025 accreditation listings, broken out by discipline and location, matter more than the accreditation logo itself. The certificate tells you a lab is competent; the scope tells you at what range and uncertainty. A calibration certificate always documents as-found and as-left readings against a traceable reference, satisfying NIST’s definition of metrological traceability — an unbroken, documented chain of comparisons back to a national standard.

A testing lab’s scope lists the test methods and standards it’s approved to run, not a measurement range. Testing scopes rarely quantify uncertainty the way calibration scopes do, since the deliverable is a compliance result rather than a traceable measured value — a distinction ISO’s own ISO/IEC 17025 overview draws directly. A testing lab still has to estimate uncertainty where it affects the validity of the result, but it isn’t reporting a calibrated value against SI units.

The clearest way to see the split is side by side. As of the 2017 edition of ISO/IEC 17025, both lab types share one standard, but their scope documents, deliverables, and reporting obligations diverge sharply once you look at what’s actually written on the certificate.

A calibration certificate is only as useful as the scope behind it. If a lab’s CMC uncertainty at your instrument’s operating range is wider than your process tolerance, the calibration is technically accredited but practically useless for your application — a gap the A2LA FAQ addresses directly for anyone vetting a provider’s actual capability rather than just its certificate number.

Most instruments in a regulated environment need both services at different points in their life. A new pressure transducer gets tested against its manufacturer spec before it enters service, then calibrated on a recurring interval to confirm it still reads accurately. Micro Precision’s instrument calibration services, spanning electrical, mechanical, optical, RF, and thermodynamic disciplines, cover the recurring side; a separate qualification test typically covers the initial acceptance side.

Interval selection matters as much as picking the right lab type. A calibration performed too infrequently can let a drifting instrument produce bad data for months before anyone catches it, which is exactly why Micro Precision’s risk-based calibration interval guide treats interval-setting as its own decision, separate from choosing between testing and calibration in the first place.

The testing lab vs calibration lab distinction comes down to one thing: a calibration lab hands you a traceable number and its uncertainty, while a testing lab hands you a compliance result. Both operate under ISO/IEC 17025, but that shared standard doesn’t make their scopes interchangeable. Getting this right before you ship an instrument saves a rejected certificate, a stalled audit, or a repeat shipment later.