Certification Currency Is an Operations Problem, Not an HR One

Ask any inspection contractor how they track certification currency and you will hear about a spreadsheet. Ask how they last discovered an expired certification and you will hear about a client gate, a pre-mobilisation check, or an auditor. Those two answers together describe the entire problem.

The number of clocks is the issue

A single technician certified in three methods carries a certification date per method, an annual near-vision acuity examination, a colour-contrast examination where the method requires it, documented on-the-job hours, site inductions per client, and often an operator-specific approval with its own validity. That is comfortably ten independent expiry dates for one person. A twelve-technician company is tracking well over a hundred.

Spreadsheets do not fail because people are careless. They fail because one row per person cannot represent that structure, and because the vision examination — running on a shorter cycle than the method certification it supports — falls out of sync with everything around it.

Why reminders do not work

A reminder informs someone about a lapse that has already happened or is about to. It does not prevent the assignment. The control that actually works is a dependency between the qualification record and the dispatch action: if the certification, the vision examination, the client approval or the instrument calibration is not current for the scope being assigned, the assignment cannot be made.

That is an operations control, not an HR one, which is why holding certificates in an HR system rarely helps. HR systems model people and roles; they have no concept of dispatch, and no concept of method-level qualification against a written practice revision. Platforms built for inspection operations — see how inspection management software enforces currency at the point of dispatch — treat it as a hard constraint rather than a report.

The second half: point-in-time recovery

Preventing the lapse solves tomorrow's problem. The audit problem is different and older: an auditor picks a report signed eighteen months ago and asks whether that person was qualified on that date. A system holding current state cannot answer, and the answer cannot be reconstructed retrospectively. Freezing the certification and calibration state onto each report at issue is trivial prospectively and impossible in arrears — which is why it is worth doing before an audit is scheduled rather than after one is announced.

What to check this week

• How many independent expiry dates does your business actually track? Count them; the number is usually a surprise.
• Can a technician whose vision examination expired last week be assigned to a job today? Test it rather than assume.
• Pick one report from eighteen months ago. Can you produce the signatory's qualification state as at that date?

For a fuller treatment of how this scales past thirty technicians, this walkthrough of tracking ASNT certification expiry across a whole technician base covers the data model and the migration sequence.