Record Keeping, Documentation, and Compliance Auditing
Records as evidence and as control
Documentation serves three purposes: operational control (what happened, who was where), legal evidence (contemporaneous, factual, signed, unaltered), and compliance proof (licences, training, checks, drills). Know the core records: daily occurrence/incident log, guard deployment and attendance records, visitor and key registers, briefing and training records, equipment checks, incident reports, and licence/authorisation files. Good records share traits: contemporaneous, accurate, legible, attributable (signed/initialled), sequential (no gaps or overwritten pages), and retained for the required period. Auditing is the supervisor's verification tool: plan the audit, sample the records, compare practice against policy and licence conditions, record findings, correct non-conformities, and follow up.
Traps to watch
- Back-filling logs: writing entries after the fact, or rewriting a page, destroys credibility. Corrections should be a dated, signed note, never an erasure.
- Gaps in sequence: missing pages or unaccounted hours suggest concealment.
- Audit as inspection theatre: an audit that finds nothing and changes nothing is not an audit.
- Retention ignorance: records kept too briefly fail legal duties; kept indefinitely may breach data protection. Know the required period.
- Confidentiality lapses: incident reports containing personal data must be stored and shared only as authorised.
Rule of thumb
Write it when it happens, sign it, and never make it look better afterwards. An honest record with an error is stronger evidence than a perfect record written late.
Worked example
An auditor finds the visitor register missing three days and two unsigned entries. Correct handling: record the finding, identify the cause (relief guard not briefed), correct the process with a briefing and a spot-check schedule, and re-audit - rather than reconstructing the missing entries from memory.