What Is a Calibration Recall System? A UK Quality Manager's Guide
Published 4 July 2026
"Calibration recall" is one of those phrases that sounds like jargon until the day you fail an audit because of it. A recall system is simply how you get an instrument back for calibration before it falls due — before a workshop uses it past its calibration date and casts doubt on everything measured with it. This guide explains what a calibration recall system does, why a spreadsheet recall list quietly fails, and how the whole thing maps to what an ISO auditor checks.
The Problem a Recall System Solves
Every calibrated instrument has an interval and a due date. The interval is set once — the harder part is acting on the due date, every time, across a fleet of instruments that all come due on different days. The failure is mundane: an instrument's calibration lapses because nobody noticed it was approaching due, it gets used on a production measurement, and now there is a question over whether that measurement is valid. Multiply that across fifty or two hundred instruments and the odds of one slipping through in any given quarter are high.
A recall system is the mechanism that closes this gap. It watches the due dates, raises the instruments approaching due, and prompts the action: recall the instrument, send it for calibration, or take it out of service until it is done. The point is that nothing is used past its due date by accident.
What a Recall System Has to Do
A working calibration recall system, whether in software or run by hand, needs four things.
Know every instrument's interval and due date. This sits on the equipment register — each instrument's calibration interval and the date its next calibration falls due. Without a complete, current register, a recall system is recalling against incomplete data. Setting sensible intervals in the first place is its own task, with established methods for choosing and reviewing them.
Look ahead, not just at today. A due-date list tells you what is overdue. A recall system tells you what is about to be due, with enough lead time to act. That look-ahead window is the whole value — it is the difference between catching a calibration before it lapses and discovering the lapse afterwards.
Prompt an action, to a person. The look-ahead is only useful if it reaches someone who can act. A red cell in a spreadsheet that nobody opens is not a prompt. An email, a dashboard flag, a task — something that lands in front of the quality manager or workshop supervisor in time — is.
Record what happened. When an instrument is recalled, sent, and returned calibrated, that has to land back on the record with the new certificate and the new due date. A recall that is not recorded leaves the next cycle blind.
Why the Spreadsheet Recall List Fails
Most teams start with a spreadsheet and a due-date column, and call it a recall system. It is not — it is a due-date list, which is a different thing. The spreadsheet has no alarm. It cannot look ahead and tell you on its own; it depends on a human opening it, sorting it, and acting, every single week. Conditional formatting turns a cell red, but red cells do not email anyone, and the file only turns red once the date is close — by which point, if nobody opened it, the instrument may already be overdue.
The deeper issue is that a spreadsheet recall list has a single point of failure: the person who remembers to check it. Go on leave, get busy with an audit, or simply skip a week, and the recall does not happen. A real recall system removes the dependency on memory. This is the same reason teams move from tracking calibration in Excel to dedicated software — not the calibration maths, but the controls around it, including recall.
How Recall Maps to ISO
The recall system is not named as such in the standards, but it is how you satisfy a requirement that is. ISO 9001:2015 Clause 7.1.5 requires that measuring equipment is calibrated or verified at defined intervals and is identified so its calibration status can be determined. "Defined intervals" is only meaningful if something acts on them before they expire — that something is the recall system. For an accredited laboratory under ISO/IEC 17025:2017, the same logic applies to keeping reference standards and equipment within their calibration status; the recall mechanism is what keeps the schedule honest. An auditor will not ask "show me your recall system" by name — they will pick an instrument and ask whether it was in calibration when it was used. A recall system is how you can always answer yes.
How CalProof Fits
CalProof runs the recall system from the equipment register. Each instrument carries its interval and due date; the system looks ahead and fires a reminder a configurable number of days before each calibration falls due, by email and on the dashboard, so instruments are recalled in time to be sent and returned before they would have been used out of calibration. When a calibration comes back, the new certificate and next due date update the record, and the audit trail logs it. The compliance dashboard shows due, overdue, and in-calibration status across every instrument at a glance.
GBP pricing from £29 a month. No per-user fees on Pro and above. UK data hosting. No long-term contract.
To see the output an auditor would see, the sample audit pack is ungated and downloads as a single PDF.
Sources
- ISO 9001:2015 — Quality management systems — Requirements
- ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories
This guide applies to UK manufacturers and laboratories under ISO 9001 or ISO/IEC 17025. It is general guidance based on the published standards; the requirements that apply to your organisation depend on your certification scope and your auditor's interpretation. Verify against your certification body or UKAS assessor. This is not legal or compliance advice.