Why calibration tracking usually fails
Calibrating an instrument correctly is a solved problem — send it to a provider, or run an in-house check against a known standard, and follow the procedure. What actually goes wrong is upstream of that: nobody notices the due date has passed until someone happens to check, by which point the instrument may already have been used for weeks past its due date.
This is a recordkeeping and visibility problem, not a technical one. A spreadsheet with due dates works until the owner is out sick the week a date passes, a new instrument is added and never entered, or a due date is quietly pushed back "for now" and never revisited.
Setting up calibration tracking per instrument
Give every instrument that requires calibration its own asset record, identified by serial number, not by category. "Calipers" is not trackable; "Calipers #CAL-014" is.
Record the calibration interval for each instrument (set by manufacturer guidance, a quality standard, or regulatory requirement, depending on the instrument and industry) and calculate the next due date from the last calibration performed, not from a fixed calendar date that ignores when the instrument actually last passed.
Label each instrument with a barcode or QR code so logging a calibration event, or checking an instrument's status before use, is a scan rather than a lookup in a separate document.
- Individual record per instrument, by serial number
- Calibration interval set per instrument type
- Next due date calculated from the last actual calibration
- Barcode or QR label for fast status checks
Catching overdue instruments before they get used
A due date that requires someone to remember to check it is a due date that will eventually be missed. The fix is an alert tied to the instrument's own record that surfaces automatically as the due date approaches, rather than relying on a person scanning a spreadsheet every week.
Where it matters most, flag an overdue instrument's status so it is visibly not available for use, rather than leaving it looking identical to a compliant one on a shelf. The goal is to make "in date" and "overdue" a difference someone can see at a glance, not something they have to go check a file to confirm.
When an instrument does lapse, log the gap explicitly: the last known-good calibration date, and every measurement taken between that date and the next valid calibration, so the traceability question ("was this reading trustworthy") can actually be answered rather than assumed.
Making it sustainable
This works reliably only when it costs almost nothing to keep current — logging a calibration should be a scan and a date entry, not a form. The moment tracking becomes a chore, it starts slipping, which is exactly the failure mode it was meant to prevent.
In StockFlow, the Assets module tracks maintenance and readiness per asset, including a due date and overdue alerting, so a calibration lapse shows up as a status change on the instrument's own record instead of depending on someone remembering to check.
Trusted by small businesses
What our customers say
“Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!”
“Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.”