In brief: an Operational Requirement sets out what your security system must achieve before anyone chooses equipment. Every item in the final quote then traces back to a reason you gave.
Quotes built the wrong way round
Many CCTV quotes start with a camera count. Someone decides how many cameras the building seems to need, prices them and calls it a proposal. An Operational Requirement reverses that order. First it defines what you’re trying to achieve. Then it works out what that means at each part of the site. Only then does it decide which equipment delivers it. This approach is set out in UK government security guidance from the National Protective Security Authority.
If you get it wrong, you pay twice: once for the original system, and again to fix the gaps.
Two stages
- A requirements conversation. What’s the problem, why does it matter, and who’s affected?
- A site survey. Those objectives become specific camera positions, coverage and technical detail.
Done in that order, every item on the quote can be traced back to a reason someone gave.
Risk first, equipment second
The most useful early question isn’t “how many cameras?” It’s “what has happened here before, and what would it cost if it happened again?” Ranking risks by likelihood and impact keeps the design focused on what matters.
A system for your site, not a generic one
An Operational Requirement adds one conversation to the process. It’s the difference between a system designed for your site and one designed for a generic version of it.
Electronic security for over a decade, after an early career in IT networks.