Skip to content
allanninal.dev/build
Collaborate

Part 5 of 7 · Certification expiry tracker series ~5 min read

How the compliance view answers

A certification register gets read in two very different circumstances. One is planning a job on a Thursday afternoon. The other is an investigation. They want different things, and a view built for the first is nearly useless for the second.

Key takeaways

  • Question one: can this crew do this job today? Answered as a list of who is missing what.
  • Question two: who was certified on this date? Answered from the cards, not from status.
  • The view never says somebody is qualified. It says what card it was shown and when.
  • Historical gaps are visible, because hiding them is how a register becomes untrustworthy.
  • One statistic matters: how many renewals were late. It tells you whether the lead times fit.

Question one: can this crew do this job

Asked on a Thursday, about next Tuesday, by somebody planning work. The useful answer is not a list of everybody’s certifications; it is the short list of what is missing.

How a crew is checked against a job's certification requirementsA vertical chain of four steps entered by a box labelled A job, carrying a date, a site and a crew. Step one asks what the job needs, taken from the job type against a short list of requirements per type. Step two asks who is on it, meaning the crew assigned for that day. Step three asks whether each required certification is valid on that date rather than today, checking the cards for their issue and expiry dates. Step four produces the missing list, naming who, what and when it expires. A note says the check runs against the job date rather than today, because a ticket expiring Monday fails a Tuesday job.AWS ACCOUNTA jobdate, site, crewWhat does it need?from the job typeJob requirementsa short list per typeWho is on it?the crew for that dayValid on that date?not today -- that dateThe cardsissued and expiresThe missing listwho, what, expires whenChecked against the job date, not today. A ticket expiring Monday fails a Tuesday job.
Fig 1. How a crew is checked against a job. The date the check runs against is the job date, which sounds obvious and is the thing most implementations get wrong.
  • Database
  • App integration
  • Management
  • Analytics
  • People

Checking against the job date rather than today is the single most common bug in systems like this, and it fails in exactly the direction that hurts: a card that is valid on Thursday when you check and expires on Monday shows green, and the job is on Tuesday.

Question two: who was certified on this date

Asked in a very different room, usually after something has gone wrong, and the answer has to come from the cards rather than from any current-status field. The register’s append-only shape from Part 3 is what makes this a single query rather than an archaeology project.

The answer format matters too. It is not “yes” or “no” — it is the card: type, number, awarding body, issued and expiry dates, and the photograph. That is what the person asking actually wants, and providing a bare yes would require them to ask a second question anyway.

The honesty line

What the view says, and does not

  • It says: “On 14 March 2026, we held a photograph of a first aid at work card for J. Reed, number 4471-882, issued 12 September 2023, expiring 12 September 2026.”
  • It does not say: “J. Reed was qualified in first aid on 14 March 2026.”
  • Why the difference matters: a card can be revoked, suspended, or forged, and none of those are visible in a photograph. The system’s assurance level is exactly “we were shown this”, and stating more than that is a claim you cannot support.
  • Where more is needed, the awarding body’s own register is the answer, and the card number in this register is what you look up. The system’s job is to make sure you know the number and the date.

The one statistic

A certification register summarised in five numbersA horizontal row of five boxes. Tracked: sixty-one certifications. Current: fifty-nine. In chase: seven approaching expiry. Lapsed: two. Late last year: five of twenty-four renewals were late. A note says the last number is about your lead times rather than about your people.THE COMPLIANCE VIEW, IN FIVE NUMBERSTracked61 certificationsCurrent59In chase7Lapsed2Late last year5 of 24 renewalsThe last number is about your lead times, not about your people.
Fig 2. The compliance view in five numbers. The last one is the only one that tells you to change something about the system rather than about a person.
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • Analytics

Five late renewals out of twenty-four means roughly one lead time in five is set too short, and the register can name which certifications they were. Fixing that is an edit to a sheet and it removes a category of problem permanently, which is a better return than any amount of reminding people harder.

Next: what all of this costs to run.

All posts