Measurement uncertainty is the clause in ISO/IEC 17025 that trips up more laboratories than any other. It's not optional, and a rough estimate copied from a manufacturer's spec sheet won't satisfy an assessor. Here's what the standard actually requires, and where I see labs go wrong on this most often.
What the standard actually requires
ISO/IEC 17025:2017 requires every testing and calibration laboratory to identify the contributions to measurement uncertainty for each method it uses, and to evaluate them using a recognised approach. Clause 7.6 doesn't mandate a single calculation method — the GUM approach is common, but it isn't the only acceptable one. What it does mandate is that the figure you report is defensible: you can show where each contributing factor came from, and you haven't quietly left anything material out. A number lifted from a calibration certificate without checking how it actually applies to your process won't survive an assessor asking you to walk through it.
Where labs get caught out
In my experience, the most common finding isn't a missing uncertainty budget — it's one that no longer matches reality. I've seen budgets built years ago and never revisited when equipment was replaced, a method was revalidated, or a new technician took over a test. Assessors will ask you to produce the uncertainty budget for a specific test on a specific day, then trace each input back to a calibration certificate, repeatability data, or a reference material certificate. If you can't do that walk-through live, in the room, a polished spreadsheet on file won't save you. The paperwork has to reflect what actually happens on the bench, not what it looked like when it was first written.
Reporting it, not just calculating it
Calculating the uncertainty is only half the job. Clause 7.8.3 requires you to report it when it's relevant to the validity of the result, when a client asks for it, or when it affects conformity to a specification. Too many labs calculate uncertainty once a year to satisfy the accreditation file, then issue test reports that never mention it. If a client is using your result to make a pass or fail decision against a tolerance, the uncertainty has to be considered as part of that decision, not filed away separately. That link between calculation and reporting is where assessors increasingly focus their questions.
Keeping the budget current
An uncertainty budget is not a one-off exercise. It needs reviewing whenever something changes that could affect it — new equipment, a method amendment, a change to the range you test, or a different person doing the work. Build that review into whatever change-control process you already run, rather than treating it as a separate annual task that quietly slips. The labs that manage this well work from a short trigger list: equipment change, method change, a significant proficiency testing result, or a client complaint about a result near a limit. Any one of those should prompt someone to check whether the existing figures still hold up.
Where decision rules fit in
One area that still catches labs out is the decision rule — the method you use to state conformity when a result sits close to a specification limit. Clause 7.8.6 requires you to document the decision rule you've applied and to have agreed it with the client where relevant. This only works if it's built on the uncertainty figure, not bolted on afterwards. If your reports state pass or fail without any visible link to how uncertainty was handled at the boundary, that's a gap worth closing before an assessor finds it for you.
If you're due a surveillance visit, pull three uncertainty budgets at random and check you can trace every input back to a source document, then check your test reports actually reference that uncertainty where it's relevant. That's a fair approximation of what an assessor will do on the day, and it's the quickest way to find out whether your paperwork and your practice have drifted apart.
Ready to talk about your business?
Book a free, no-obligation call. We will tell you exactly what certification would involve for your size, sector, and starting point.