Keeping a school site secure comes down to a question that sounds simple and rarely is: who is on the premises right now, and should they be? Between staff, pupils, parents, supply teachers, contractors, governors and visitors, a school site is busier than most workplaces, and the duty to safeguard everyone on it is higher. This guide sets out what the rules expect of schools, where the usual paper sign-in book falls short, how the DBS question actually works, and how to make sure you can account for everyone if the alarm sounds.
This article is for general information and is not legal or safeguarding advice. Schools should follow their own policies and current statutory guidance.
Schools in England work within Keeping Children Safe in Education, the Department for Education’s statutory safeguarding guidance. It does not hand you a prescribed sign-in system or a fixed list of rules for the front gate. What it does expect is that a school manages access to its site and knows who is on the premises, as part of its wider safeguarding arrangements.
In practice that comes down to three things a secure site can do: control who comes in, keep an accurate record of who is inside, and account for everyone if the site has to be evacuated. How a school meets those is for the school to decide. The point of a good system is to make all three easy to do well, and easy to show you have done.
The front-of-house process is where site security starts. Visitors should be identified, signed in, and given a clear badge, and the office should be able to see at a glance who is expected. For contractors and supply staff, this is also the point at which you confirm the right checks are in place before they go any further into the school.
Knowing who is on site is the heart of it. That means a live record of staff who are in, and of every visitor and contractor who has signed in and not yet signed out. A record that only captures arrivals, and misses departures, overstates who is present and is worse than useless in an emergency.
If the site is evacuated, someone has to stand at the assembly point and confirm that everyone who was inside is now safely out. That is only possible if the list they are working from is accurate and actually reaches them outside the building. This is where a lot of otherwise careful schools are exposed, and it is covered in more detail in our guide to where fire roll call should be carried out.
Most schools still have a book on the reception desk, and for a quiet site it can just about do the job. But it has real weaknesses once you look closely.
Each visitor can usually read the names, companies and host details of everyone who signed in before them, which discloses other people’s personal data to whoever is standing at the desk. The book is easy to misplace and impossible to search quickly. And when the alarm sounds, it is often the one thing nobody thinks to carry out of the building. A digital sign-in removes those weaknesses: it shows each visitor only their own entry, keeps a searchable record, and turns the day’s arrivals into a live list a marshal can use at the assembly point. Our guide to school visitor management systems goes into how these work in detail.
This is the point schools worry about most, and it is worth being precise, because it is often overstated.
Not every visitor to a school needs a DBS check. Whether a check is required depends on what the person is doing and how closely they are supervised, and the school makes that judgement. A parent at a school play, or a contractor accompanied at all times, is in a different position from someone working unsupervised with pupils on a regular basis. The rules around regulated activity and who needs a check are set out in the Government’s DBS eligibility guidance, and they are the kind of thing that changes, so it is right that the decision sits with the school rather than with a piece of software.
What a visitor system can do is support that process rather than replace it. At sign-in, reception can record that a visitor’s DBS check has been seen, so there is a clear log that the right check was in place for the people who needed one. The school still decides who needs checking, runs the checks, and keeps the single central record. The system keeps the evidence that it happened.
Edu Connect is our product built specifically for schools and multi-academy trusts, and it is designed around exactly these three questions. It handles staff attendance, so you have a live picture of who is in. It handles visitor sign-in digitally, with the option to record that a visitor’s DBS check has been seen. And because it already knows who is on site, it produces a live fire roll call that a marshal can carry out to the assembly point on a mobile device.
Just as important is what it does not do. Edu Connect is not a management information system and does not replace one. It does not do pupil attendance, it does not run DBS checks, and it does not hold the single central record. Those stay with your MIS and your safeguarding processes. Edu Connect works alongside them, with a live sync to Arbor so staff and site information stays consistent, and takes care of the site-security side that an MIS is not built for. For a multi-academy trust, it also means every school in the trust can run site security the same way, which matters as much as any single feature.
See how Edu Connect secures your school site