Expired equipment runs no analysis
The rule against using equipment with expired calibration is written in every SOP. The trouble is an SOP blocks no one: it relies on the analyst remembering, on a busy day, to check the label before powering up the instrument. Here the rule leaves the page and becomes a system lock. Each instrument runs through a state workflow, the status light shows where it stands on the spot, calibration notifications fire on their own, and using a failed or expired one is blocked at the source. You don't trust that nobody used it. The system wouldn't let them.
Each instrument runs through a workflow.
In use, in calibration, in maintenance, condemned. The instrument moves between states and, in each one, the system knows whether it can produce a result. Not a loose label, a state machine.
Calibration notifications fire on their own.
Alerts at 90, 60, 30 and 0 days before expiry, sorted by priority (urgent, high, medium, low). You open the screen and see how many are urgent, you don't find out during the audit.
Expired equipment is blocked.
Failed or expired calibration turns it unavailable. A result won't leave an instrument that can't produce one, so the SOP rule becomes a lock instead of trust.
Every calibration with its proof attached.
Date, due date, certificate number, result (approved, approved with restriction or rejected), cost and notes. Log it and the status and the light recalculate instantly.
Maintenance that already opens the purchase.
Sent for external maintenance? The system generates the linked purchase requisition, with supplier, deadline and cost, so quoting and payment run in the Purchasing module. Maintenance doesn't die in an email.
Condemning is an irreversible, controlled action.
Taking equipment out of service requires a reason, disposal, authorization and an attached condemnation report. Vanish in the dark, no. Vanish with an audit record, yes.
Approved with restriction is a real state.
Calibration isn't only pass or fail. Approved with restriction is logged, so whoever uses the instrument knows the limitation instead of treating it as flawless.
Each instrument's cost shows up.
Each certificate and each maintenance stores its cost. By year-end you know how much each instrument cost to keep, not just that it cost something.
The workflow running: alert fires, equipment moves, status returns
The state engine is configurable and runs on its own. Watch the instrument leave In use as calibration nears expiry, fire the notification, move, and come back once calibration is logged.
The equipment record holds everything the auditor asks for
Calibration, maintenance, nonconformity, quotes, shipments and history in one place. You don't rebuild the instrument's life across three folders in front of the auditor.
Calibration with certificate and periodicity.
Validity, last calibration, periodicity and status at the top. The calibration history sits below, with the certificate attached. Metrological traceability in the record, not in a network folder.
Maintenance per ISO/IEC 17025 §6.4.
Preventive, corrective and predictive with plan, periodicity and history. Equipment that's down reflects on availability right away, with no one having to flag it.
Nonconformity tied to the instrument.
The equipment's NC opens right there, with root cause, corrective action and effectiveness check. The instrument's deviation doesn't become a loose case outside the QMS.
Quotes and shipments without leaving the record.
The maintenance purchase requisition becomes a quote in the Purchasing module, and shipments in progress show what's out for calibration or repair, with an expected return.
Frequently asked questions
Does the system really stop the use of uncalibrated equipment?
Yes. Equipment that failed or has expired calibration becomes unavailable. A result won't leave an instrument that can't produce one, so the SOP rule becomes a system lock instead of relying on someone remembering.
How does the calibration expiry warning work?
Each instrument has a periodicity and a due date, and the status is calculated by the system. The status light shows the state on the spot and notifications warn as calibration nears or has already passed. You schedule recalibration ahead, not the night before.
Where does the calibration certificate live?
Attached to the instrument itself, along with date, due date, certificate number, result and cost. Metrological traceability lives in the record, not in a separate network folder nobody finds during the audit.
Does the instrument come back available on its own when maintenance ends?
Not in the dark. Availability follows the status you log: close the maintenance and record the calibration or verification result, the status light recalculates and the instrument can be used again. While the status says it's down, it stays blocked, even if the physical repair is already finished.
Want to see the QMS running with your lab’s routine?
Get through the next audit without burning a weekend night hunting for PDFs. Book a demo and see document control, CAPA and Westgard working with a case similar to your lab's.