Year end is when workforce compliance records get looked at properly. Someone asks for a report, and the distance between what you believe you hold and what you can actually produce becomes visible. The checklist below is the review worth doing before that happens, written for compliance managers in construction, utilities and other regulated UK industries.
Work through it in order. Every step is about evidence you can put in front of somebody, not records you assume exist somewhere.
1. List every expiry date coming up
Start with renewals, because those are the gaps that create themselves. Cards, tickets, qualifications and certificates each expire on their own schedule, and the ones that lapse quietly are the ones nobody set a reminder for. List every expiry date across the whole workforce, sort by date, and treat the nearest renewals as work already booked rather than work to think about later.
If you cannot say with confidence what is due to expire, that is itself the finding. The point of a training record management system is that it stays on top of training expiry dates and alerts you before things lapse, rather than filing the document and leaving you to notice. Where renewal notifications are configurable, set them to the lead time your courses actually need, not the lead time the software happened to default to.
2. Check the evidence sits behind each record, not just the date
A completion date tells an auditor a course was attended. It does not tell them anything was learned, demonstrated or signed off. The records that hold up under scrutiny carry the evidence with them: assessment results, sign-offs, and the proficiency determination somebody made at the time.
Go through a sample of records for your highest-risk roles and ask whether each one would survive a question. If the answer is a certificate scan and nothing else, that is a thin record. Employee certification tracking should capture not just completion but the assessment scores, the sign-offs and the proficiency determinations behind them, so the record tells the whole story rather than the headline.
3. Separate what people have done from what they are authorised to do
These are two different questions and compliance teams get asked both. The training history answers the first. An authorisation certificate answers the second: it records what one individual was assessed as competent to do, and issues them permission for those specific activities.
That distinction matters at the individual level. Two people assessed on the same day can hold different authorisations, one cleared for high voltage work and the other for low voltage only. A year-end review that only counts completed courses will show both as trained and tell you nothing useful about what either is permitted to do. Check that your authorisations are recorded as authorisations, with the workflow behind them intact, from creation through assessment and authorisation to employee sign-off.
4. Run your roles against your requirements, not your names against your courses
Most year-end reviews start from the people and work outwards, which finds the gaps you already suspected. The more useful direction is the other way round. A competency framework defines the mandatory requirements for a job role first, then runs across the workforce to show who meets them and who does not.
Run that comparison now rather than in January. It surfaces the roles where the requirement has quietly moved on, and it separates your compliance floor from your development plan, because mandatory and preferred competencies are not the same obligation and should not sit in the same list.
5. Include contractors, subcontractors and temporary workers
The hardest part of a year-end review is rarely your own employees. It is the subcontract crew who started in September and the agency operative covering shifts. If those workers sit in a separate spreadsheet, or in no system at all, your audit report is incomplete before you start.
Check they hold full records rather than cut-down guest entries. Every worker type should carry their own profile with their full training history, qualifications and competency evidence, whatever their employment status. Anything less and the gap is in the part of the workforce you have least direct control over, which is exactly where a client will look.
6. Confirm your card checks are recorded as checks
Verifying a card and evidencing that you verified it are different acts. A manager who checked a card at the gate in March has done the right thing, but unless that check was captured, it did not happen as far as an audit is concerned.
Review how card verification is logged across your sites. Checks that are cross-referenced against industry card bodies and stored automatically as validation history give you something to show. Checks held in somebody’s memory or a site diary do not.
7. Test the report before you need it
Produce the audit report now, as a rehearsal, and read it as an auditor would. The exercise usually shows up a few things: records that exist but cannot be located quickly, records that are current but unevidenced, and workers who are in the business but not in the system.
Being able to generate a complete, audit-ready report on demand, rather than assembling one from exports, is the practical test of whether your training records are genuinely in order. If the rehearsal is painful in December, the real thing will be worse.
8. Turn the gap list into next year’s training plan
A checklist that ends in a list of gaps has done half the job. The gaps are next year’s training requirement, and the sooner they become booked places the less likely they are to still be gaps at the next review.
Put the renewals and the missing competencies straight into the schedule. Handled in one place, training course management keeps courses in an organised calendar with automated joining instructions and reminders, and a completed course updates that worker’s record automatically. That is what stops the same gap reappearing next December.
What your audit history should hold
One thing worth confirming while you are reviewing: what the system actually retains. In Competency Cloud, every certificate and training item ever uploaded against a person is held with its completion and expiry dates and a record of who uploaded it, and those records are kept indefinitely. That is the history an auditor is working from, so it is worth knowing it is there and knowing what it covers before somebody asks.
Doing it once, then keeping it true
A year-end checklist is a snapshot, and a snapshot starts going out of date the moment you take it. The reason compliance teams repeat the same scramble every December is usually that the record only gets corrected when somebody looks at it.
The alternative is a system that maintains the picture continuously: expiry dates tracked across the workforce, alerts ahead of renewals, role requirements mapped against what people actually hold, and the evidence stored where the record is. Done that way, the year-end review stops being a reconstruction and becomes a read of something that was already accurate.