Choosing calibration software
How to Track Calibration Due Dates in Software (and Stop Recalls Slipping)
Full disclosure: Axiospec is one of the tools in this guide, so weigh our take accordingly. The recurring problem is simple. An instrument goes past its due date, nobody notices, and it turns up overdue during an audit. This is how software computes next-due dates, surfaces due-soon and overdue instruments, and reminds you before a recall slips.
The problem: overdue instruments found during an audit
Almost every calibration program starts on a spreadsheet. It works until it does not. One person owns the file, they update it when they remember, and the due dates drift out of date. Then an auditor pulls a caliper, checks the sticker, and it expired four months ago. Now you are writing a nonconformance and reviewing every measurement that instrument touched since it went overdue.
The spreadsheet is not really the villain. The problem is that a static file cannot tell you what changed today. It does not know that a gage was calibrated last week, or that three more come due on Friday. Someone has to look, and people are busy. Tracking due dates in software handles the part humans are bad at: watching a moving list every single day.
How software computes the next-due date
The core calculation is small. Take the last calibration date, add the calibration interval, and you get the next-due date. If a micrometer was calibrated on January 10 with a 12-month interval, it is due on January 10 the following year. Software does this for every instrument at once and keeps the date current as new calibrations are logged.
The interval is the judgment call, not the math. Set it too long and you risk using an instrument that has drifted. Set it too short and you pay for calibrations you did not need. Interval is driven by how the instrument is used, its history, and the standard you work to. If you are still deciding, the interval guide and calculator below walk through it.
Due-soon, overdue, and reminders
A due date on its own is just a number in a cell. What keeps recalls from slipping is turning that date into a status you can act on, plus a reminder that reaches a person before the date passes.
- Due soon: instruments coming due inside a window you choose, so there is time to schedule the work or send the item out.
- Overdue: instruments past their due date, counted and separated so they are impossible to miss.
- Reminders: notifications ahead of a due date, so the right person acts while there is still runway.
- Status counts: a running tally of how many instruments are current, due soon, and overdue across the whole shop.
An at-a-glance readiness view
Counts are useful, but people also think in calendars and in one honest summary. Two views cover most of what a quality lead needs on a Monday morning.
A Calibration Due Calendar lays out what comes due by date, so you can see a heavy week before it arrives and plan around it. An Audit-Readiness Scorecard rolls the whole picture into one place: how many instruments are current, what is due soon, what is overdue, and where the gaps are. It is the view you want open when someone asks whether you are ready for an audit, instead of digging through a spreadsheet to answer.
Software supports that readiness. It does not certify it. Whether you pass still depends on your own processes, your scope, and your assessor. The value is that the record is kept audit-ready as you work, not rebuilt the night before.
Keeping the dates honest at the bench
Due-date tracking only works if the last-calibration date is accurate. That breaks down when logging a calibration means walking back to a desk and updating a file later, or never.
With native iOS and Android apps, you can scan a QR or barcode label on the instrument, pull up its record, and log the calibration right at the bench or in the field. You can print your own asset labels for free, and use voice input for readings. Every entry is attributed to a user and timestamped on a tamper-evident, hash-chained audit trail, with calibration certificates attached to each asset. When an auditor asks for proof, it is a one-click audit-pack export, PDF and CSV with an integrity page, rather than a scramble.
How Axiospec handles due dates
Axiospec computes the next-due date for every instrument, counts what is due soon and overdue, and sends reminders so recalls do not slip. The Due Calendar and Audit-Readiness Scorecard give you the at-a-glance view. It runs in the browser with native iOS and Android apps, supports multiple sites with per-site views, and fits standards including ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, and IATF 16949. There is a free plan for up to 50 active instruments with unlimited users and no credit card, and you can import from a spreadsheet and export everything anytime.
The fastest way to judge whether the due-date views fit how you work is to look at them with data already in place. The live demo runs on sample data with no signup.
Put it into practice
Import your asset registry in an afternoon, log every calibration to a tamper-evident audit trail, and produce records on demand. Prefer to see it first? Take a self-guided tour with sample data, no signup required.
Axiospec is a documentation and workflow tool. It helps you keep clean, traceable, audit-ready records; certification depends on your own processes, scope, and assessor.
More like this, by email
A short series of practical calibration guides like this one. No spam, unsubscribe with one click.