What you receive
Deliverables
- Security plans, manuals, post orders, SOPs and workflows
- Governance structure and accountability frameworks
- A named owner for every section, not just a department
- A built-in review schedule so documents stay current
- Training and rollout support
Is this right for you?
- Organisations with outdated, generic or unused security documentation
- Teams that need post orders and SOPs their officers will actually follow
- Organisations preparing for leadership change, staff turnover or an audit
- Guard providers and in-house teams that need a common operating standard
How it works
Our approach
1
Understand the operation
We learn how your team actually works — routines, roles and constraints — before writing anything.
2
Write to be used
We draft concise documents scoped to what your team can realistically sustain, with clear ownership.
3
Roll out and review
We support training and rollout, and set a review cadence — annually at minimum, or after any material change.
Common questions
Frequently asked questions
Can you update our existing plan rather than start again?
Yes. Many engagements start with a review of what you have, keeping what works and rewriting what does not.
Why are your plans shorter than others we have seen?
Deliberately. Shorter plans get read, and read plans get followed. Detail goes where it is needed, not everywhere.
How often should a security plan be reviewed?
At least once a year, and after any material change to the site, staffing or operation.
Where this applies