Technical newsheet
Metrology & CalibrationDevice profile
Auditors Trace Nonconformances to Outdated Drawings, Not Bad Gages
The measurement was fine; the document was not. Auditors trace nonconformances to outdated drawings — and SMEs face a weekly 'revision gap' risk heading into the ISO 9001:2026 transition.
By Olivia Hart4 min read736 words
Features
- The revision gap is the distance between the revision engineering approved and the revision inspection actually used.
- In a cited case, parts passed inspection to Rev B while engineering had approved Rev C eight days earlier after a bearing supplier change.
- ISO 9001:2026 retains the requirement to control documented information, including changes.
- Small and mid-sized manufacturers face the revision gap as a weekly risk; large OEMs typically have dedicated document control.
- Controlled releases should generate PDF, STEP, DXF and DWG files from the released version so inspection and CMM references match by construction.

The measurement was fine; the document was not. Ask a quality manager where nonconformances come from, and the answer usually points to the process, the operator or the gage. Ask an auditor, and you often hear something else: the part was inspected against a document that was no longer current.
That failure mode has a name in metrology practice — the revision gap, the distance between the revision engineering approved and the revision inspection actually used. It rarely surfaces until it appears as scrap, a customer complaint or an audit finding.
What the revision gap looks like on a bench
Consider a typical case. A batch of housings fails first article inspection on a bore diameter. The CMM (coordinate measuring machine) report checks out, and the program checks out. The parts conform — to Rev B. Engineering approved Rev C eight days earlier, after a bearing supplier change tightened the bore tolerance. The inspection bench never received it.
When the auditor asks who released Rev C, when, and how inspection was told, the answers come from an email thread, a folder name and someone's memory. None of that constitutes evidence. All of it becomes a finding.
Where does document control break?
Three points of failure recur across shops, according to the analysis.
- Release. In many small and mid-sized manufacturers, "released" means a file moved into a folder, a PDF saved with "Rev C" in the name, or an email sent. Those are habits, not controlled states. They hold until the week everyone is busy.
- Export. Inspection works from a PDF drawing; the CMM programmer works from a STEP file. Both are usually exported by hand, often at different times, sometimes from different versions of the model. Each file looks official. They do not always describe the same part.
- Feedback. When inspection finds a design problem — a datum that cannot be fixtured, a tolerance the process cannot hold — the finding travels back by email, a marked-up printout or a conversation. It rarely stays attached to the revision it concerns, so the next revision can repeat it.
Can faster inspection fix a document problem?
No. Inline sensors, automated CMM programming and AI-assisted inspection shorten the time between making a part and knowing whether it conforms. All of them assume the reference is correct. If the nominal geometry or the drawing behind a program sits one revision behind, faster inspection produces confident results against the wrong target.
The remedy does not require a large PLM (product lifecycle management) program. It requires controls that can be checked rather than remembered:
- An explicit state on every drawing and model — In Progress, Under Review, Released — that quality can see without asking engineering
- Named sign-off on each release, recording who approved it and when, so the audit answer sits on the release itself
- Quality on the approval, as approver or observer, so inspectability issues surface before the revision is final
- Production files generated from the release, with PDF, STEP, DXF and DWG produced from the released version and stored against it, so the inspector's drawing and the programmer's model match by construction
- Feedback attached to the model, so inspection findings reach the design engineer in the next revision
Why the ISO 9001:2026 timing matters
The ISO 9001:2026 transition keeps the requirement to control documented information, including changes. As manufacturers review their quality systems for the revision, many will check procedures on paper. Fewer will check how a revision actually travels from design to the inspection bench.
Small and mid-sized manufacturers carry the most exposure. Large OEMs usually maintain dedicated document control. Contract shops, SME manufacturers and engineering consultancies often hold designs on network or cloud drives, employ engineers across sites, and run a quality team of one or two people who also handle incoming inspection and supplier issues. For them, the revision gap is a weekly risk, not an edge case.
A test before your next audit
Take one recent nonconformance and trace it backward. Which revision was the inspector using? Where did that file come from? Who approved the revision that should have been used, and how did inspection find out? If any answer depends on a folder name, an inbox or a person's memory, document control has a gap the auditor will find too.
The question every shop should now ask: does your revision trail survive an audit without anyone's memory?
via bnpmedia.com (Original)
Filed under
- document-control
- revision-control
- cmm-inspection
- iso-9001
- quality-auditing
More from Olivia Hart
Show full bio
Market editor covering technology and product news in Instruments, test and measurement at Testbench Report.
99 articles
Application notes
- ISO 9001:2026 Published as Evolution, Not Overhaul
- Metrology bulletin: 12 µm scanning, traceability and inline QA
- Cavity 3 at 10.045 mm: Why Ticks Fail First Article Reports
- When a Perfect NDT Record Is a Lie: Verifying Inspection Documentation
- Smart metrology moves factory inspection into real-time control