Some training is optional. Some training is the law, or the insurer's condition, or the auditor's first question. Anti-money-laundering refreshers every year. Equipment operator re-evaluations every few years. Food-safety certificates that lapse on a fixed date. Safeguarding, fire wardens, first aid, data protection.
The training itself is rarely the hard part. The hard part arrives months later, when someone outside the company asks a simple question: show me who was trained, on what, when, and when they're due again.
We keep hearing versions of the same situation across the communities we follow. An HR lead at a small manufacturer that has just been acquired, inheriting a team of equipment operators and no clear record of who had their last refresher. A compliance trainer reminding firms that the regulator won't ask whether you trained people, it will ask to see the records. An operations lead trying to track food-safety training for around a hundred staff, with certificate renewal alerts so nobody quietly expires. Small businesses asking for something affordable with "reporting" in it, without being sure what reporting they actually need.
Different industries, same shape of problem. Here are six assumptions that come up again and again, and what tends to happen in practice.
Myth 1: "We trained everyone, so we're covered"
Reality: if you can't show it, it didn't happen, at least not in the eyes of whoever is asking. A sign-in sheet in a drawer, a group email saying "please watch this video" and a manager's memory are not records. The question is never "did training happen?" It's "for this named person, on this date, which version of the material, and did they pass?"
The fix is boring and effective: decide what one training record must contain before you run the next session. Person, course or topic, version, date completed, result, who delivered or signed it off, and the date it expires.
Myth 2: "Completion is the same as compliance"
Reality: many requirements care about more than a ticked box. Some need a passed assessment. Some need a practical evaluation by a qualified person, especially for equipment and safety work. Some need a signed acknowledgement of a policy.
Video watched to the end is the weakest of these. If your requirement includes "demonstrated competence", the record needs to show who observed it and what they checked. That part often lives on paper on the shop floor, and it needs a place to land next to the online part, or the record is only half there.
Myth 3: "We'll remember when renewals are due"
Reality: nobody remembers. People change roles, managers leave, and the person who set up the spreadsheet moves on. Expiry is the part that breaks first, because nothing happens on the day a certificate lapses. Nobody notices until an incident or an audit.
Whatever you use, renewals need to be driven by dates, not memory. Each certificate gets an expiry date when it's issued, reminders go out ahead of time to the person and their manager, and someone can pull a list of "expired or expiring soon" in one step.
Myth 4: "New hires can catch up later"
Reality: the gap between someone starting and being trained is exactly where the risk sits. That's especially true after an acquisition or a busy hiring season, when a whole group arrives with unknown history.
A simple rule helps: role determines required training, and starting in the role starts the clock. If someone joins as an equipment operator, the required items for that role are assigned on day one with a due date, and anything they bring from a previous employer is checked and recorded, not assumed.
Myth 5: "We need an expensive platform to do this properly"
Reality: it depends on headcount and how many different requirements you track. We've seen three workable setups, and each has a ceiling.
- A well-kept spreadsheet plus a shared folder of certificates. Fine for a handful of people and one or two requirements. It breaks when nobody owns it or when you need reminders.
- A learning platform with certificates, expiry dates and reports. Sensible once you have dozens of people, several roles and recurring refreshers. Check that it can issue dated certificates, set expiry, send reminders and export records in a format someone else can read.
- An HR system with a training module. Good when you already use one and the requirements are simple. Often weaker on assessments and on the actual course content.
Whichever you pick, the test is the same: can you hand an outsider a clean report for one person and for one requirement, quickly, without rebuilding it by hand?
Myth 6: "Once it's set up, it runs itself"
Reality: the material changes. Rules get updated, procedures change, a new machine arrives. If the course content isn't versioned, you can't show which version someone was trained on, and you may be certifying people on an outdated procedure.
Give every required course an owner and a review date. When the content changes, record the new version, decide whether existing certificates still stand or need a refresher, and keep the old version's record intact.
A simple order of work
If you're starting from scratch, or from an inherited mess, this sequence keeps it manageable:
- List the requirements. Which training is legally or contractually required, for which roles, and how often it renews.
- Map people to roles. Every person gets the required items for their role, with due dates.
- Collect what already exists. Old certificates, sign-in sheets, previous employer records. Record what you can verify and flag what you can't.
- Define the record. Person, item, version, date, result, sign-off, expiry. Same fields every time.
- Set reminders. Ahead of expiry, to the person and their manager, with an escalation if it's missed.
- Run a mock request. Pretend an auditor has asked for one person's history and one requirement across the whole team. Time how long it takes. Fix whatever slowed you down.
That last step is the one most teams skip, and it's the one that shows whether the system works.
What still deserves judgement
Records prove that training happened. They don't prove it worked. A short scenario check, a supervisor's observation or a follow-up a few weeks later tells you much more about whether people will do the right thing under pressure. Treat the record as the floor, not the goal.
And be honest about what isn't training at all. If people keep getting a procedure wrong, sometimes the fix is a clearer checklist on the wall or a better process, not another module.
Your turn
- If you've been asked to show training records, what did the person asking actually want to see, and what was missing?
- How do you handle the practical, observed part of a certification alongside the online part?
- Spreadsheet, learning platform or HR system: where did your setup start to break, and at what headcount?
- When a procedure changes, do you re-certify everyone, or only the people it affects?
Top comments (0)