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.
Key takeaways
- A certificate archive answers a different question from operational competence
- Build a per-post view: what this site requires, and who meets it
- Refresher dates need a prompt attached, like any other expiry
- Site induction is the element most often skipped on short-notice cover
The SecureOptix team
Written by people who work daily with security contractors on SIA licensing, screening and the records that hold up under an inspection.