Training records that survive an audit

Training records are usually kept — as certificates, in a folder, filed by date. That format answers "did this person attend a course?" It does not answer the question an assessor or a client actually asks, which is whether the officer on that post is trained for that post.

Two different questions

The distinction matters because the two questions need different structures. A certificate archive is organised around events. Operational competence is organised around people and posts.

• –Event view — who attended what, and when
• –Person view — what this officer holds, and what has expired
• –Post view — what this site requires, and who meets it

Most contractors have the first. The third is what makes rostering safe, and it is the one that almost never exists as a view.

Refreshers are dates, and dates need prompts

Anything with a refresher interval has the same failure mode as licence expiry: a date sitting in a document with nothing attached that raises its hand. Related: tracking licence expiry without a spreadsheet.

Site-specific induction

Client contracts frequently require site-specific induction on top of general training, and this is the element most often skipped for short-notice cover. If induction status is not visible at the point of assignment, it will not be checked at 5am.

Attendance is the easy part to evidence

Training records overwhelmingly prove attendance: a name, a date, a course title, sometimes a signature. What a client or assessor is more often interested in is whether the training was relevant to the post the officer actually works, and whether anything since has confirmed it stuck.

An officer trained on a generic induction two years ago and posted to a site with specific requirements — a particular alarm system, a specific evacuation role, a client's own procedures — has a training record that is complete and not obviously relevant to what they do.

Site-specific training is the usual gap

The recurring finding is that generic training is well recorded and site-specific training is not recorded at all, because it happened informally: a handover from the outgoing officer, a walk round with a supervisor, a briefing at the start of a shift. All genuinely useful, none documented, and therefore invisible when a client asks what training their site's officers have had.

Common mistakes

• –Recording attendance without recording what the training covered
• –Site-specific briefings delivered informally and never documented
• –No link between an officer's training and the posts they actually work
• –Records held per course rather than per officer
• –No refresher tracking, so training ages invisibly
• –Certificates held by officers rather than by the business

What separates a record that holds up

A record that survives scrutiny ties three things together: the individual, the specific content covered, and the post or site it was relevant to. Most records hold the first and part of the second. The third is what lets a contractor answer the question a client actually asks, which is not whether officers are trained but whether the officers on their site are trained for their site.

Building that link at the point training is delivered costs almost nothing. Reconstructing it afterwards, across a workforce with turnover, is the kind of exercise that consumes weeks and produces something nobody quite trusts.

One more thing: sample your own files first

The cheapest way to find out that practice has drifted is to read your own records the way an assessor would, before a client does it for you. Pick three officers at random, on three different contracts, and try to answer what training each has had for the site they actually work.

• –Sample a few files periodically rather than waiting for an audit
• –Pick officers across different contracts and branches, not the easiest ones
• –Treat anything you cannot answer quickly as the finding

One practical test: pick a site and ask what its officers were trained on

Choose one client site and try to answer what training the officers working it have had that is specific to that site — the access arrangements, the client's procedures, the things that caught somebody out before.

Generic training is well recorded almost everywhere. Site-specific briefing is the highest-value training a security contractor delivers and is usually delivered verbally at a handover, which makes it invisible to exactly the client most likely to ask about it.

• –Record site briefings, not only formal courses
• –Link training to the posts an officer actually works
• –Organise records by officer rather than by course
• –Track refreshers so training does not age unnoticed
• –Sample your own files before a client audits them