A stolen tool, an unauthorised entry or a CCTV blind spot can look like an isolated issue at first. It rarely is. Knowing how to audit security incidents gives site and facilities managers a disciplined way to establish what happened, protect evidence, identify control failures and make sure corrective action is actually completed.
An incident audit is not about finding someone to blame. It is a fact-led review of the event, the response and the security arrangements in place at the time. Done properly, it creates an auditable record for senior management, insurers, clients and, where required, the police or regulators.
Start by separating the incident from the audit
The immediate incident response comes first. Make the area safe, contact emergency services where there is a threat to life or serious crime, preserve the scene and notify the appropriate site contacts. Do not delay urgent action while waiting to begin an audit.
The audit begins once the immediate risk is controlled. Its purpose is wider than the initial report. It tests whether the site’s security plan, access controls, patrol arrangements, CCTV coverage, contractor management and escalation process operated as intended.
This distinction matters. A concise incident report may confirm that a gate was left unsecured at 22:15. An audit should establish why it was unsecured, how long it remained exposed, whether patrols should have identified the issue, what footage and records support the timeline, and what must change to prevent a recurrence.
Define the audit scope before reviewing evidence
Every audit needs a clear scope. Without one, reviews can become unfocused, particularly on complex construction sites, multi-occupancy properties or estates with several suppliers.
Set out the incident type, location, relevant time period, assets or people affected, and the controls being assessed. For example, following a theft from a construction compound, the scope may cover perimeter security, gatehouse procedures, guard patrol records, alarm activations, CCTV footage, key control and delivery access over the 24 hours before discovery.
Decide early who owns the audit. This should usually be a competent manager with sufficient independence from the daily activity being reviewed. They need access to records and authority to assign actions. If a guarding provider, monitoring centre, traffic management team or subcontractor is involved, make their responsibilities and response deadlines explicit.
Not every event needs the same depth of review. A minor trespass with no loss may require a proportionate local review. Repeated unauthorised access, violence, significant theft, safeguarding concerns, data loss or an incident with contractual implications warrants a more formal audit and senior oversight.
Preserve evidence and build a reliable timeline
Evidence deteriorates quickly. CCTV may be overwritten, staff memories can diverge, and physical conditions on site may change during normal operations. Secure relevant material as soon as possible and record who collected it, when and where it has been stored.
Useful evidence will vary by site, but commonly includes:
- CCTV footage, remote monitoring clips, alarm logs and system health records
- Guard occurrence books, digital patrol records, body-worn video where used, and supervisor reports
- Access-control logs, visitor registers, delivery records, key registers and permit documentation
- Photographs, site plans, damage reports, witness accounts and police crime references
- Rosters, training records, risk assessments, assignment instructions and supplier communications
Create a timed sequence of events rather than relying on one account. Start with the last confirmed secure point, then map each known action, alarm, patrol, access event and report through to the point at which the incident was contained. Mark assumptions clearly. A gap in evidence is itself a finding, not something to be filled with guesswork.
CCTV and personal data require careful handling. Footage should be accessed only by authorised personnel, retained in line with the organisation’s policy and relevant data protection obligations, and shared only where there is a lawful and justified reason. Good evidence management protects both the investigation and the organisation.
Test what was meant to happen against what happened
The most valuable part of an audit is the comparison between documented controls and real site practice. Review the security risk assessment, assignment instructions and site rules first. Then test whether the arrangements were suitable, communicated and followed.
For perimeter breaches, check the condition of fencing, gates, hoarding, lighting and warning signage. Establish whether access points were locked, monitored or left dependent on staff judgement. On vacant properties, examine inspection frequency, alarm coverage, boarding condition and the response process for signs of entry.
For incidents involving people, assess the visitor and contractor process. Were identities checked? Were visitors escorted where required? Did the gatehouse have an up-to-date list of expected deliveries and authorised personnel? In education settings, safeguarding procedures and the management of access during arrival, collection and events may be central to the audit.
Where guarding is part of the control package, verify that officers were correctly deployed, fully briefed and working to current instructions. Review patrol routes and timings, but do not treat a completed patrol record as proof that a patrol was effective. Compare it with CCTV, access events and site conditions. A patrol route that does not cover a recurring blind spot is a design failure, even if every checkpoint has been scanned.
Technology also needs to be audited as an operational control, not just an installed asset. Was the CCTV camera recording at the correct angle and resolution? Was the wireless system online? Did remote monitoring receive the alarm? Was the response agreed in advance, and was it delivered within the expected timeframe? Equipment that is present but poorly configured provides false reassurance.
Identify root causes, not just immediate failures
Most incidents have more than one contributing factor. A gate may have been left open, but the underlying cause could be unclear handover arrangements, a damaged lock, pressure to keep deliveries moving, inadequate lighting or a lack of supervisory checks.
Use repeated questioning to move beyond the first visible failure. Ask what control should have stopped or detected the event, why that control did not work, and whether the weakness exists elsewhere on the estate. Avoid broad conclusions such as “human error” unless the audit explains the conditions that made the error likely.
This is also where supplier performance should be assessed fairly. If an officer missed an escalation, establish whether the instructions were clear, the communications equipment worked, staffing levels were adequate and the escalation route was realistic. Accountability should be evidence-based and shared appropriately across the client, managing agent, principal contractor and service providers.
Turn findings into actions that can be verified
An audit only improves security when its findings become controlled actions. Each action should state the required outcome, owner, deadline, priority and method of verification. “Improve site security” is not an action. “Install a lockable pedestrian gate, update the delivery process and confirm closure through a supervisor inspection for four weeks” is measurable.
Prioritise actions according to risk. Immediate measures may include securing a breach, increasing patrols, changing access codes or deploying temporary monitored CCTV. Medium-term actions could involve revising assignment instructions, retraining staff, improving lighting or adjusting camera coverage. Longer-term measures may include redesigning access routes, replacing weak perimeter infrastructure or consolidating fragmented site services under one accountable management process.
Cost and operational impact should be considered openly. Restricting access may reduce trespass but slow deliveries. More frequent patrols may improve visible deterrence but cannot replace a physical barrier at a known breach point. The right measure depends on the site’s risk profile, operating hours, public interface and the value or sensitivity of what is being protected.
Report clearly and follow through
A useful audit report should allow a decision-maker who was not present to understand the event quickly. State the facts, timeline, evidence reviewed, control failures, root causes, actions, owners and residual risks. Separate confirmed findings from matters that remain unproven.
Keep the report factual and professional. Avoid speculation, emotive language and unsupported criticism. Where a criminal investigation is live, ensure the report does not compromise police enquiries or disclose sensitive information unnecessarily.
Close the audit only after action is verified. That may involve a site inspection, a test activation, a review of new patrol data, a revised risk assessment or confirmation that staff have received and understood updated instructions. For recurring issues, track trends across sites and months. A single attempted intrusion may be opportunistic; repeated activity may indicate a targeted vulnerability requiring a different level of control.
A well-run incident audit does more than document a problem. It gives managers confidence that security arrangements are being tested against real conditions, not simply accepted because they are written down. Treat each incident as evidence about the site, act on it promptly, and the next audit should show a stronger operation rather than the same failure in a different form.