Skip to content
LobbyExpress
Search

Guide

Running an evacuation roll-call from visitor data

How to turn sign-in records into a roll-call that works when the alarm sounds: who holds the list, how wardens reconcile it at the assembly point, what to do when the network or the tablet is unavailable, and how to drill it.

By LobbyExpress Editorial

The fire alarm is the moment a visitor management system earns its keep. Every other day it prints badges and texts hosts; on the day of an evacuation it is meant to answer one question quickly and accurately: is anyone still inside?

Many organisations discover during their first drill that the answer is less reliable than they assumed. The list lives on a tablet that has just been left in an evacuated reception. Half the visitors on it went home hours ago without signing out. Staff are not on it at all. And nobody is quite sure who is supposed to be reading it.

None of these problems is hard to fix, but they need to be fixed before the alarm, not during it. This guide covers the decisions and the drill.

What the law expects, in general terms

In England and Wales, the Regulatory Reform (Fire Safety) Order 2005 places duties on the “responsible person” for a premises, including carrying out a fire risk assessment and having appropriate procedures for evacuation in an emergency. Scotland and Northern Ireland have their own fire safety legislation with similar aims. None of these instruments tells you to use a visitor management system, but your evacuation procedure has to account for the people on your premises, and visitors and contractors are among them.

Your fire risk assessor is the right person to advise on how roll-call should fit into your procedure, how many wardens you need and how often you should drill. This guide focuses on the practical mechanics of using sign-in data well.

The sequence, from alarm to all-clear

A roll-call has a small number of steps, and each one needs a named owner.

Roll-call sequence from alarm to reportA three-lane diagram. The system lane: when the alarm is raised, the current on-site list is sent to wardens’ phones. The wardens lane: wardens sweep their zones on the way out, then mark people as accounted for at the assembly point. The roll-call lead lane: the lead collects warden reports, then reports anyone unaccounted for to the fire and rescue service on arrival.SYSTEMWARDENSROLL-CALLLEADAlarm raisedtrigger or buttonList sent to phoneseveryone signed in nowSweep zone, exitno going back inMark accounted forat the assembly pointCollect warden reports by zonestaff, visitors and contractors togetherReport unaccountedto the fire service
Every box needs a named person and a named deputy. The arrow that most often breaks in drills is the one from the system to the wardens’ phones.

Who holds the list

The list is only useful if it is in the hands of the people at the assembly point within moments of the evacuation starting. There are three common arrangements, and many sites use more than one:

  • Pushed to wardens. The system sends the current on-site list to named wardens’ phones when the alarm is raised, either automatically through an integration with the fire panel or when someone presses a button.
  • Opened by wardens. Wardens open the list in an app or browser once they are outside. This depends on them having access, knowing where to look and having signal at the assembly point.
  • Carried out by reception. The receptionist takes a tablet or printed list as they leave. This works only if reception is staffed and the device is close to the exit route.

Whichever you choose, write it into the evacuation procedure, and test whether it still works when reception is unstaffed, when the usual warden is on holiday and when the alarm sounds at 7am or 7pm.

Example ground floor plan showing where roll-call information should beAn illustrative ground floor plan of an office with a reception and sign-in kiosk by the main entrance, three warden zones, two exits and an assembly point outside. A secure box holding a printed snapshot sits by the side exit. Wardens carry the list on their phones to the assembly point. The kiosk is marked as a place the list must not live only, because it is inside the evacuated building.EXAMPLEZONE AZONE BZONE CReceptionKiosk inside theevacuated buildingMain exitAssemblypointSide exitSecure box with a datedprinted snapshotWardens bring the listout on their phones
An illustrative plan. The kiosk, outlined in rose, is the one place the roll-call list must not depend on, because nobody should go back to it once the alarm sounds.

Know what the list does not cover

A visitor system knows about the people who signed in through it. That is usually visitors, contractors and sometimes delivery drivers. It does not know about staff unless staff also sign in, or unless it draws on another source such as an access control system or a desk-booking platform.

With hybrid working, the staff gap matters more than it used to. You can no longer assume that everyone on the payroll is at their desk. If your staff roll-call relies on a team leader’s memory of who came in, that is the weakest part of your process, and it is worth solving at the same time as the visitor list.

