Separate the requirement from the event
A calibration requirement defines what must happen and when. A calibration event records what actually happened. Keeping these concepts separate allows the schedule to generate due work while preserving each historical outcome and its supporting evidence.
When evaluating software, check whether an interval change rewrites history or only affects future work. Earlier events should remain understandable against the requirement that applied at the time.
Make due-state logic explainable
A dashboard can show current, due soon or overdue, but staff also need to understand how that state was calculated. Look for visible due dates, requirement intervals, completed events and any manual decisions affecting availability.
Explainable state becomes especially important when an item has several requirements, such as calibration, maintenance and inspection, with different frequencies.
- Requirement and interval
- Last accepted completion
- Next due date
- Responsible person or team
- Current work state
- Exception or restriction context
Test failure and remediation workflows
A passing calibration is the simple case. The more revealing test is what happens when a result is unacceptable, evidence is incomplete or the item requires repair. Software should preserve the failed outcome and support the subsequent remediation and return-to-service record.
Avoid systems where staff must overwrite the original event to make the current dashboard appear correct. That destroys the history needed to explain the decision later.
Connect certificates and evidence
A calibration certificate should be attached to the event it supports, not only to a general equipment folder. The connection should remain clear when another event occurs or a revised document is uploaded.
Consider file access, review state, version behaviour and the information visible in a timeline. The objective is not to collect documents; it is to keep useful evidence beside the work and decision.
Use reminders as part of a workflow
Notifications should prompt action without becoming the system of record. Ask whether reminders lead staff to a defined work item, whether ownership is visible and whether completion updates the next due state consistently.
A reminder-only tool may still leave the laboratory coordinating work through inboxes and spreadsheets. The benefit of a focused system is the connected record behind the reminder.
Choose pilot measures that reflect assurance
A short pilot can measure whether users find due work faster, attach evidence consistently, understand exceptions and reconstruct an item's history. Include equipment with different intervals and at least one non-routine outcome.
AureqoEq is being developed to connect equipment, requirements, work, evidence and approval events. Early-access evaluation should establish whether that model matches the laboratory's actual assurance process.