Why the transition is the moment

The short answer. ISO 9001:2026 was published on September 16, 2026, and organizations certified to ISO 9001:2015 have until September 30, 2029 to move to it, according to LRQA. Because the transition means reopening procedures and walking a registrar through each record anyway, it is a low-cost time to move inspections, nonconformance reports, corrective actions and calibration out of spreadsheets. The records that matter most at an audit are the ones that connect: which gauge measured a part, whether that gauge was in calibration that day, and what happened after a failed inspection. Whether a set of records satisfies the standard remains the registrar's call.

ISO 9001:2026 was published on September 16, 2026, and shops certified to the 2015 edition have until September 30, 2029 to move to it, according to LRQA. Three years sounds like plenty. In a contract machine shop it goes quickly, because the transition lands on top of real work: jobs, customers and the audits you already have.

Whatever the new edition asks of your quality system, you will open your procedures, look at how each record is kept, and walk your registrar through it. That is the one time in years when changing where the records live costs little extra. You are already rewriting the procedure; you might as well rewrite it around a better record.

This article is about four records that cause the most trouble at audits when they live in spreadsheets and Word files: inspections, nonconformance reports (NCRs), corrective actions and calibration. The system keeps records; whether they satisfy the standard is still your registrar's call.

Last reviewed: November 11, 2026

What goes wrong with spreadsheet quality records

Most shops don't lack records. They have too many copies of them, kept by different people, and not connected to each other.

  • Inspections are written on the traveler, then typed into a workbook later, if at all. The verdict, pass or fail, is typed as a word rather than worked out from the reading and the drawing's tolerance.
  • NCRs are Word files in a shared folder, numbered by whoever remembers the last number.
  • Corrective actions are opened from an NCR, but nothing links them back, and many are closed without anyone checking that the fix worked.
  • Calibration lives on a gauge list that is kept up when someone remembers, and nothing stops a gauge past its due date from being picked up and used.

Each record may be fine on its own. The trouble is the questions that cross them. An auditor or a customer picks a part and asks: which gauge measured it, was that gauge in calibration that day, and if the part failed, what happened next?

A worked example: one overdue gauge

Here is an illustrative case, with dates and figures made up.

A bore gauge was last calibrated on March 4 with a 12-month interval, so it was due on March 4 of the next year. Nobody noticed the due date pass. On April 15 it went out for its calibration and came back out of tolerance.

Now the arithmetic starts. Every inspection made with that gauge since March 4 is in question, and arguably since its last good calibration. If the shop ran, say, 40 jobs through that bore check in those six weeks, someone has to find all 40, work out which parts are still on the floor and which have shipped, and decide for each whether the reading could have been wrong enough to matter. A bore read at 0.0003 inch inside a 0.0005 inch tolerance is a very different question from one read 0.0001 inch inside it.

In a spreadsheet shop, the first step alone is the hard part, because the inspection records often don't say which gauge was used, only that the dimension was checked.

How to do it better, even in a spreadsheet

You can tighten these records a great deal before you change any software.

  1. One calibration register. One row per gauge, with an ID marked on the gauge itself, the last calibration date, the interval, and a due date worked out by formula, not typed. Conditional formatting turns rows red once the due date passes.
  2. The gauge ID on every inspection. Add a gauge column to the inspection log and make it required. This single column is what makes the overdue gauge example answerable.
  3. Readings, not verdicts. Record the measured value, the nominal and the tolerance, and let a formula decide pass or fail.
  4. One NCR log with real numbers. A sheet, not a folder: NCR number, part, job, quantity, disposition, and the corrective action number if one was opened.
  5. No closing without an effectiveness check. Give the corrective action log a column for the check, the date it was done and what it found, and treat an empty cell as still open.

This is better, and it is honest work. Its limit is that nothing enforces it. The workbook can't stop a machinist from picking up the overdue gauge, can't stop someone from typing "pass", and can't keep last month's record from being edited after the fact.

How a system does it

The demo for Penwick Machine Works, a fictional machine shop, shows the same four records kept as the work happens, rather than written up afterwards.

  • Inspections on the machine's tablet page. The machinist runs the operation's in-process checks on the tablet beside the machine, and only gauges in calibration are offered. Inspections and first articles are passed or failed against the drawing's tolerances, never typed as a verdict. A reading out of tolerance offers "Hold and report".
  • The NCR log, kept in the system rather than as Word files in a shared folder.
  • Corrective actions that close only with their effectiveness check. The AI helper drafts the first version from the NCR, the notes from the floor and earlier corrective actions on the same part family: the problem statement, containment, likely causes, a proposed action and the effectiveness check, noting when it looks like a recurrence. The quality manager edits it before anything is saved. The AI drafts; the quality manager decides.
  • The calibration register, which the demo built from the old gauge list with the due dates worked out again. A gauge past due drops off every gauge list on the floor until it is calibrated.
  • An audit page with each record exported to Excel, and records that can't be changed once saved.

In the demo you can follow a failed inspection all the way to a closed corrective action, the same question an auditor asks, answered by clicking rather than searching.

Try it, and what it costs

The job shop page covers the rest of the system: the work orders board, the shop board, customer POs read by AI and the owner's dashboard. The live demo lets you sign in with one click as the production manager, a machinist, the quality manager or the owner, with no account to create. The data resets every night, so you can't break anything.

A typical build costs $8,000 to $25,000 at a fixed price, and hosting and support start at $350 a month.

Questions

When does the ISO 9001:2026 transition end?

According to LRQA, ISO 9001:2026 was published on September 16, 2026, and organizations certified to the 2015 edition have until September 30, 2029 to transition. Three years passes quickly when the transition lands on top of normal work and existing audits.

What happens to past inspections when a gauge is found out of tolerance?

Every inspection made with that gauge since its calibration due date, and arguably since its last good calibration, is in question. Each affected part has to be found, sorted into still on the floor or already shipped, and judged on whether the reading could have been wrong enough to matter. That first step is hard unless each inspection record names the gauge used.

What should a spreadsheet quality system record to stand up at an audit?

Keep one calibration register with the due date worked out by formula, a required gauge ID on every inspection, measured readings with nominal and tolerance so a formula decides pass or fail, one numbered NCR log, and a corrective action log that stays open until its effectiveness check is recorded. A spreadsheet cannot enforce any of this, so it depends on people filling it in.