Reconciling at the assembly point

Roll-call is a reconciliation: the list of people who should be out against the people who are out. Every name lands in one of four places.

The four outcomes of a roll-call reconciliationA two-by-two grid. One axis asks whether a person is on the on-site list; the other asks whether they are seen at the assembly point. On the list and seen: accounted for. On the list and not seen: unaccounted for, which needs urgent checking because they may have left without signing out or may still be inside. Not on the list but seen: missed sign-in, to be added. Not on the list and not seen: invisible to the roll-call, which is the gap the process is designed to close.SEEN AT ASSEMBLY POINTNOT SEENON THE LISTNOT ONTHE LISTAccounted forMark them off. Nothingmore to do until all-clear.Unaccounted forCheck with host, phone them.Report to the fire service.Never go back in to look.Missed sign-inAdd them to the list now.Find out how they got in.InvisibleInside, never signed in.Only zone sweeps and goodsign-in discipline catch them.
The top-right box is where time goes during a real evacuation. Most of the names in it, in practice, belong to people who left earlier without signing out.

The unaccounted-for box is where sign-out discipline pays off. If visitors routinely leave without signing out, every evacuation produces a list of people who might be inside. Wardens then spend the critical minutes phoning hosts to establish that someone left at lunchtime. Each of those names also has to be passed to the fire and rescue service as unconfirmed, which is exactly what the process exists to avoid.

Practical ways to improve sign-out include returning badges at the desk, automatic sign-out at a set time for visitors who cannot still be on site, sign-out prompts sent to hosts, and making the exit route pass the kiosk. Automatic sign-out needs care: it tidies the record, but it can also remove someone who genuinely is still in the building.

Plan for the list being unavailable

The roll-call must not depend on anyone re-entering the building, or on a single device or network. Think of it as layers, each one a fallback for the one above.

Layers of roll-call fallbackFour stacked layers, each a fallback for the one above. First, the live list on wardens’ phones. Second, a copy of the list stored on the device, readable without a connection. Third, a printed snapshot kept at an exit or in a grab bag, refreshed regularly. Fourth, a headcount by zone from wardens’ sweeps, which needs no list at all.Live list on wardens’ phonesUpdates as people are marked offCopy held on the deviceReadable with no signal at the assembly pointPrinted snapshot at the exitRefreshed on a schedule, dated, kept secureZone sweep headcountNeeds no list at all1234
The lower layers are less accurate but more robust. A procedure that only works at layer one will fail on the day the network does.

A printed snapshot is personal data left in a public place, so keep it in a secure but accessible spot, such as a locked box at the exit that wardens hold keys for, and destroy old copies when they are replaced. A copy on a warden’s phone is personal data on a personal device; your data protection lead will want to know how it is protected and when it is cleared. Our guide to GDPR and visitor data covers the wider retention questions.

Drill the roll-call, not just the evacuation

A fire drill that empties the building but never tests the list will tell you the alarm works and the exits are clear. It will not tell you whether the roll-call works.

When you drill, decide in advance what you will observe. Useful questions include:

  • How long did it take for each warden to have the list in hand?
  • How many names were unaccounted for, and how many of those had simply left without signing out?
  • Was anyone at the assembly point who was not on the list?
  • Did the fallback layers work when you deliberately withheld the top one?
  • Did contractors and delivery drivers know where to go?

Record the answers and compare them over time. You do not need a benchmark from anyone else; you need to know whether your own process is getting more accurate. Run at least one drill outside core hours, and at least one where the usual roll-call lead is deliberately absent.

After each drill, hold a short debrief with wardens and reception. The most useful fixes are usually small: a phone that was not enrolled, a warden who had left, a kiosk placed where departing visitors walk past it.

Where to go next

If your current process still relies on a paper book at the front desk, read the real cost of the paper sign-in book. For why roll-call has become one of the main reasons organisations buy visitor software, see front desk software is becoming facility infrastructure and what a visitor management system actually does. If you are specifying a new system, put the roll-call scenarios at the top of your requirements using how to write a visitor management RFP.