An organisation invests in new security procedures: access control, visitor management, incident reporting, cash handling. The documents are approved and circulated. Six months later, little has changed. Staff are still doing things the old way, and the new procedures sit in a shared folder.
The problem is rarely the content. It is the rollout.
Explain the why
People follow procedures they understand. Before a new SOP goes live, explain what problem it solves and why the old way is no longer acceptable. A short briefing from a manager carries more weight than an email attachment.
Train for the job, not the document
Walk people through the procedure where they will use it — at the gate, the front desk, the cash office. Practise the parts that happen rarely, like an alarm or an incident, so people are not learning them for the first time when it matters.
Get sign-off
Ask each person to confirm they have received, read and understood the procedure. It creates accountability and gives you a record of who has been trained.
Check early and often
The first 90 days decide whether a procedure sticks. Spot-check frequently in the first weeks, correct mistakes on the spot, and collect feedback. If something does not work in practice, fix the procedure rather than tolerating the workaround.
Keep it alive
Assign an owner to every SOP, schedule a review at least annually, and update it after any incident or significant change. Train new staff as part of induction.
What this means in practice
- Brief teams in person on why the new procedure matters.
- Train on site, and practise the rare scenarios.
- Record sign-off from everyone affected.
- Spot-check weekly for the first three months.
- Name an owner and set a review date.
Talk to us about procedure rollout and training support. → Security plans & manuals
