Refresher training: tracking the deadlines without a parallel spreadsheet
Echipa HR 365 · reviewed 2026-09-04 · 5 min read
Deadlines are not tracked per course, but per person–training pair: each has its own expiry date, calculated from the day that person passed, not from the day the session was held. The difference looks small and is exactly why deadline spreadsheets break in their second year.
Why the register breaks in year two
In year one everything is simple: a session was held, everybody attended, the deadline is twelve months out for all of them. In year two you get the people who missed it and caught up later, those who joined in between, those who moved to a different post needing different training. From that point, a column with a single date describes nobody’s reality.
| Field | Why it is needed | The frequent mistake |
|---|---|---|
| The person | The deadline is individual, not a group one | It is kept per department or per session |
| The type of training | Each has its own interval | They all get the same interval |
| The date of passing | The deadline is calculated from this | The session date is used instead of the pass date |
| The interval, in months | It differs by type and sometimes by post | It lives in somebody’s head, not in the register |
| The calculated deadline | It is recalculated at every refresher | It is filled in by hand and stays stale |
| The evidence | The file or the verification code | It is kept somewhere other than the register |
The alert threshold: 45 days, not 7
An alert a week before expiry leaves time for nothing: the session has to be scheduled, the trainer has to be free, people have to be taken off shift. A 45-day threshold lets the refresher be scheduled in the month’s normal rhythm, not as an emergency.
The three thresholds that work together
- System or register — at 45 days: it appears on HR’s planning list, bothering nobody
- HR — at 21 days: the session must already have a date and an attendee list
- HR and manager — at 7 days: those not signed up appear by name to their manager, with the exact deadline
The third threshold is the only one that reaches the manager. Send all three and the alerts become noise, and the manager filters out all of them — including the one that mattered.
The monthly list has to be short
A correct register in a 150-person company with three annual training types produces roughly 35 deadlines a month. If your list consistently shows over 60, it means all the training was done in the same period of the year — and that produces a peak you cannot cover, which repeats itself year after year.
What an uncontrolled peak means
A company with 150 employees, three mandatory annual trainings, all historically held in February. A 2-hour session, groups of at most 15, average hourly cost 11 EUR, internal trainer.
- Sessions needed in a single month
- 150 ÷ 15 × 3 = 30 sessions
- Trainer hours
- 30 × 2 = 60 h
- Production hours taken out, concentrated in February
- 150 × 6 h = 900 h
- Cost of the hours taken out
- 900 × 11 = 9,900 EUR, in a single month
- The same hours, spread across the year
- 75 h a month instead of 900 — the same cost, without the peak
Nu intră în calcul:
- the cost of cover in production, which appears only at the peak and is what actually hurts
- extra sessions for those who miss it, more likely when everything falls in the same month
The annual cost is identical. What changes is that in the second version there is no month in which production stops. The smoothing is done once, by deliberately shifting the deadlines at the next refresher — after that it maintains itself.
What you do not do
- Do not keep the deadline register separately from the record of passes. Two sources for the same date diverge at the first catch-up.
- Do not mark somebody as trained before they pass the test, to make the report look good. The pass date is what everything downstream is calculated from.
- Do not send alerts to everybody. Whoever can do nothing with the information will ignore it, and will ignore you next time too.
- Do not recalculate deadlines retroactively when you change an interval. The new interval applies from the next pass, or correctly trained people become expired overnight.
Where to start
Check first whether your register holds the pass date or the session date. It is a one-column difference and explains most of the deadlines that look wrong.
Then count how many deadlines fall in each month of next year. If the distribution is concentrated in one or two months, deliberately shifting them at the next refresher is the cheapest possible intervention — it costs nothing and removes the peak permanently.
Only after those two is it worth adding alert thresholds. Correct alerts on wrong dates produce nothing but distrust in the system.
What about somebody returning from long leave with an expired deadline?
The deadline does not suspend itself — it is recalculated when they return, with the training done in their first days. What matters is that the absence is visible in the register, or the person appears as a straggler for no reason.
Do I have to retrain somebody who changes post?
It depends on what the new post requires, not on what they did before. Which is why training attaches to the post, not to the person — at an internal move, the difference between the two sets tells you what to do.
Deadlines calculated from each person’s pass date
The register maintains itself: every pass recalculates the deadline, and the planning list appears 45 days ahead rather than seven.
Free account, every module for 7 days, no card required.