How to Set Up Training Expiry Alerts That Actually Work

A first aid certificate expires on a Tuesday. Nobody notices until Friday, when an auditor asks for it. By then, you have been operating with a compliance gap for four days and no record of how it happened.

This is the reality of training expiry management for most UK businesses. The training gets done. The records exist somewhere. But when a certificate lapses, nobody finds out until it is too late.

The problem is not that people forget. The problem is that the alert systems most organisations rely on are fundamentally broken.

Why calendar reminders fail

The most common approach to tracking training expiry dates is also the least reliable: someone adds a reminder to their Outlook calendar.

This fails for three reasons.

First, calendar alerts are personal. When the person who set the reminder is on leave, off sick, or leaves the company, the alert goes with them. Nobody else knows the renewal was due.

Second, calendar alerts are easy to dismiss. A pop-up appears, you are in the middle of something else, you click "dismiss" and move on. There is no escalation. No follow-up. No audit trail showing the alert was sent and ignored.

Third, calendar alerts do not scale. If you have 20 staff members each with five training requirements, that is 100 expiry dates to track. Managing 100 individual calendar entries across multiple people is not a system. It is a liability.

Why spreadsheet conditional formatting is not enough

A step up from calendar reminders is the spreadsheet approach. You build a training matrix in Excel, add expiry dates, and use conditional formatting to turn cells red when a certificate has lapsed.

This is better than calendar reminders. At least the data is in one place. But it still has critical weaknesses.

Spreadsheets do not send alerts. Conditional formatting only works when someone is looking at the spreadsheet. If nobody opens the file for three weeks, expired certificates sit there silently turning red while you remain non-compliant.

Formulas break. Someone inserts a row and the formula references shift. Someone pastes data over the formula. Someone saves a copy to their desktop and now there are two versions, neither of which is the source of truth.

There is no escalation. A red cell in a spreadsheet does not email anyone. It does not notify a manager. It does not create a task. It just sits there, hoping someone will notice.

That said, if you are currently using nothing at all, a spreadsheet with expiry tracking is a genuine improvement. Here is the formula to flag certificates expiring within 30 days:

=IF(expiry_date - TODAY() < 30, "EXPIRING", "OK")

Replace expiry_date with the cell reference containing the certificate expiry date. Use conditional formatting to highlight cells containing "EXPIRING" in amber and "EXPIRED" (where the date has already passed) in red:

=IF(expiry_date < TODAY(), "EXPIRED", IF(expiry_date - TODAY() < 30, "EXPIRING", "OK"))

This gives you a basic traffic-light view. It will catch some gaps. But it will not catch all of them, because it relies on a human opening the file and acting on what they see.

What an effective alert system looks like

A training expiry alert system that actually works has four characteristics.

1. Automated alerts at multiple intervals

A single reminder 30 days before expiry is not enough. By the time you book the training, schedule the staff member, and wait for the provider's next available date, 30 days can disappear quickly.

Effective systems send alerts at three intervals:

90 days before expiry: planning alert. Enough time to book training, arrange cover, and budget for the cost.
60 days before expiry: action alert. Training should be booked by now. If it is not, this is the prompt to escalate.
30 days before expiry: urgent alert. The certificate is about to lapse. If training is not already scheduled, you are about to have a compliance gap.

Each alert should include the employee name, the training type, the expiry date, and the action required. No vague "training due soon" messages.

2. Escalation to managers

If the person responsible for booking the training does not act on the 90-day alert, the 60-day alert should copy in their line manager. If the 60-day alert is also ignored, the 30-day alert should go to the compliance lead or operations director.

Escalation turns a passive notification into an accountability chain. Someone has to own the renewal, and if they do not, someone more senior finds out.

3. A dashboard showing the full picture

Individual alerts are useful. A dashboard showing all upcoming expiries across the entire organisation is essential.

This is what separates a compliance system from a reminder system. A dashboard lets you see patterns: are all the forklift licences expiring in the same month? Is one team consistently late on renewals? Are there training types where the renewal pipeline is empty?

Without this view, you are managing compliance one alert at a time. With it, you can plan proactively.

4. An audit trail

Every alert sent, every action taken (or not taken), and every renewal completed should be logged. When an inspector asks how you manage training expiries, you need to show the system, not just the outcome.

An audit trail also protects you internally. If a manager ignores three alerts and a certificate lapses, the log shows exactly when the warnings were sent and to whom.

How to build this with what you have

If you are not ready to invest in dedicated training matrix software, you can approximate some of these features using existing tools.

Microsoft 365 / Power Automate: Create a flow that reads expiry dates from a SharePoint list or Excel file and sends email alerts at defined intervals. This gives you automated alerts and basic escalation, but requires someone with Power Automate skills to set up and maintain.

Google Sheets + Apps Script: Write a script that runs daily, checks expiry dates, and sends emails via Gmail. Free, but fragile. If the script breaks, nobody gets alerted and nobody knows the script broke.

Shared spreadsheet + manual review: At minimum, designate one person to open the training matrix every Monday morning and check for upcoming expiries. Put this in their job description. Make it a standing agenda item in their one-to-one. This is the low-tech option, but it is better than hoping someone remembers.

None of these approaches give you a proper audit trail or dashboard. They are workarounds, not solutions. But they are better than the alternative of discovering a lapsed certificate during an HSE visit.

The cost of getting it wrong

Under the Health and Safety at Work Act 1974, employers must ensure that employees receive adequate training. A lapsed certificate means that the legal obligation to maintain competence is not being met, even if the employee's actual skills have not changed.

The fines for training failures are substantial. But the operational cost starts earlier: insurance claims where training records are incomplete, contracts lost because compliance evidence is out of date, and the time spent firefighting renewals instead of managing them.

A proper training compliance system does not eliminate training requirements. It eliminates the gaps between when a certificate expires and when someone notices.

Where your training matrix fits in

Your training matrix is the foundation. It tells you who needs what. Expiry alerts are the mechanism that keeps it current. Without alerts, a training matrix is a snapshot that becomes outdated the moment a certificate lapses. With them, it is a live compliance record.

If your current matrix does not include expiry dates for every entry, start there. You cannot alert on dates you have not recorded.

TrainProof builds expiry alerts into every training record. Automated notifications at 90, 60, and 30 days. Escalation to managers. A live dashboard showing every upcoming renewal across your organisation.

Join the waitlist to be notified when it is ready.