Education June 2026 9 min read

How to Write a School Security Specification That Gets You What You Actually Need

Most schools go to market for a security system with a vague brief. The result is a set of quotes that are impossible to compare, a decision made on price rather than suitability, and a system that may not fit the site once it is installed. This guide is written for school business managers and site managers who want to write a specification that puts them in control of the process from the start.

Why the Brief Matters More Than the Budget

The most common mistake schools make when procuring a security system is treating the specification as an administrative formality rather than a decision-making tool. A weak brief produces a weak procurement. Suppliers fill the gaps with their own assumptions, quote different things, and the school ends up comparing a Ford with a Ferrari without realising that is what it is doing.

A strong specification does four things. It forces you to think clearly about what you actually need before you speak to anyone trying to sell you something. It puts all suppliers on the same footing so their quotes are genuinely comparable. It gives you a contractual baseline for what the finished system must deliver. And it signals to the market that you are a serious, informed buyer, which tends to bring out the best in the suppliers who respond.

None of this requires specialist technical knowledge. It requires structured thinking about your site, your people, and the outcomes you need to achieve.

Start With Your Risks, Not the Technology

A specification that opens with "we need 12 cameras and a new access control system" has already made a decision before the problem has been properly defined. Start instead with a clear statement of the risks you are trying to manage. This does two things: it anchors the whole specification in genuine need rather than assumed technology, and it gives suppliers the context to recommend a solution that actually fits.

Think through the specific security challenges your site faces. A large secondary school with multiple perimeter gates has different priorities from a primary school on a quiet residential street. A school that has suffered repeated overnight vandalism needs a different response to one that has never had a break-in but is now required to demonstrate Martyn's Law compliance.

Useful questions to ask yourself before you write a single line of specification: Where have incidents occurred in the last three years, and at what time of day? Which areas of the site are currently unsupervised? Where do staff and pupils feel least safe? What would your insurer say about your current provision? What does your DfE protective security guidance review say needs to improve?

Once you have a clear picture of your risks, the technology choices become much more straightforward. You are specifying a solution to a defined problem, not browsing a catalogue.

The Eight Sections Every School Security Specification Should Include

A well-structured specification gives suppliers everything they need to quote accurately and gives you a clear framework for evaluating what comes back. These eight sections cover the ground that matters.

Specification structure
  1. Site overview. A brief description of the school: type, age range, number of pupils and staff, number of buildings, site area, and any access or structural considerations relevant to installation. Include a site plan if one is available. Suppliers who have not yet visited the site need enough information to quote realistically.
  2. Current provision. What security systems are currently in place, how old they are, and what is wrong with them. If you are replacing an existing system, say so and explain why. If you are adding to existing provision, be specific about what must integrate with what.
  3. Objectives and outcomes. What must the finished system achieve? Be specific. "Improve security" is not an objective. "Ensure every entrance to the main building is covered by a camera with a clear view of arriving faces, with footage retained for 31 days and accessible within five minutes" is an objective. Write your outcomes in measurable terms wherever possible.
  4. Scope of works. A description of what you want the supplier to provide. This includes the systems required (CCTV, access control, intruder alarms, fire systems), the areas of the site to be covered, any specific technical requirements, and any works that are explicitly out of scope. If you want the supplier to handle cabling but not decoration, say so.
  5. Compliance requirements. The legal and regulatory standards the system must meet. This should reference Martyn's Law compliance requirements where applicable, KCSiE obligations, UK GDPR requirements for CCTV data retention and signage, and any insurance conditions. If the school is subject to specific procurement framework requirements, include those here.
  6. Integration requirements. What must the new system connect to? This includes existing systems that are staying in place, the school's IT network, any management software already in use, and any third-party monitoring arrangements. Be specific about whether integration is mandatory or desirable.
  7. Practical constraints. Installation timing (most schools need works completed during holiday periods), access restrictions, working hours on site, the need to maintain normal school operations during installation, and any listed building or planning constraints that affect what can be installed where.
  8. Contract and support requirements. What you expect after installation. This includes warranty terms, planned preventative maintenance, response times for reactive call-outs, software update policy, and training requirements for staff. A system that cannot be adequately supported is a liability, not an asset.

How to Specify CCTV Without Getting Sold Cameras You Do Not Need

CCTV is the area where schools most commonly over-specify on the wrong things and under-specify on the things that actually matter. Resolution figures and camera counts look impressive in a quote but tell you very little about whether the system will work for your site.

The questions worth specifying around are coverage, retention, and management. Coverage means every area identified in your risk assessment has a camera that can clearly see what needs to be seen. A camera pointed at a car park that captures the sky is not providing coverage. Specify the areas to be covered and the purpose of each camera, and ask suppliers to demonstrate how their proposed positions meet your stated objectives.

Retention means footage is stored for long enough to be useful. The UK GDPR guidance for most school CCTV systems suggests 31 days as standard. Shorter retention periods are sometimes proposed to reduce storage costs, but a 14-day retention period is useless if a safeguarding concern comes to light three weeks after an incident. Specify the retention period you require.

Management means the system can actually be used by the people responsible for it. Ask suppliers to demonstrate the management interface and to confirm how quickly a specific piece of footage can be located and exported. A system that requires 45 minutes and a specialist engineer to retrieve a clip is not fit for purpose in a school context.

One thing most schools forget to specify: what happens when the system fails. Ask every supplier how the system behaves during a network outage, a power failure, or a hardware fault. Does it fail safely? Does it alert someone? How quickly can it be restored? A system with no answer to these questions is a system that will let you down at the worst possible moment.

