hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 7.6ISO/IEC 17025:2017 · Control the work from request to report

ISO/IEC 17025 clause 7.6: explain measurement uncertainty

Measurement uncertainty describes the uncertainty associated with a measurement result. ISO/IEC 17025 clause 7.6 requires laboratories to identify relevant contributions and evaluate them appropriately. The purpose is to understand the result well enough for its intended use, not to add an unexplained number to a report.

What does the clause require?

Identify significant sources of uncertainty, including sampling where relevant, and use suitable analysis. A laboratory performing calibrations must evaluate uncertainty for its calibrations, including calibration of its own equipment. A testing laboratory must also evaluate uncertainty, with appropriate estimation where the method prevents a rigorous evaluation.

The standard recognises established methods and circumstances where previously determined uncertainty can remain applicable if critical influences are controlled. This does not mean copying an uncertainty value indefinitely. The laboratory needs to understand the basis and whether the actual method, range and conditions remain within it.

A practical sequence for the laboratory

Sterling recommends beginning with the result being reported and the method producing it. Identify the quantities, equipment, references, preparation and conditions that can influence it. Decide which contributions are significant and how they will be evaluated. The appropriate technical approach depends on the measurement; there is no useful universal budget for every laboratory.

Use evidence appropriate to the contribution, such as relevant calibration information, method performance or repeat measurements. Document the reasoning and limitations so another competent person can understand it. Review the evaluation when method changes or performance evidence suggest the previous basis is no longer suitable.

Connect this work to reporting and conformity decisions. The uncertainty evaluation under 7.6 and the reporting requirements under 7.8 are related but different responsibilities. An internal calculation does not establish that a customer received the information needed to interpret a result.

ISO/IEC 17025 consulting & certification support

Get clause 7.6 right the first time — with a global leader in ISO/IEC 17025 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Why clause 7.6 matters to the laboratory

Uncertainty is how a laboratory tells the customer how far a result can be relied on. Without it, a number looks more exact than it is, and decisions that depend on it, such as accepting a batch or approving a repair, may be taken on false confidence. A properly built evaluation also helps the laboratory itself: it shows which parts of the process contribute most doubt, so improvement effort goes where it matters. It becomes crucial near specification limits, where the margin for a wrong conclusion is small. Laboratories that treat the work as a shared, understood analysis, not a number borrowed from elsewhere, find that questions from customers and assessors become easier to answer.

How to implement clause 7.6

Build the evaluation from the actual measurement process, then keep it alive. Start with one high-volume result and extend from there, so the team learns the approach on something familiar.

  1. Choose one reported result and describe the measurement process behind it in plain steps.
  2. List the influences at each step, such as the reference, the instrument, preparation, environment, the operator and sampling where relevant.
  3. Decide which influences are significant, and what evidence will quantify each: calibration data, repeat measurements, validation results or technical knowledge.
  4. Combine them with a method suited to the case and record assumptions, so another competent person can follow the reasoning.
  5. State where the evaluation applies: method, range, conditions and the people allowed to use it.
  6. Set review triggers, such as a method change, new equipment or monitoring data that no longer match the evaluation.
  7. Link the outcome to contract review and reporting so the customer receives uncertainty information that matches the agreed use of the result.

Calibration example: uncertainty beyond the reference certificate

Illustrative example 1

A hypothetical laboratory calibrates a customer's measuring device using a suitable reference. Copying the reference's reported uncertainty as the entire uncertainty of the calibration would overlook other potentially significant influences from the laboratory's actual work.

Illustrative example 2

The team examines the method, equipment behaviour, conditions and relevant observations to identify the complete basis appropriate to that activity. It retains the evaluation and checks that the reported information matches the work. The example illustrates the reasoning needed; it is not a numerical calculation or a prescribed list of contributions for every calibration.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 7.6 alive in Effivity

Record what you decided under clause 7.6, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO/IEC 17025 programme.

Construction materials example: variation in the actual test

A materials testing laboratory has an established uncertainty evaluation, but a new preparation arrangement changes how specimens are handled. Management wants to keep the old figure to avoid delaying customer work. The technical question is whether the earlier basis still represents the method's performance.

The laboratory evaluates the change and any significant contributions, updates the basis where necessary and checks associated reporting. This fictional scenario shows why uncertainty is connected to operational changes. A value is not reliable merely because the same number appeared on last year's report.

Manufacturing example: a result near a specification limit

A manufacturer asks its laboratory whether a component passes a limit. The measured value is close to the boundary. The laboratory must distinguish the numerical result from a conformity conclusion and apply the relevant agreed or prescribed decision rule.

Uncertainty informs the technical interpretation and associated decision risk. The laboratory should not invent an acceptance rule after seeing whether the result is commercially convenient. Discuss the reporting and decision needs during contract review, then retain a consistent basis for the conclusion.

Evidence that makes the evaluation understandable

What counts as evidence

Useful evidence includes the intended measurement, evaluated contributions, data sources, method of analysis, assumptions, relevant conditions and review decisions. Where a prior evaluation continues to be used, evidence should support the control of critical factors and continued suitability.

IT tools can organise calculations, but formulas and transfers require appropriate checking. A software-generated uncertainty table does not establish that all significant influences were considered. Limit access to uncontrolled changes and retain the basis for the current version.

Explore each numbered part

7.6.2 · evaluate uncertainty for every calibration

Evaluate measurement uncertainty for all calibrations performed by the laboratory, including calibration of its own equipment. This guide explains how reference uncertainty, method performance and other significant influences contribute to the result, with examples showing why copying a reference certificate's uncertainty does not describe the complete calibration activity.

7.6.3 · evaluate uncertainty in testing

Understand how testing laboratories evaluate measurement uncertainty, including methods that do not permit a rigorous numerical evaluation. This guide explains estimation based on technical principles or experience, the qualified provisions for recognised methods and controlled factors, and how uncertainty affects interpretation, customer needs and statements of conformity.

Common nonconformities with clause 7.6

Reviewers meet a familiar set of problems when they look at uncertainty work.

  • The reported uncertainty is lifted from a reference certificate and presented as the whole answer.
  • An old evaluation is reused after a change of method, equipment or material with no review.
  • Significant contributions, such as sampling or environment, are left out because data are hard to collect.
  • Calculation spreadsheets are uncontrolled, so formula changes go unnoticed.
  • Only senior staff understand the evaluation, and the people using it cannot explain its limits.

Frequently asked questions

Is uncertainty the same as a mistake?

No. An uncertainty evaluation addresses the measurement result and the available knowledge about it. Errors, invalid work or uncontrolled mistakes need their own investigation and action; they should not be hidden inside an enlarged uncertainty figure.

Must uncertainty be recalculated from scratch for every result?

Not in every case. Where an established evaluation remains applicable and relevant influences are controlled, it may support subsequent work. The laboratory needs a technically defensible basis for that decision.

Can we use another laboratory's budget?

It may help identify questions to examine, but it does not demonstrate your method, resources or conditions. Establish and maintain evidence appropriate to your own activity.

Connect uncertainty with defensible laboratory results

Sterling can help identify uncertainty-related gaps within a scoped laboratory implementation and accreditation preparation programme. Effivity ISO & GRC automation software can support agreed evidence and review workflows; it does not replace technical evaluation. Discuss your testing or calibration scope, and use ISO/IEC 17025 awareness training to build the team's understanding of the wider responsibilities.

All ISO/IEC 17025 clauses · Parent clause guide

Source basis and reading note. This is original practical guidance for ISO/IEC 17025:2017. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide accreditation for a defined laboratory scope outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO/IEC 17025 in your organisation.