Skip to main content
Martyn's Law guidance updated in April 2026 — is your organisation prepared?Check your obligations →
Multi-Site Planning4 June 20266 min read

Lockdown Alarms for Multi-Academy Trusts: Rolling Out Across Sites

Running the same procedure across several schools is harder than running it well at one. Here is how trusts across Greater Manchester and elsewhere handle the tension between consistency and site reality.

Article Overview

Practical guidance for real-world site decisions.

Running the same procedure across several schools is harder than running it well at one. Here is how trusts across Greater Manchester and elsewhere handle the tension between consistency and site reality.

At a Glance

  • Standardise the signal and the expectation, then allow site-specific design underneath.
  • Central monitoring is what makes a multi-site estate maintainable.
  • Phasing by site lets coverage follow the budget rather than waiting for all of it.
  • Staff move between sites, which is exactly why consistency matters.

Section 01

The problem is people moving between sites

In a trust, staff move. Cover teachers, central team members, site staff and leadership all work across more than one building. If the alert means one thing at one school and something else at another, that mobility becomes a hazard.

The fix is not complicated but it has to be deliberate. Agree that the same signal means the same thing everywhere, and that the expectation of staff is the same everywhere, before individual sites start specifying equipment.

Section 02

Standardise the signal, vary the design

Sites genuinely differ. A Victorian primary with thick walls, a 1970s secondary with long corridors and a recent build with open-plan spaces need different device counts and placements to achieve the same outcome.

  • Same tone and same visual indicator at every site
  • Same first action expected of staff everywhere
  • Same all-clear process and the same role authorised to give it
  • Device count and placement determined per site by survey

Section 03

Monitoring is what makes it maintainable

One building can be checked by walking around it. Six cannot, at least not reliably or repeatedly. Without central visibility, maintenance across an estate becomes a matter of hoping each site remembers.

A monitoring bridge that reports device status and battery health centrally turns that into an exception list. The central team sees what needs attention rather than chasing confirmation that nothing does.

Section 04

Phasing beats waiting

Few trusts can fund every site at once. The practical route is to sequence, usually starting with the sites that have the weakest current coverage or the highest assessed risk rather than the ones that are easiest.

Wireless systems suit this well, because a later phase adds to what is already there rather than repeating a building project. It also lets you apply what you learned at the first site to the next.

Section 05

Primary and secondary sites need different thinking

The same procedure rarely transfers cleanly between a primary and a secondary school, even within the same trust. The difference is not the building so much as the independence of the people in it.

In a primary, almost every pupil is with a member of staff at almost every moment, and the response is essentially a staff instruction carried out on behalf of a class. Younger children also react more strongly to alarm tones, which is an argument for spoken messages and for careful framing during drills.

In a secondary, pupils move independently, may be off timetable, and are spread across a larger site. The procedure has to account for pupils who hear the alert while nowhere near their usual room, which means telling them what to do rather than relying on a teacher being present.

Section 06

Coordinating with existing systems

Most schools already have several systems that touch on safety, and a lockdown alert needs to sit alongside them without creating confusion. The fire alarm is the critical one, and the distinction between the two signals should be identical across every site in the trust.

Access control, if you have it, is worth considering at the same time. Being able to secure entrances quickly complements an alert that tells people a lockdown is underway, and the two decisions are easier to make together than separately.

  • Fire alarm: signals must be unmistakably different at every site
  • Access control: consider how entrances are secured during an alert
  • Reception and visitor management: who is responsible during an incident
  • Site communications: how the central team is informed

Section 07

Building the business case for the board

A trust-wide rollout is a governance decision as much as an operational one, and the paperwork tends to be what slows it down. It helps to present the whole programme with phases marked, rather than a series of separate site requests.

Boards generally want to see the same things: what the current gaps are, what the standard will be, what it costs in total, and how it splits across financial years. Framing it as a single programme delivered in phases is usually more persuasive than an annual repeat of the same conversation.

  • Current position at each site, including known coverage gaps
  • The trust-wide standard being adopted and why
  • Total programme cost with a per-site and per-phase breakdown
  • Which sites are prioritised and on what basis
  • Ongoing costs and who owns the system day to day

