We Almost Lost Our ISO Audit Because We Couldn't Prove the Maintenance Was Done

The surveillance audit was going well. The auditor had spent the morning walking the production floor, reviewing quality control procedures, and interviewing two operators. By early afternoon, she was at the measuring room. She stopped in front of the coordinate measuring machine — the CMM that the company uses to verify every critical dimension on its automotive housings — and asked a routine question: 'Can you show me the maintenance records for this equipment for the past twelve months?'

The production manager went to the maintenance room and came back with a spiral-bound notebook. The auditor turned to the relevant pages. There were four entries for the CMM across the year — each one a few handwritten lines, no timestamps beyond the month, no checklist of what was inspected, and one signed by a technician who, she was told, had left the company in the spring.

She wrote a Major Non-Conformity.

What a Major Non-Conformity Actually Means

In the ISO 9001 world, a Major Non-Conformity is not a warning. It is a formal finding that a significant element of the quality management system has failed. The consequences in this case were immediate and concrete:

• A corrective action plan had to be submitted to the certification body within 30 days, with objective evidence of root cause analysis and corrective measures.
• The company's Tier 1 automotive customer — who required ISO 9001 as a condition of the supplier agreement — was notified of the finding as a matter of procedure.
• An extraordinary follow-up audit was scheduled for 90 days later to verify that corrective actions had been implemented.
• Until the follow-up audit was passed, the customer placed new purchase orders on hold pending review.

The maintenance had been done. The production manager knew it, the technicians knew it, and a closer look at the notebook confirmed that something had been recorded. But 'we know it was done' is not evidence. In an ISO audit, if it is not documented in a way that can be independently verified, it did not happen.

Why the Notebook Failed the Audit

The notebook entries failed on four specific grounds — the same four grounds that paper maintenance records almost always fail when subjected to formal scrutiny:

1. No verifiable timestamp. 'March' is not a date. The auditor cannot determine whether the maintenance interval required by the quality plan was actually met.
2. No checklist of work performed. The entry said 'CMM annual maintenance done.' It did not say what was checked, what was measured, what was cleaned, what was replaced, or what the results were. There is no way to confirm that the maintenance was complete rather than partial.
3. No traceable technician. One entry was signed by a person no longer employed by the company. There is no way to verify their competency record or follow up on what they did.
4. No linkage to the maintenance plan. The quality management system defined a required maintenance interval for the CMM. The notebook entries were not demonstrably linked to that requirement — they were informal records, not evidence of a managed process.

None of these are obscure requirements. They are standard expectations in any ISO 9001 audit. The problem was not that the company did not maintain its equipment — it was that the recording system was not capable of producing credible evidence of that maintenance.

The Hidden Risk in Every Small Manufacturing Business

This company was not unusual. The vast majority of small manufacturers with ISO 9001, IATF 16949, BRC, or IFS certification maintain their equipment in practice — but record that maintenance in systems that would not survive a determined audit: notebooks, spreadsheets, email trails, or nothing at all.

The risk goes unnoticed for years because most surveillance audits do not dig deeply into maintenance records. When an auditor does look — as part of a focused audit, a customer-driven second-party audit, or simply because something on the production floor prompted the question — the gap becomes immediately visible.

The companies that fail on this are not the ones that neglect maintenance. They are the ones that do the work and fail to capture it in a way that proves it.

What an Audit-Ready Maintenance Record Looks Like

When an auditor asks for proof that a piece of equipment was maintained within a required interval, the evidence needs to answer five questions without ambiguity:

• When was the maintenance performed — exact date and time?
• Who performed it — named, traceable individual?
• What was done — a specific list of tasks completed?
• What were the findings — were any issues noted, and if so, what was done about them?
• Was it on schedule — does this record demonstrate that the required interval was met?

A notebook entry answers none of these reliably. A completed work order in iTenance answers all of them.

How iTenance Creates the Audit Trail Automatically

When the company implemented iTenance after the audit finding, the goal was not to create a documentation system on top of their maintenance work — it was to make the documentation an automatic output of the work itself.

1. Every Work Order Is Timestamped at Creation and Completion

