Quality · 12 Jul 2026 · 6 min read

First Article Inspection without the spreadsheet

Of all the quality paperwork in a precision shop, the First Article is the one that actually stops a job dead. New part, new revision — you can't run the batch of fifty until the first one's been proven, dimension by dimension, against the drawing. Fair enough. It's the doing of it that hurts.

If you machine to AS9100, or you supply anyone who does, you know the drill. Fresh revision lands, and before the run can go ahead someone has to sit down with the drawing and build a FAIR — every dimension, every tolerance, every GD&T callout, transcribed into a form, then measured off the first part and typed back in. Balloon the drawing. Number the characteristics. Fill the columns. Attach the evidence.

In most shops that's a Word template, or an Excel one if you're lucky, plus a folder somewhere, plus the hope that when the customer or the auditor asks for it in eight months' time, you can find it.

Why the First Article eats hours

The honest root cause is the same one behind most quality-admin pain: the FAIR is built as a separate document, disconnected from the job it belongs to. So the dimensions get re-typed off the drawing by hand — which is both slow and exactly where transcription errors creep in. The measured values get keyed into a form that has no idea which job, which revision, or which machine it relates to. The evidence — the CMM printout, the photos, the gauge used — lives in a different place again. Nothing links to anything. You're assembling a story by hand that the system could have stored as a story in the first place.

And because it blocks the run, that hour or two of form-filling isn't just admin — it's the machine standing idle while someone does it. Fix the disconnection and the whole thing collapses into the flow of the work.

What makes it painless instead

This is one of the parts we built DMOS around, because we hated it as much as anyone. Four things do the work.

1. It creates itself, and it stops the run

When a job hits the floor on a fresh part-revision, the system raises the First Article Inspection automatically and blocks the bulk run until it's signed off. You don't have to remember to do a FAIR — the job won't let you ship fifty until the first one's proven. The gate is the system's, not a person's memory. (If it's not a fresh revision, no gate — it only fires when a First Article is genuinely required.)

2. The characteristics come from the part, not your typing

The inspection is built against the part revision and its drawing that already live in the system — so the characteristics aren't re-keyed off the page by hand for the hundredth time. You record the measured value against each one and mark it pass or fail. The overall result derives itself. No separate form, no transcription round-trip.

3. The gauge is part of the record — and it's checked

When you record a measurement you pick the gauge you used, from your calibration register. If that gauge is out of calibration, the system flags it right there — because a First Article signed off on an out-of-cal gauge is exactly the kind of thing that unravels on audit day. Calibration and inspection aren't two disconnected spreadsheets; they're the same system, so the check is automatic.

4. Fail, and the loop starts on its own

If a characteristic fails, you raise a non-conformance straight off the inspection in a click — and it inherits the job, the part-revision and the machine automatically. That NCR drives a corrective action, and the run stays halted until it's resolved. The failure and its fix are captured as a linked chain, not reconstructed later from memory. And when the audit comes round, all of it — the FAIR, the characteristic-level evidence, the NCR, the CAPA — is already in the audit pack, because it was stored against the job the moment it happened.

Why I built this

I'm not writing this as a software company that read the AS9100 standard once. I ran a UK precision-machining shop, and I built FAIRs the old way — the Word template, the ballooned PDF, the folder, the machine sat waiting while I filled columns. DMOS is the operating system that ran that shop, turned into a product. The First Article gate exists because a customer job on a fresh revision needed it and I was tired of it being a manual ritual that held up the spindle.

I won't pretend a fictional number at you. If First Articles hold your machines up and your quality evidence lives in folders you dread searching, taking the friction out of it gives you back spindle time and a calmer audit. Run your own numbers against the Everything plan (£149/month) and decide whether that trade is worth it for your shop.

The honest objections

• "We don't do formal FAIRs — our customers don't ask." Then this matters less to you today. But the moment you win aerospace, defence or medical work, you will, and having the mechanism already running beats scrambling to bolt it on mid-contract.
• "Our inspector likes his spreadsheet." Fair — most do, because it's what they've got. The test is whether recording a value against a characteristic that's already linked to the job is less work than re-typing the whole drawing into a fresh sheet each time. For a fresh revision, it is.
• "We've a stack of old FAIRs on paper." Leave them. DMOS records First Articles from go-live; your historical paper stays as reference. You're not digitising the past to run clean going forward.

If the First Article is the thing that quietly holds your shop up — the machine waiting while a form gets filled — it's worth twenty minutes to see it done differently.