Skip to content

Understanding detection limits (batch 2 guide 13)

aBy admin·
The short answer

The short answer is that discipline beats intensity: a planned routine with written criteria and independent verification outperforms last-minute heroics every time. This guide on understanding detection limits focuses on EU-bound packaging: A lab result reading not detected never means zero — it means below what the method can see. Buyers who misread detection limits as purity certificates approve materials carrying undetected loads right up to the method's blind spot.

Key takeawaysStart from the conclusion: detection and quantification limits frame every low-level result: below detection the substance may or may not be present; between detection and quantification it is present but unmeasurable; only above quantification does the number carry full weight is decided by preparation and evidence discipline, not by effort on the day. Acceptance sampling inspects a statistically drawn portion of a lot instead of every unit, with accept and reject counts fixed by the chosen plan before anyone visits the factory. [1] · In practice this comes down to working habits: Challenge methods whose limits sit too close to the threshold, since the blind band then covers the decision zone. Read every not-detected result together with its stated limit and compare that limit against the regulatory threshold. · The expensive mistake runs the other way: Filing not-detected reports without checking limits lets high-limit methods certify what they cannot see. Like any factory acceptance test, a pre-shipment visit only works when the pass criteria were written down and agreed before production finished. [2] · Remember the standing rule behind all of this: The compliance question is never just detected or not — it is whether the method could have seen a violation at the threshold that matters.

Packaging compliance work for the EU market sits at the intersection of material science and paperwork: substance restrictions, labeling duties, and technical documentation all have to line up before goods ship. Testing answers the material question, while declarations, bills of materials, and report traceability answer the documentation question.

A lab result reading not detected never means zero — it means below what the method can see. Buyers who misread detection limits as purity certificates approve materials carrying undetected loads right up to the method's blind spot. Because packaging touches every SKU a buyer ships, small efficiencies in test planning compound fast — one shared sample set, one coordinated lab slot, one coherent report package per season. The articles in this series treat testing as a managed routine rather than a last-minute scramble before the vessel sails.

For packaging programs, that means mapping every component against the current substance rules, keeping sample traceability airtight from factory floor to lab bench, and scheduling retests around real change triggers instead of arbitrary dates. The sections below turn that conclusion into working detail, from preparation through evidence to follow-up.

Why understanding detection limits deserves its own routine

Detection and quantification limits frame every low-level result: below detection the substance may or may not be present; between detection and quantification it is present but unmeasurable; only above quantification does the number carry full weight. Compliance judgment lives inside those bands.

Illustration: Why understanding detection limits Decorative illustration for the section "Why understanding detection limits"; visual only, carries no data.

In day-to-day terms that means the following. Read every not-detected result together with its stated limit and compare that limit against the regulatory threshold. Require quantification-level numbers wherever compliance math — sums, averages, migration totals — depends on the value. Challenge methods whose limits sit too close to the threshold, since the blind band then covers the decision zone. For packaging programs, that means mapping every component against the current substance rules, keeping sample traceability airtight from factory floor to lab bench, and scheduling retests around real change triggers instead of arbitrary dates.

Like any factory acceptance test, a pre-shipment visit only works when the pass criteria were written down and agreed before production finished. [2]

Putting independent verification into the plan

Buyers handling EU-bound packaging usually set this up as part of the booking routine rather than a separate project. Many buyers ask UTS to carry out the visit as a fully independent party, so findings are judged against the criteria rather than the relationship.

That single arrangement removes most of the failure modes described in this guide. Like any factory acceptance test, a pre-shipment visit only works when the pass criteria were written down and agreed before production finished. [2]

Reading the field signals

Result wordingWhat it actually meansBuyer action
Not detected (limit stated)Below method visibility, not absentCheck limit vs threshold
Trace / estimated valuePresent but not quantifiableJudge conservatively, retest sensitively
Number above limitQuantified with stated uncertaintyUse in compliance math with care
Pass at high limitBlind band covers thresholdDemand sensitive retest
Pass at low limitReal margin demonstratedFile with confidence
Limits unstatedResult uninterpretableReturn report for completion

Read this way, the table is a field manual rather than a reference card. Like any factory acceptance test, a pre-shipment visit only works when the pass criteria were written down and agreed before production finished. [2]

Illustration: Reading the field Decorative illustration for the section "Reading the field"; visual only, carries no data.

A working sequence for understanding detection limits

  1. Extract limitsPull detection and quantification limits for each parameter from the report, not just the verdicts.
  2. Compare to thresholdsCheck each limit against its regulatory threshold to size the blind band.
  3. Judge fitnessReject methods whose blind band covers the decision zone and request a more sensitive method.
  4. Handle traces honestlyReport between-limit traces as present-but-unquantified and judge them conservatively.
  5. Specify methods upfrontWrite required sensitivity into the test request so limits arrive fit for purpose.

Sources

  1. Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
  2. Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.

Frequently asked questions

What is the difference between detection and quantification limits?

Detection is the lowest level the method can distinguish from background; quantification is the lowest level it can measure reliably. Results between the two indicate presence without a trustworthy number.

Is not detected the same as compliant?

Only when the detection limit sits comfortably below the regulatory threshold with proper margin. A not-detected at a limit above the threshold proves nothing about compliance.

Why do limits differ between labs?

Equipment sensitivity, sample preparation, matrix interference, and method choice all shift limits. That is why buyers specify required sensitivity instead of assuming all reports see equally far.

What should buyers write into test requests?

Named methods or minimum sensitivity requirements per parameter, so the lab's limits arrive matched to the decision. Sensitivity specified late is sensitivity renegotiated expensively.

The Atelier — Lyon, since 2009

Each piece drawn, cut, and finished by hand.

Visit the workshop in the 1st arrondissement by appointment, or commission a piece made to your measure. Six-week lead time, lifetime guarantee on every numbered edition.

Begin a Bespoke Commission →