Separate four connected records
The following model is a practical design proposal, not a prescribed set of fields:
| Record | Question it answers | Illustrative content |
|---|---|---|
| Equipment item | What are we managing? | Internal identifier, description, location, custodian and lifecycle state. |
| Requirement | What work or evidence is expected? | Activity, trigger or due rule, applicable criteria and responsible role. |
| Work event | What actually happened? | Date, performer, result, notes and related requirement. |
| Evidence and decision | What supports the next action? | Linked document, review outcome, restrictions and authorisation where required. |
Keeping these separate helps you ask better questions. Changing a location should not silently alter a completed service event. Updating a future due rule should not overwrite the rule against which earlier work was assessed.
Use one equipment item as a worked example
Consider a fictional balance, EQ-DEMO-017. The register identifies the item and its custodian. It has a scheduled activity and a separate check defined by the laboratory’s procedure.
The demonstrator records work against the relevant requirement and attaches synthetic evidence. A reviewer can then show how the result was accepted, rejected or returned for more information—if those controls are part of the product being evaluated.
Do not make the example succeed only because the demonstrator knows where an unrelated PDF was stored. Ask another evaluator to retrieve the same history using the equipment record. That tests the connection between the records rather than memory of the demonstration.
Do not collapse different activities into one label
Calibration, verification and maintenance may all appear in an equipment history, but they answer different questions. The international vocabulary defines calibration and verification separately. Use those distinctions when naming records and deciding what evidence is appropriate.
A generic completed checkbox can conceal an important difference: work took place, but its result may still require review. Similarly, a requirement may be current while the equipment has a separate restriction. Ask the supplier to explain the state model in plain language.
Test the exception before trusting the green status
Create a fictional failed check. Ask what happens next. Is the issue linked to the affected item? Can a person record a restriction? Who decides whether the equipment may return to use under your procedure? Does the previous failure remain visible after corrective work?
These are evaluation questions, not assertions that every system must use one particular workflow. The important point is that your laboratory’s responsibility should not disappear behind an unexplained status colour.
An overall status should also have an understandable basis. Ask which requirements contribute to it, how missing information is treated and whether any overdue item can be hidden by a later unrelated event.
Choose useful register fields, then control changes
Avoid collecting fields simply because the software allows them. Begin with the information needed to identify an item, assign responsibility, find its records and interpret its status. Add specialist fields when there is a clear use.
Agree how items are added, relocated, retired and corrected. Decide which historic records must remain associated with a retired item and how duplicate register entries will be handled. Test those actions with synthetic data before importing a large register.
Evaluate the complete history
A practical acceptance exercise is to ask a second person to retrieve one item’s relevant requirement, completed work, evidence and decision. Give them the equipment identifier, not a set of hidden instructions. Record missing links and ambiguous labels as specific gaps.
For the scheduling detail, use the calibration tracking guide. For the product boundary, review AureqoEq. A Request a product walkthrough can start with one representative item and one exception, using demonstration data rather than your live equipment records.