Calibration tracking software keeps in one place which measuring instruments in a company (calipers, scales, pressure gauges, thermometers, test equipment) were calibrated when, when the next calibration is due and where the certificate is. In short, it lets you prove with a document during an audit that "the instrument used for this measurement was within valid calibration on that day". Reminding people of dates is not enough for that: an overdue instrument must be taken out of use, and the measurements affected by an instrument that fails calibration must be traceable.
What does calibration tracking software do?
In many companies calibration runs on a spreadsheet and stickers on the equipment. That works as long as the list is kept up to date; but when an instrument moves to another department, a certificate stays buried in an inbox or the responsible person goes on leave, tracking breaks, and this is usually discovered on audit day.
- A record for every instrument: serial number, measuring range, location, owner and calibration interval.
- Alerts to the owner and the quality team for upcoming and missed due dates.
- The result, laboratory and certificate of every calibration in the instrument history.
- Overdue or failed instruments marked as "out of service".
- The instrument list and certificates an auditor asks for, exported in a few clicks.
Why is the core record the calibration event, not the instrument?
It is tempting to store a single "last calibration date" field on the instrument record, but that field overwrites the previous value every time it is updated. When an auditor asks about a measurement from six months ago, you cannot show the state on that day. The right model stores every calibration as a separate record: when it was performed, the result, the next due date and the certificate file. The instrument’s current status is calculated from the latest record; history is never deleted or edited.
An overdue instrument should not just raise a reminder, it should be out of service. The difference between "we sent a reminder" and "nobody could measure with that instrument" is whether the audit produces a finding.
In the example below usability is calculated from the latest calibration record, and when a calibration fails the measurements taken with that instrument since the last pass are listed.
type Calibration = {
instrumentId: string;
performedAt: Date;
result: 'pass' | 'fail';
nextDueAt: Date;
certificateFile: string;
};
// An instrument may be used only if its latest calibration passed and is not overdue.
function isUsable(history: Calibration[], instrumentId: string, now: Date): boolean {
const latest = history
.filter((c) => c.instrumentId === instrumentId)
.sort((a, b) => b.performedAt.getTime() - a.performedAt.getTime())[0];
return latest !== undefined && latest.result === 'pass' && latest.nextDueAt > now;
}
// When a calibration fails, list the measurements taken since the last passing one.
function affectedMeasurements<T extends { instrumentId: string; measuredAt: Date }>(
measurements: T[],
instrumentId: string,
lastPassAt: Date,
failedAt: Date,
): T[] {
return measurements.filter(
(m) =>
m.instrumentId === instrumentId && m.measuredAt >= lastPassAt && m.measuredAt <= failedAt,
);
}How are calibration intervals and due dates set?
Software does not decide the interval; the manufacturer’s recommendation, frequency of use, the instrument’s past stability and your industry’s requirements do. The program’s job is to store that decision per instrument and enforce it. The next due date should be calculated from the actual calibration date, not the planned one, so a late calibration does not shorten the next cycle. Alerts are sent a set time before the due date by a scheduled task (cron job), and the same instrument gets a single alert per day.
Instruments sent to an external laboratory need their own status: "at calibration". During that time the instrument should not appear as available, and any replacement unit should be recorded too. If information about who and which department holds the instrument relies on the same data as your asset and custody tracking software, the two lists never drift apart.
What happens when an instrument fails calibration?
If calibration shows the instrument was out of tolerance, the question is not only how to adjust it: every measurement taken and every product released with it since the last passing calibration is now suspect. The program should be able to produce that list, which requires inspection and measurement records to store which instrument was used. The result of the impact analysis becomes a nonconformance, and the root cause, corrective action and effectiveness check run through nonconformance and CAPA software.
Calibration should not be confused with maintenance either. Maintenance keeps an instrument working; calibration ensures the value it reads is correct. For periodic maintenance of production machines see our article on maintenance management software; the two processes can share an equipment record but run on separate schedules.
Certificate archive and audits
Each calibration certificate should be stored as a file attached to its record, only authorized people should be able to upload it, and an uploaded file should not be editable afterwards. If you want to manage certificate and procedure versions in one place, our document management system article goes into detail. Interpreting accreditation and standard requirements is your certification body’s role; this article is not a substitute for certification consulting.
Off-the-shelf software or custom development?
For a business with a few dozen instruments that does not keep measurement records in another system, an off-the-shelf calibration tool is usually enough. Custom development makes sense when inspection and measurement records already live in your own production tracking (MRP) system and impact analysis must run on that data automatically, when you operate several sites, or when an instrument’s out of service status must show up on production screens immediately.
Conclusion
Good calibration tracking software stores every calibration as its own record, calculates the due date from the actual date, takes overdue instruments out of service and can find the affected measurements when a calibration fails. If you would like to design your quality processes together, see our corporate solutions page or request a quote.