Our Blog
Practical guidance on gauging, calibration, standards, and shop-floor quality, from the DSN engineering team.
Practical guidance on gauging, calibration, standards, and shop-floor quality, from the DSN engineering team.
Almost every shop we visit has a gauge register. Almost none of them are current. The typical register starts as a well-intentioned spreadsheet — every gauge listed, calibration dates entered, due dates calculated — and within a few months it drifts. New gauges arrive and are not added. Calibrated gauges come back and the dates are not updated. Gauges are moved between stations and the locations go stale. By the time an auditor asks to see it, the register is a document of what the shop wished it had been doing, not what it actually did.
The problem is not the spreadsheet. The problem is that a gauge register is treated as a record instead of a system. This guide explains how to build one that stays current — because the habits around it work, not because someone remembers to update it.
A register has three jobs. It tells you which gauges you have and where they are. It tells you when each gauge is due for calibration. And it tells you who is responsible when something goes wrong. Everything else — criticality ratings, usage logs, drift history — is valuable but secondary. If the register does those three things reliably, it is working. If it does not, no amount of extra columns will fix it.
The reason most registers fail is that the first job — knowing what you have and where it is — is treated as a one-time data entry instead of an ongoing discipline. A register that is not updated when gauges arrive, move, or leave is a register that is wrong, and a wrong register is worse than no register because it creates false confidence.
A working register does not need dozens of columns. It needs: gauge ID (engraved or labelled on the gauge itself), description (size, type, standard), storage location, assigned owner, last calibration date, next due date, and criticality (high, medium, low). That is enough to manage recall, locate gauges, and prioritise calibration spend. Usage logs and drift history can be added later for gauges where the data justifies it — see our calibration frequency guide for how criticality drives intervals.
The one field that most registers miss is the owner. A gauge with no named owner is a gauge that nobody updates in the register, nobody calibrates on time, and nobody notices when it goes missing. Ownership is the single habit that keeps a register alive. See our gauge usage guide for why ownership matters across gauge management.
A register stays current through a few specific moments, not through weekly maintenance sprints. When a new gauge arrives, it is added to the register the same day — see our incoming gauge approval checklist for the receipt process that feeds this. When a gauge returns from calibration, the dates are updated before the gauge goes back to its location. When a gauge moves between stations or plants, the location field is updated. When a gauge is retired or replaced, it is marked as such, not deleted — the history matters for audit.
Each of these updates takes seconds if the register is accessible to the people who need it. A register that lives on one person's laptop, updated when that person has time, will always drift. A register that the gauge owners can update themselves — even if it is a shared spreadsheet — stays closer to current.
A spreadsheet works for a small gauge inventory — up to perhaps 50 or 100 gauges, depending on discipline. Beyond that, the manual update burden and the lack of automated due-date alerts make a dedicated system worthwhile. The features that matter most are: automated due-date flagging, the ability to link certificates to gauge IDs, and access for multiple users across shifts or sites. Features that look impressive in a demo — AI predictions, dashboards nobody looks at — matter less than the basics done reliably.
The transition from spreadsheet to system should not happen until the spreadsheet habits are solid. Buying a system to fix a discipline problem just moves the same problem to a more expensive platform. Get the habits right first; the system then amplifies them instead of inheriting their failures.
A register is not standalone — it connects to every other gauge practice. Calibration intervals come from the criticality and usage data in the register. Storage locations come from the register and feed back into it. Wear decisions — when to replace rather than recalibrate — use the drift history that the register accumulates. See our wear limits guide for that decision. And the certificate data that supports audits is only useful if it is linked to the right gauge in the register — read our certification guide and calibration report guide.
When an auditor looks at your gauge register, they are checking whether your inspection is under control. A current register with named owners, accurate locations, and no overdue calibrations is evidence of a managed system. A stale register with missing owners and overdue dates is evidence of a system that exists on paper only. The difference is not the format — it is whether the habits behind it are real. For the audit-friendly documentation that surrounds the register, see our incoming approval checklist.
We help customers build gauge management practices that stay current — through calibration support that connects to the register, gauge supply that arrives with proper documentation, and guidance on structuring recall and criticality. If your register is a document of good intentions rather than a working system, talk to our team. The fix is usually habits and ownership, not software — and once those are in place, the software actually pays off.