Part of the Calibration series on the Mobtag platform.
In short: Customers want scan → see cert → see next due. You need the same object to power QA, dispatch, and the dispute the week after a failed visit. A single live profile per item beats inbox archaeology.
Whether you are UKAS-driven or in-house, the experience is converging: a portal moment at the item, with a history that matches the bench. The expensive failure is not a missing PDF—it is competing PDFs with the same serial and a different “final” outcome.
What “control” means in practice
- Identity on the item: the tag and the record are unambiguous.
- Supersession, not amnesia: a new cert is added; the story of the old one is still explainable.
- Next due is operational: it reflects lead time, site access, and carrier days—not a naive calendar tick.
| Stakeholder | The question they are really asking |
|---|---|
| Lab / bench | What is my queue, what is OOT, where is the evidence? |
| End customer or site | Pass/fail, when next, and the PDF in one place |
| Quality / UKAS | Trace to competence, to procedure, to change over time |
When customer and regulator share the same week
If a surveillance visit and a major account review line up, “two packs” in parallel is how drift starts. The winning state is: one chain from the physical item to the evidence, with named versions when certificates change.
Summary: Control is a single, trusted profile per item—certificates, due dates, and a history every audience can use without a rebuild the night before the meeting.