Document control is one of the most common sources of ISO/IEC 17025:2017 nonconformities, and how a finding gets classified changes what you need to do about it.
An obsolete document sitting unused at the bench is usually a document control issue under clause 8.3, closed out through the clause 8.7 corrective action process. If that document was actually used to carry out work, it also becomes nonconforming work under clause 7.10, because the validity of the output is now in question.
A correction fixes the specific instance found; a corrective action fixes the cause so it doesn't happen again. ISO 17025 itself doesn't classify findings as major or minor; that call comes from your accreditation body.
When a document control problem arises during assessment, most labs already know roughly what happened. An old procedure was sitting at the bench, or a form went into use without proof that it was signed off.
What's less clear, even to experienced quality managers, is what to do about it once it's written up. Is it nonconforming work, a nonconformity, or both? And does it need a full corrective action?
These distinctions matter because ISO/IEC 17025:2017 treats them differently, and closing a finding with the wrong process can itself become a question at your next assessment.
A nonconformity is the failure to meet a requirement, whether that requirement comes from the standard itself or from the laboratory's own documented management system.
That second part is easy to overlook. If your own SOP requires a review every two years and it's a year overdue, that's a nonconformity against your own system, even though the standard doesn't specify a two-year interval anywhere. A nonconformity can also arise from a procedure that was followed correctly, but turns out not to be fit for its purpose.
Nonconformities can be identified during an internal audit, a management review, a customer complaint, day-to-day work, or an external assessment by a body such as UKAS in the UK, or A2LA, ANAB or NVLAP in the US. None of these routes is more official than another. Regardless of how it's spotted, the standard expects a defined response rather than an ad hoc fix.
It depends on what was found and how it affects the work.
Clause 7.10 covers a specific piece of laboratory activity that didn't meet the lab's own procedure or an agreed customer requirement, such as a calibration performed on an instrument that had passed its calibration due date. The lab has to react. It has to decide whether the work is affected, whether it needs to be stopped, and whether a customer needs to be informed.
Clause 8.7 covers the response once a nonconformity has been identified, regardless of its source. This is the clause that sets out the process of correcting what was found and deciding whether the underlying cause needs to be eliminated.
A document control failure can trigger clause 7.10 or 8.7, or both. An obsolete SOP found unused at a bench is usually a document control issue under clause 8.3, handled through the clause 8.7 process. A calibration actually carried out against that SOP's outdated acceptance criteria also becomes nonconforming work under clause 7.10, because the validity of that specific output is now in question. The distinction matters because it changes what you need to demonstrate to close the finding.
Six patterns come up repeatedly in document control findings raised at assessment:
Staff working from a printed copy or a locally saved file after it's been superseded.
Custom calculation tools or data-entry templates with no version history, change tracking, or formal validation.
A document or record with no proof of who reviewed or authorised it, or when.
Worksheets or logs with missing details, such as environmental conditions or equipment identification, that are needed to repeat or evaluate the work.
Manufacturer manuals, published standards or client methods used without checking their current status.
A correction made with no indication of what was changed, when, or by whom, or one that obscures the original entry.
Our complete guide to ISO/IEC 17025 document control covers what a compliant system looks like for each. The rest of this article focuses on what to do once a finding has been raised.
A correction fixes the specific instance found. A corrective action addresses why it happened so that the same failure doesn't recur elsewhere.
For an obsolete SOP, the correction is straightforward. You remove the outdated copy and replace it with the current version. But that doesn't look at why it was there in the first place. The corrective action does. Was the withdrawal process not followed on this occasion, or is there no reliable way to remove superseded copies at all? If it's the latter, the fix is to build a check into the release process rather than just removing this one document.
Not every nonconformity needs a full corrective action. Clause 8.7.1 requires the lab to evaluate the need for action to eliminate the cause, and clause 7.10.3 requires corrective action where nonconforming work could recur. A genuinely isolated instance may only require a correction.
ISO/IEC 17025:2017 doesn't itself define nonconformities as major or minor. Accreditation bodies grade findings under their own procedures, and the terminology varies: UKAS raises mandatory or recommended improvement actions, A2LA cites deficiencies, and some bodies use major and minor categories.
Generally, these bodies treat a finding as more serious when it directly affects confidence in the validity of the results, when several related minor findings point to the same cause, or when it repeats a previously raised finding. The exact criteria and timescales vary by body, so check your own accreditation body's documented procedure rather than assuming a fixed rule applies.
Clause 8.7.1 sets out the steps for closing out an ISO 17025 document control nonconformity. Here they are applied to the obsolete SOP example:
Contain the problem. Remove the obsolete copy, and check whether any recent work relied on it in a way that now needs reviewing.
Ask why it happened. Was it a one-off oversight or a wider gap in how superseded documents get withdrawn?
Add a bench check to the release process, or move to a system that automatically withdraws superseded copies.
At the next internal audit, confirm that the check has been happening and no further obsolete copies have turned up.
Revise the release procedure, or update the risks considered during planning if the review shows it's warranted.
Clause 8.7.2 also expects the response to be proportionate to the effect of the nonconformity. A single obsolete form found once warrants less than the same pattern turning up across several document types.
The controls that prevent repeat findings are worth treating as corrective action design, since each removes a specific cause.
These are the kind of controls a document management system (DMS) is built to apply automatically, rather than relying on people to remember them. Cognidox handles this centrally: a single controlled repository, locked templates, enforced approval before release, and change logs that build themselves. If you're weighing up whether a DMS is worth introducing at all, our guide to the key benefits of a DMS for regulated industries covers the wider case beyond just this one problem.
A nonconformity is the failure to meet a requirement, from the standard itself or from the lab's own system.
Document control findings can arise as nonconforming work (clause 7.10) or as a nonconformity handled through corrective action (clause 8.7), or both, depending on whether the affected document was actually used to carry out work.
Six patterns recur in document control findings: obsolete procedures, uncontrolled spreadsheets, missing evidence of approval, incomplete technical records, unmanaged external documents, and untraceable record corrections.
A correction fixes the instance found; a corrective action fixes the cause.
ISO/IEC 17025 doesn't define major and minor nonconformities. Any grading of findings comes from your accreditation body.
Closing a nonconformity under clause 8.7 means reacting, evaluating the cause, implementing action, reviewing it, and updating the system if needed.
Ready to reduce document control findings at your next assessment? Read our complete guide to ISO/IEC 17025 document control, or book a demo of the Cognidox DMS to see how centralised access, locked templates and automated change logs remove these causes before your next assessment.
A correction fixes the specific instance found, such as replacing an obsolete document at the bench. A corrective action addresses the underlying cause, so the same failure doesn't recur elsewhere. Clauses 7.10.3 and 8.7.1 require labs to evaluate whether a finding is isolated, in which case a correction may be enough, or whether it needs a full corrective action under clause 8.7.
It can be either. An obsolete document sitting unused at the bench is typically a management system nonconformity against clause 8.3, handled through corrective action under clause 8.7. If that document was actually used to carry out work, such as a calibration against outdated acceptance criteria, that activity also becomes nonconforming work under clause 7.10, because the validity of the output is in question.
No. ISO/IEC 17025:2017 does not define nonconformities as major or minor. Any grading of findings, along with the process and timescales for closing findings, is set by individual accreditation bodies such as UKAS, A2LA, ANAB or NVLAP, so check your specific body's documented approach rather than assuming a universal standard applies.