ISO 13485 inspection documentation: what an auditor actually wants to see
The first ISO 13485 audit I sat through as a plant head went sideways over a single missing signature. The part was good, the CMM data was clean — but the inspection record had no operator initial and no link back to the drawing revision. The auditor wrote it up as a nonconformity. The lesson stuck: under ISO 13485, the part being right is not enough. You have to prove it was checked, by whom, against which drawing, with what result.
ISO 13485 inspection documentation is the chain of records that turns a measured dimension into traceable, audit-ready evidence. This guide walks through what the standard requires, what the records must contain, and how to stop the paperwork from eating your inspection team alive.
What ISO 13485 actually requires for inspection records
ISO 13485:2016 is the quality management system standard for medical devices. It does not give you a fill-in form. Instead, clause 7.5.1 (production and service controls), clause 8.2.6 (monitoring and measurement of product), and clause 4.2.5 (control of records) together demand that you define how product is inspected, record the results, and keep those records controlled and retrievable.
In plain terms, three things must always be provable from your documentation: that the correct acceptance criteria were applied, that the person releasing the product is identified, and that every record can be traced back to the specific device, batch, and drawing revision. Clause 7.5.9 on traceability tightens this further for implantable devices, where you must record components, materials, and work environment conditions.
The core records you must maintain
Most ISO 13485 inspection systems revolve around a handful of record types. Here is what each one carries and where engineers most often lose marks.
| Record | What it proves | Common gap |
|---|---|---|
| Incoming inspection record | Purchased material met spec before use | No link to supplier CoC or lot number |
| In-process inspection | Conformance during manufacture | Missing operator ID or time stamp |
| Final inspection / release | Product met all acceptance criteria | No authorised release signature |
| Device History Record (DHR) | The batch was made per the DMR | Records not collated per batch |
| Nonconformance / CAPA | Out-of-spec product was controlled | Disposition without justification |
The Device History Record (DHR) is the one that trips people up. It is not a single document — it is the compiled evidence that a particular batch was built and inspected according to the Device Master Record (DMR). Your inspection sheets are a major input to the DHR, so if the inspection sheet is incomplete, the DHR is incomplete by definition.
What every inspection record must contain
Regardless of format, a compliant inspection record needs these fields. Build them into your template once and you stop arguing about them at audit time.
- Part number and drawing revision. The exact revision inspected, not just "latest". This is the single most common traceability gap.
- Characteristic identifier. A balloon number tying each result to a specific dimension or GD&T callout on the drawing.
- Nominal, tolerance, and acceptance criteria. Stated, not implied — so the record stands alone.
- Measured result and the instrument used. Including the gauge ID for calibration traceability.
- Operator identity and date. Who measured, when. Electronic records need clause 4.1.6 software validation behind the signature.
- Disposition. Accept, reject, or use-as-is with reference to the nonconformance record.
If you run electronic records, ISO 13485 clause 4.1.6 expects the software used for the QMS to be validated for its intended use, and for jurisdictions under US FDA 21 CFR Part 11 you also need controlled electronic signatures. Keep that in mind before moving inspection sheets into a spreadsheet nobody has validated.
From drawing to controlled inspection sheet
The documentation chain starts at the drawing. Before anyone measures anything, every dimension, tolerance, surface finish, and feature control frame on the print needs a unique balloon number — because that number is the row in your inspection sheet, your DHR input, and your traceability matrix.
Manual ballooning of a dense medical-component drawing — say an orthopaedic implant housing with 90+ characteristics — takes hours and routinely drops callouts. A missed general-tolerance note becomes an uninspected characteristic, which becomes an audit finding. CadNexa's auto-ballooning reads the PDF with Smart Detect plus Box+Balloon OCR, finds the dimensions and GD&T, and numbers them sequentially, so nothing slips through. You verify rather than transcribe.
Add image here
From the ballooned drawing you export a structured characteristic list — number, nominal, tolerance, type — which becomes the skeleton of the inspection sheet. This is the same workflow covered in the guide on how to convert a drawing to an inspection sheet, and it feeds directly into FAI and PPAP packs. For medical work, the discipline that matters is locking the drawing revision into that export so the record is unambiguous.
Common ISO 13485 documentation mistakes
- Citing "latest revision" instead of the actual revision. Records must name the exact rev the part was made and inspected against.
- Inspection sheets that don't reconcile to the DHR. If the batch quantity inspected doesn't match the batch built, the DHR fails.
- Unvalidated spreadsheets holding records. Clause 4.1.6 expects QMS software to be validated; an ad-hoc Excel sheet rarely is.
- No calibration link. A measured result with no gauge ID can't be traced to a calibration certificate.
- Re-numbering balloons every revision. When characteristic numbers shift between revs, historical records stop lining up — compare revisions instead.
How CadNexa fits into ISO 13485 documentation
CadNexa is not a full QMS — it does not replace your document control or CAPA system. What it does is fix the weakest link: turning the drawing into a complete, controlled set of inspection characteristics with nothing missed. You open the PDF, auto-balloon it, capture tolerances and methods, and export the characteristic list as balloon data to CSV — the exact columns a final inspection record and a DHR input need. Pair it with disciplined revision control and your inspection sheets stop being the thing auditors write up.
Turn any drawing into an audit-ready inspection sheet
Auto-balloon the PDF, capture every characteristic, and export a clean, traceable list — free to try.
Build Your Inspection Sheet — Free →Frequently asked questions about ISO 13485 inspection documentation
What inspection records does ISO 13485 require?
ISO 13485:2016 requires records showing that defined acceptance criteria were applied, that the person releasing product is identified, and that results are traceable to the device, batch, and drawing revision. In practice this means incoming, in-process, and final inspection records, compiled into the Device History Record per batch.
What is a Device History Record (DHR)?
A DHR is the compiled evidence that a specific batch was manufactured and inspected according to the Device Master Record. It is not one document but a collation of records — including inspection sheets, so an incomplete inspection sheet makes the DHR incomplete.
Does ISO 13485 allow electronic inspection records?
Yes, but clause 4.1.6 expects software used in the QMS to be validated for its intended use, and jurisdictions under FDA 21 CFR Part 11 require controlled electronic signatures. An unvalidated spreadsheet holding release records is a common finding.
How do I make inspection records traceable to the drawing?
Balloon every characteristic on the drawing with a unique number and record the exact drawing revision on the inspection sheet. Each measured result then references its balloon number, so any reading can be traced back to a specific dimension on a specific revision.
What is the difference between FAI and ongoing ISO 13485 inspection?
First Article Inspection verifies 100% of characteristics on an initial part to prove the process can make the design. Ongoing ISO 13485 inspection records conformance during routine production — usually sampled — and feeds the Device History Record for each batch.