Gauge Calibration Scheduler & Certificate Tracker: Never Measure With an Uncontrolled Gauge

The problem this kills

Every calipers, micrometer, pin gauge, torque wrench, and CMM in your shop is supposed to be on a calibration schedule. Each one has an interval, a last-cal date, and a certificate sitting in a folder somewhere. The whole point is simple: nobody should ever inspect a part with an instrument that's overdue or out of cal — because if they do, every measurement that gauge took since its last good cal is now suspect, and that's a recall conversation, not a paperwork problem.

But the schedule lives in a spreadsheet that nobody opens until the auditor asks for it. Due dates get computed by hand. The "due this month" tab is stale. A gauge goes overdue on the floor and keeps getting used because no alert ever fired. The certificate for the gauge the auditor just pointed at is missing, or it's the old one. And when a gauge finally comes back from cal failing, nobody traces back what it last inspected. Each gap is small. Together they're the exact finding that turns a smooth ISO 9001 / IATF 16949 / AS9100 audit into a corrective-action marathon.

You don't need a five-figure CMMS module to fix this. You can build the tracker yourself, this weekend.

What you'll build

An internal web tool your quality team logs into. You import your gauge list — the CSV or Google Sheet you already keep — and the tool does the date math for every instrument: from the last-cal date and the interval it computes the next-due date and stamps a live status (in service, due soon, overdue, out of cal). It emails the owner before each gauge comes due, and again the moment one tips overdue, so an uncontrolled gauge can't quietly stay on the floor.

When a gauge gets calibrated, a tech records the result and uploads the certificate PDF straight to the gauge's record. Here's the controlled part: that gauge does not go back to "in service" on its own. The calibration coordinator reviews the result and the cert and approves it — only then does the status flip and the next-due date reset. If a gauge comes back out of cal / failed, the tool opens an impact review so you capture what that gauge last inspected before it gets reset. At any time you click once to export a clean calibration register in the columns your QMS or auditor expects.

What's inside the Implementation Plan

The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own metrology program — how you ID your gauges, your gauge types and intervals, where they live, who owns them, your "due soon" lead time, your approval rules, and your messiest edge cases (gauges out for repair, loaners, calibrate-before-use, reference standards) — and then it reads a short spec back for your thumbs-up before it builds anything. That's the difference between a tool shaped to your gauge register and a generic template you have to wrestle into shape.

From there it walks the agent through the data model (gauges, calibration events, certificates, alerts, audit), the importer, the due-date and status engine, the due/overdue email alerts, the record-cal-result + cert-upload flow, the out-of-cal impact review, the coordinator approval gate that blocks "in service," and the register export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: import your gauge CSV, export a clean register CSV, and you never have to touch any existing system's API to ship.

The governance it includes (this is the point)

This is quality — the controls are the product. The plan builds them in: a login so only your team can use it; row-level security so each plant or organization only ever sees its own gauges; a complete audit trail of who imported, calibrated, approved, and exported, and when; a hard human-approval gate so a gauge cannot return to "in service" until the calibration coordinator signs off on the result and cert; and a duplicate guard (gauge ID + cal date) so the same calibration can't be recorded twice. An out-of-cal gauge forces an impact review before reset. That's the controlled-instrument story your auditor wants to see — on a screen, not in a binder.

Who it's for

Quality engineers, calibration coordinators, and metrology technicians who own the gauge program and are tired of finding out a gauge was overdue only when the auditor circles it. If you can explain to a new hire how a gauge gets its due date and what makes it safe to use again, you can build this — no developer required.

You've got this — open the plan, paste the first prompt, answer a few questions about how your calibration program actually runs, and you'll watch your first gauge list turn into a live, alerting register.