What site-specific SOPs should cover
Good SOPs usually define responsibilities, escalation, communications, control points and reporting expectations clearly enough that the site can act consistently when pressure rises.
Lockdown, invacuation and evacuation
These should be treated as practical operational procedures, not just documents. What matters is whether people know the triggers, routes, controls, decision points and communications expected of them.
Escalation and command structure
Ownership matters. Current contacts, decision authority and reporting lines help turn procedures into something usable rather than something left to assumption.
Drills, walkthroughs and review
Procedures stay usable when they are revisited, walked through and updated. Sites do not need drama to justify this; they need realism and operational discipline.
Common weaknesses
- Outdated documents.
- Unclear triggers or vague terminology.
- Ownership that is assumed rather than defined.
- No real review cycle.
Practical review checklist
- Are responsibilities clear by role, not just by document title?
- Are escalation routes current and owned?
- Are communication steps usable in practice?
- Have procedures been reviewed against the actual site layout and access patterns?
Lockdown restricts movement into and within a building to contain a threat. Invacuation moves people from outside areas into the building for safety. Both need clear triggers, ownership and rehearsed procedures.
How often should lockdown procedures be tested? Procedures should be tested regularly — at least annually and after any significant building, staffing or operational change. Tabletop exercises and walkthroughs are useful between full tests.
Who should own escalation decisions during an incident? Escalation ownership should be clearly assigned in advance, not left to individual judgement in the moment. It typically sits with a named role — such as duty manager, site controller or senior security officer.