What is 30/60/90 expiry tracking?

A rolling dashboard of everything expiring within 30, 60 and 90 days. 90 days is planning territory (rebooking courses), 60 is action territory (reminders out, dates agreed), 30 is escalation territory (anything still unrenewed gets chased hard). The point is that nothing crosses its expiry date unseen.

Why do certificate expiries slip through?

Because nobody re-checks two thousand spreadsheet rows every Monday. Expiry is silent — the certificate looks identical the day after it lapses. Without a system watching dates continuously, discovery happens at the worst moment: when a worker is turned away at the gate or an auditor samples the record.

Who should receive expiry alerts?

Two audiences: the provider's own team (to plan courses and capacity) and the client companies whose workers hold the certificates (to rebook in time). In Sentinel, renewal reminders go to the companies that need to rebook, triggered from the same expiry dashboard.

Sentinel / Guides / Expiry tracking

The 30/60/90 method for expiry tracking

Certificates don't expire suddenly. They expire silently — the document looks identical the day after it lapses. The fix is a rolling watch, not a better memory.

Why expiries slip through

Nobody re-checks two thousand spreadsheet rows every Monday. That's the whole story. Expiry dates were recorded correctly, filed correctly — and then time passed, quietly. Discovery happens at the worst possible moment: a worker turned away at the gate, a client audit sampling exactly the lapsed record, a contract renewal asking for proof.

The rolling windows

30 / 60 / 90 — what each window means

90 daysPlanning territory. Enough runway to schedule courses, group renewals into sessions, and plan trainer capacity. Nothing here is urgent — which is exactly why it's the right time to act.

60 daysAction territory. Reminders go to the client companies whose workers are expiring; dates get agreed; bookings land in the calendar.

30 daysEscalation territory. Anything still unrenewed gets chased hard, by name. Whoever crosses this line unbooked is a known risk, not a surprise.

The method's power is that it's rolling: the dashboard is never "done", it's simply always current. The question changes from "did anyone check the sheet?" to "is anything in the red window?" — a question one glance answers.

Renewals are revenue, not admin

For a training provider, every expiring certificate is a rebooking waiting to be claimed — by you or by a competitor. Providers who remind client companies at 60 days don't just prevent compliance gaps; they capture the renewal course. Expiry tracking done well is a sales system wearing a compliance badge.

What this looks like in Sentinel

Sentinel's expiry dashboard watches every certificate across rolling 30/60/90-day windows, and renewal reminders go to the companies that need to rebook — triggered when you need them, from the same register that issued the certificates. Every action lands in the audit log. 9,000+ certificates run on this loop in production.

Know what expires before it expires

Rolling 30/60/90 windows, company reminders, audit log — one register doing the watching for you.

Book a demo →

Common questions

What is 30/60/90 tracking?

A rolling dashboard of everything expiring in the next 30, 60 and 90 days — plan at 90, act at 60, escalate at 30.

Why do expiries slip through?

Because expiry is silent and spreadsheets don't watch themselves. Systems that alert continuously do.

Who should get the alerts?

Your team (capacity and course planning) and the client companies who need to rebook — Sentinel sends the latter automatically.

Practical guidance from the Sentinel team. Validity periods are set by your course categories and accreditation requirements — configure the windows to match yours.