Skip to content
allanninal.dev/build
Collaborate

Part 4 of 7 · Certification expiry tracker series ~6 min read

How a renewal gets chased

Everything else in this system is bookkeeping. This is the part that prevents the Monday at the gate, and it rests almost entirely on one number per certification type: how long the renewal actually takes to arrange.

Key takeaways

  • The lead time is a property of the certification, and setting it right is most of the work.
  • Four steps: the holder, the holder again, the manager, and whoever schedules the work.
  • A booked course pauses the chasing; it does not stop it.
  • On expiry day the person is marked as not currently holding it, loudly and visibly.
  • An expired ticket keeps chasing forever. It never times out and never goes quiet.

Lead time, not a fixed reminder

CertificationTypical lead timeWhy
Vocational medical120 daysAppointment availability, then processing
Site safety card90 daysTest centre availability plus card delivery
First aid at work90 daysCourse dates near you are sparse
Abrasive wheels30 daysHalf-day course, widely available
Manual handling21 daysOften delivered in house
Insurance-mandated refresher60 daysCertificate must be with the insurer before renewal

Those numbers are the whole system. A thirty-day reminder on a certification with a hundred-and-twenty-day lead time is a reminder that arrives ninety days too late to help, and a ninety-day reminder on a half-day course is one that gets ignored and then forgotten. Neither of those is fixed by better message wording.

The ladder

The four-step escalation for an approaching certification expiryA vertical chain of five steps entered by a box labelled Expiry minus lead time, computed per certification. Step one tells the holder what is expiring, when, and how to book; a reply that it is booked exits to Booked, which pauses until the course date. Step two asks whether there has still been nothing after fourteen days, exiting to Tell them again, shorter and with the date. Step three asks again at half the lead time, pulling the holder's manager from the staff list and exiting to Tell the manager with the holder copied in. Step four asks again at fourteen days out, pulling whoever does work planning and exiting to Tell scheduling so that work can be moved. Step five is Expiry day, where the person is marked as not current, visibly. A note says the fourth step is the one that saves the day, because work gets rescheduled before the gate.AWS ACCOUNTExpiry minus lead timeper certificationTell the holderwhat, when, how to bookBookedpause until the daterepliesStill nothing?after 14 daysTell them againshorter, with the dateyesStill nothing?at half the lead timeTheir managerfrom the staff listTell the managerholder copied inyesStill nothing?at 14 days outWhoever scheduleswork planningTell schedulingso work can moveyesExpiry daymarked not current,visiblyThe fourth step is the one that saves the day: work gets rescheduled before the gate.
Fig 1. The escalation ladder, keyed off the lead time rather than the calendar. The step that actually prevents lost work is the fourth, because it reaches somebody who can move a job.
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • People

Booking pauses rather than stops

“I’ve booked it for the 14th” is the answer everybody wants, and it is not the end of the story. Courses get cancelled, people miss them, and cards take weeks to arrive afterwards. So a booking records a date and suppresses chasing until a few days after it, at which point the system asks a single question: did it happen, and do you have the card?

If the answer is yes, a photograph closes it. If there is no answer, the ladder resumes from wherever it had reached, which is usually quite far along by then. The failure mode this prevents is the one that catches most businesses: a booking is treated as a resolution, everybody relaxes, and the card never arrives.

Expiry day

On the day, the person is marked as not currently holding that certification. Not expired-soon, not amber — not holding it. That distinction is the point of the whole system, because the alternative language lets people keep working on the assumption that a certificate is basically fine.

What happens on the day a certification expiresA horizontal row of five boxes. Marked not current: on the day, at one minute past midnight. Holder told: plainly. Manager told: and whoever schedules work. Stays visible: no archiving and no greying out. Chases forever: weekly until it is replaced. A note says nothing here times out and a lapsed ticket is louder next month than it is today.WHAT HAPPENS ON EXPIRY DAYMarked not currenton the day, at 00:01Holder toldplainlyManager toldand schedulingStays visibleno archiving, no greyChases foreverweekly until replacedNothing here times out. A lapsed ticket is louder next month than it is today.
Fig 2. Expiry day, and afterwards. The unusual property is that the chasing never stops: a lapsed certification is the one thing in this series with no expiry on its own alert.
  • Security & identity
  • Management
  • People

The forever part is deliberate and is the opposite of how most alerting works. Every other reminder in this series eventually escalates and then rests. A lapsed certification does not, because the situation it describes does not improve with time — it gets worse, and a system that goes quiet about it after a fortnight is actively misleading.

Getting the lead times right

  • Start from how long the renewal took last time. The register knows: it has the gap statistics from Part 3.
  • Add the card delivery time, not just the course. A ticket that arrives three weeks after the assessment needs three weeks more lead.
  • Ask the person who books them. They know which courses are hard to get near you, and that knowledge is not written anywhere.
  • Revise annually. A lead time that produced two late renewals last year is too short, and the fix is a number in a sheet.

Next: the compliance view, and the one question it is built to answer quickly.

All posts