The moment a technician opens a work order in iTenance, the system records the date and time. The moment they mark it complete, that timestamp is recorded too. There is no entry of 'March' — there is a precise record of when the work started and when it was completed, captured by the system automatically, not by the technician's memory.

For the CMM, the annual maintenance work order now shows: opened 14 March at 08:42, completed 14 March at 11:17. That is audit-ready evidence of timing.

2. Named Technician on Every Work Order — Permanently

Every work order in iTenance is assigned to a named user account. When a technician completes and signs off a work order, their name and user record are attached to it permanently. If that technician later leaves the company, their completed work orders remain in the system with their name and, if maintained, their competency record linked to their profile.

The auditor's question — 'who did this, and can you verify their competency?' — is answerable in two clicks.

3. Maintenance Checklists Define What Was Done

For every piece of equipment subject to a quality plan maintenance requirement, the company built a checklist in iTenance: the specific tasks required by the manufacturer's service schedule and the quality system. The checklist is attached to the recurring work order. The technician cannot mark the work order complete without working through each item.

The CMM annual maintenance checklist includes: probe qualification, axis calibration verification, temperature compensation check, linear scale inspection, software version confirmation, and cleaning of the granite table and stylus rack. Each item is ticked with a timestamp. The completed checklist is the proof of what was done.

4. Recurring Work Orders Enforce the Required Interval

The quality plan required annual maintenance for the CMM and quarterly lubrication checks. Both are now set as recurring work orders in iTenance with the exact intervals. The system creates the next work order automatically when the previous one is completed. If a work order becomes overdue, it escalates — the responsible supervisor receives a notification.

This means the maintenance interval is not dependent on someone remembering. The system manages the schedule and flags any departure from it. An auditor can see that no interval was missed, because the system would not have allowed it to pass unnoticed.

5. One-Click Audit Report for Any Machine

When the follow-up auditor arrived 90 days after the original finding, the production manager opened iTenance, filtered the CMM's maintenance history by date range, and exported a structured report: every work order, every checklist, every technician, every timestamp, in chronological order.

The auditor reviewed it in ten minutes. The Non-Conformity was closed.

Beyond ISO: The Day-to-Day Value of the Audit Trail

The audit trail in iTenance turned out to be useful well beyond formal external audits. Within the first six months, the maintenance history for the CMM helped in three practical situations:

• A customer query about measurement uncertainty on a batch of parts was answered by cross-referencing the measurement date against the most recent calibration record — a five-minute investigation rather than a two-hour search through paper files.
• When the CMM began drifting slightly on one axis, the history of probe qualification results over twelve months revealed that the issue had been developing gradually — enabling a targeted repair rather than a full recalibration at the manufacturer's facility.
• When a second technician was trained on CMM maintenance, the completed checklists from the previous year served as a concrete training reference — what was done, how it was done, what findings were normal.

The documentation that was built for the auditor turned out to be useful for the engineers, the trainers, and the troubleshooters too.

Getting Compliance-Ready: What to Set Up First

If you have ISO 9001, IATF 16949, BRC, IFS, or any customer-mandated quality certification that references equipment maintenance, start with this:

1. List every piece of equipment that your quality plan requires to be maintained on a defined schedule. This is usually five to fifteen machines in a small manufacturing operation — the critical measurement equipment, key production machines, and any equipment referenced in your control plan.
2. For each machine, create a recurring work order in iTenance at the required interval — annual, semi-annual, quarterly. Attach the manufacturer's maintenance checklist or your internal procedure as the task list.
3. Ensure every technician has a named user account in iTenance. Work orders completed under a shared login or a generic account will not satisfy an auditor looking for individual traceability.
4. Run one full cycle before your next audit. By the time the auditor asks the question, you will have a complete, exportable maintenance history for every critical asset — built automatically, without any additional documentation effort beyond the work itself.

'The audit finding was the best thing that happened to our maintenance system. We were doing the work — we just were not capturing it properly. Now the record builds itself every time a technician completes a job.'

— Production Manager, Automotive Parts Manufacturer

The auditor is not trying to catch you out. She is trying to verify that your quality system is real — that the maintenance your procedures describe is the maintenance you actually perform. The only way to satisfy that question is to have a record that is as reliable as the work itself.

A notebook is not that record. A timestamped, named, checklist-backed work order in iTenance is.