Profile the threat realistically
Opportunist break-in, organised crime targeting plant or metal, hostile reconnaissance, vandalism and trespass each demand different detection layers. Don't scope to the average — scope to the specific.
Map the physical envelope
Is the asset inside a building, in a yard, or the site itself? Each implies a different primary detection layer.
Decide the response model
Keyholder, guard, monitored unverified alarm, video-verified police response — each has different cost, latency and effectiveness.
Match the system to operational reality
Who arms it? When? Who manages keyholders? Who responds at 2am on a Sunday? Systems fail at the human seams.
Cost the system over a decade
Capital plus monitoring plus maintenance plus expected replacement. The cheapest install is often the most expensive system over ten years.
In summary
- Match technology to threat profile, not to a generic security checklist.
- Primary detection layer follows the physical envelope.
- Response model is half the system — scope it explicitly.
- Compare TCO over a decade, not capital cost.
Frequently asked questions
Should I use one supplier for everything?
Single-supplier deployments are simpler operationally but can lock you in. Component standards-based design preserves flexibility.
Should I involve my insurer before scoping?
Yes — always. The insurer sets the minimum grade, signalling and monitoring requirements, and specifying a system without their input often means costly rework. A brief conversation before scoping avoids designing to the wrong standard, and many insurers will discount premiums modestly for systems that materially exceed their baseline requirements on a commercial site.
What questions should I ask a prospective installer?
Ask for evidence of recent installations on similar sites, current NSI or SSAIB certification in the UK or UL and state licensing in the US, and named references with permission to contact them directly. Also ask who provides monitoring and maintenance, and whether either is subcontracted to a third party under a different service standard.
How do I compare quotes that look very different on price?
Rebase both quotes onto the same technical specification: grade, sensor count and type, signalling path, monitoring model, response pathway and lifecycle inclusions. Big price differences almost always come from different assumptions on one of these axes rather than genuinely better commercial terms. Comparable quotes are the only fair basis for a purchase decision.
How long should a specification take to write?
A credible commercial specification takes three to eight days of specialist time — site survey, threat assessment, insurer alignment, technology selection and lifecycle costing. Rushed specifications produce systems that are misaligned with site risk and expensive to modify later. Time invested at the specification stage is consistently the highest-return spend on any commercial security project.
Do I need an independent security consultant?
On projects above around fifty thousand pounds capital, or on sites with unusual risk profile, an independent consultant usually pays for their fee several times over through better specification, competitive tendering and avoided rework. Below that threshold, working directly with two or three reputable installers on a common brief often gives comparable value.
How often should the specification be reviewed after install?
Review the specification annually against changes in site operations, insurance requirements and threat profile, with a deeper review every three years covering technology refresh options. Systems drift out of alignment with operational reality faster than most operators expect, and the annual review is the mechanism that catches drift before it becomes a security failure.
Talk through this with a specialist for your site
Tell us about your site and we'll connect you with a commercial security specialist who understands your detection, monitoring and response requirements.