Section 08

Learning from the first site

One genuine advantage of phasing is that the first installation teaches you things that improve every subsequent one. That only happens if someone is paying attention and the findings are captured centrally.

The most useful lessons are usually procedural rather than technical: which parts of the handover staff found confusing, what the first drill exposed, and which questions parents or governors asked. Those answers make the second site considerably smoother.

It is worth having the central team present at the first site’s handover and first drill for exactly this reason. The travel cost is small against the benefit of not repeating the same avoidable friction at every school in turn.

Section 09

Who owns it once the rollout finishes

Programmes have owners. Systems in daily use often do not, and this is where multi-site rollouts most commonly lose momentum. Once the central project closes, responsibility needs to land somewhere specific at both trust and site level.

A workable split is that each site owns day-to-day operation, briefing new staff and running drills, while the central team owns the standard, the monitoring overview and the review cycle. Written down, that takes a paragraph. Left implicit, it tends to mean nobody does it.

The practical test is simple: if a device reports a fault next term, who receives that message and who acts on it? If the answer is not immediately obvious, the handover is not finished.

Section 010

Keeping consistency as the trust changes

Trusts grow. Schools join, buildings are added, and sites occasionally leave. Each of those events is a moment where a carefully built standard can quietly fragment if nobody is watching for it.

A joining school will usually arrive with its own arrangements, or none. Bringing it onto the trust standard is easier if the standard is a short written document rather than institutional knowledge held by whoever ran the original programme.

  • Add lockdown arrangements to the due diligence list for joining schools
  • Review the trust standard annually rather than only when something changes
  • Keep a central register of what is installed where, and when it was last tested
  • Include new buildings and extensions in the standard from the design stage

Section 011

Procurement across a trust

Trust-wide purchases usually attract more procurement scrutiny than single-site ones, and the thresholds that trigger formal processes vary by trust and by funding source. It is worth establishing early which route applies, because it affects the timeline more than anything technical.

A programme covering several schools may exceed a threshold that any individual site would not, which occasionally surprises people who have bought for one school before. Splitting a programme to stay below a threshold is not a legitimate approach, so it is better to plan for the process than to design around it.

Where frameworks are available they can simplify this considerably, and many trusts already use them for other estates and safety work. Whether one covers this category is worth checking with your finance or procurement lead before going to market.

The practical advice is to involve procurement at the point you commission surveys, not at the point you want to order. A specification produced with the eventual process in mind is far easier to take forward than one that has to be reworked to fit it.

  • Establish which procurement route applies before surveying
  • Check whether an existing framework covers this category
  • Plan the governance and procurement timeline alongside the calendar
  • Keep the specification supplier-neutral enough to compare quotes
  • Involve procurement early rather than at order stage

Frequently Asked

Questions we get asked about this

Can one system cover multiple sites?

Each site normally has its own system, since you would not want an alert at one school sounding at another. What is shared is the standard, the signal, and typically central monitoring that reports on all sites in one place.

Do we have to do all our schools at once?

No, and most trusts do not. Phasing by site is normal and lets the rollout follow budget cycles. Wireless systems make later phases straightforward because they add to what is already installed.

Can we get a trust-wide price?

We survey each site because device counts genuinely differ, but we quote as a programme so you can see the total and the per-site breakdown. That is usually what a board needs to approve a phased plan.

How do we keep procedures consistent across schools?

Write one trust-level procedure covering the signal, the first action and the all-clear, with a short site annex for local detail. That gives consistency where it matters without forcing very different sites into one layout.

Who manages the system day to day?

Usually the site team locally, with central oversight through monitoring. The monitoring layer is what lets a central estates or compliance lead see the position across every school without visiting.

Need help applying this to your site?

We can turn the principles in this article into a practical recommendation based on your building, procedures, and response priorities.

Want advice specific to your building and team?

We can help you move from general guidance to a clear, site-specific recommendation.

✓ No obligation✓ Free site survey✓ UK-based support