How to Specify Access Control Without Creating New Problems

Access control specifications fail most often in two areas: they do not think through the day-to-day user experience, and they do not address what happens when the system needs to change.

The user experience point is practical. A system that requires staff to fumble with a key fob, enter a PIN, and wait three seconds for a door to release will be propped open within a week. Specify that the system must be fast and intuitive to use in normal daily operation, and ask suppliers to demonstrate this with real hardware rather than a brochure.

The change management point is often overlooked entirely. Schools are dynamic environments. Staff join and leave constantly. Contractors come and go. Permissions need to change. A system that requires an engineer visit every time a user is added or a permission is modified is going to be expensive and badly managed. Specify that the management software must allow authorised staff to add users, change permissions, and deactivate credentials without external support.

Also specify the integration between access control and your other systems. A door that is forced open should trigger an alert and, if CCTV is present, direct the nearest camera to the event. This is standard capability in a properly integrated system, but it needs to be in the specification to be certain it is delivered. For more on what a complete access control system includes, see the access control buying guide.

The Questions That Separate Good Suppliers From the Rest

Alongside the technical specification, include a set of questions that all suppliers must answer in writing. The answers reveal capability, experience, and honesty more reliably than anything else in the procurement process.

Questions to include in your specification
How many schools have you installed systems for in the last two years, and can you provide references from at least two whose sites are similar to ours?
Who will carry out the installation on site, and are they directly employed by your company or subcontracted? What accreditations do they hold?
How will you manage installation to minimise disruption to normal school operations, and what is your plan if works overrun the agreed holiday window?
What happens to our system when the manufacturer ends support for the hardware or software? What is your upgrade pathway and what will it cost?
What is your guaranteed response time for a critical fault, defined as a system failure that leaves a significant area of the site without cover? What are the financial remedies if you miss that commitment?
How does your system support our UK GDPR obligations, specifically data retention periods, subject access requests, and secure deletion?
Walk us through a scenario where our system needs to support a safeguarding investigation. How would footage be retrieved, who can access it, and how is the chain of evidence maintained?

A supplier who answers these questions thoroughly, specifically, and without evasion is a supplier worth taking seriously. A supplier who responds with generalities, redirects to their brochure, or fails to answer the safeguarding question at all has told you something useful.

How to Structure the Pricing to Get Comparable Quotes

The single most common reason schools cannot compare security quotes is that they ask for a single price and receive back proposals that bundle different things in different ways. One supplier includes three years of maintenance. Another does not. One includes staff training. Another charges for it separately. The lowest headline number is not the most cost-effective solution.

Require suppliers to break their pricing into clearly defined categories and to price each one separately. At a minimum this should include: hardware supply, installation labour, cabling and infrastructure, management software licence, first-year maintenance and support, and any ongoing annual costs. This structure makes it straightforward to compare like with like and to identify where the real cost differences lie.

Also require suppliers to confirm the total cost of ownership over a five-year period. This forces them to be explicit about what ongoing costs look like and makes it much harder to win on a low upfront price that conceals expensive annual fees.

A note on value for money: The DfE guidance on procurement requires schools to demonstrate value for money, not simply lowest cost. A well-written specification that produces structured, comparable quotes is your evidence that you ran a proper process. It also gives your governing body something concrete to review, rather than asking them to compare numbers that mean different things.

What to Do When the Quotes Come Back

Even with a strong specification, you will receive proposals that do not fully address what you asked for. This is normal. The question is whether the gap reflects a deliberate alternative approach the supplier can justify, or a failure to engage with the brief.

Score each response against your specification using a simple framework: does it cover the scope, does it meet the compliance requirements, does it answer the questions, and does it give you the pricing structure you asked for? A proposal that fails on any of these is not ready for evaluation and should be sent back with a request to address the gaps before it is considered further.

For the proposals that do meet the brief, invite the shortlisted suppliers to present in person and to bring equipment for demonstration. The management software particularly benefits from hands-on evaluation. A system that looks elegant in a brochure can be frustrating in daily use. A system that looks unremarkable can be fast, intuitive, and well-supported.

Take references. Call them rather than emailing. Ask specifically whether the supplier delivered on time, whether the system works as specified, and whether they would use the same company again. The answers to those three questions tell you most of what you need to know.

A Brief Note on Timing

School security procurement takes longer than most business managers expect when they start the process. A thorough specification, a proper tender period, evaluation, reference checking, contract negotiation, and scheduling of installation within a holiday window can take four to six months from start to finish, even when everything goes smoothly.

If your driver is Martyn's Law compliance ahead of the April 2027 enforcement deadline, the time to start the specification process is now. Leaving it until the second half of 2026 risks running out of holiday windows for installation before the deadline arrives.

If your driver is a system that has failed or is approaching end of life, the same logic applies. A temporary failure in an ageing system has a way of becoming a permanent failure at exactly the wrong moment. Starting the procurement process before the crisis rather than during it gives you leverage, time to run a proper process, and a much better chance of getting the right system at the right price.

Want help putting your specification together?

We offer free site surveys for schools across the South East. We will assess your current provision, talk through your requirements, and give you a clear, honest picture of what your specification should include. No obligation, no pressure, and nothing to sell you until you are ready.

Request a Free Survey →
Accreditations
NSI NACOSS Gold
SSAIB Approved
BAFE Registered
Constructionline
ISO 9001:2015
Crown Commercial Service