A School Roll-Call App: Does “Registered Today” Mean Accounted For at the Assembly Point?

A school considering a digital evacuation roll call needs to distinguish its ordinary attendance records from observations made during a particular evacuation. A pupil recorded in class earlier, a contractor signed in at reception and a person confirmed at the assembly point are not the same kind of evidence. Specify the incident reconciliation and reporting workflow before buying a faster scanner.

This is a software commissioning guide, not an evacuation plan, fire-safety assessment or certification. A competent responsible team must determine the school's actual arrangements and applicable local requirements. Software must support that approved plan, not delay evacuation or direct anyone to search a building.

Define the population that needs checking

A current class register can help prepare a roll call, but its entries should not automatically become confirmations at the assembly point. Agree how the approved process includes pupils away from their usual class, staff, visitors and contractors. An appointment list is not proof that a visitor arrived, and a missing sign-out is not proof that they remain inside.

The London Borough of Tower Hamlets school fire-evacuation guidance calls for an assembly-point count checked against attendance registers and the visitors book. It explicitly includes visitors and contractors. This is guidance published in a London school context, not a universal legal specification for every country.

For a digital project, ask the school's responsible team which records are used and how uncertainties are reported. Show the origin and freshness of the expected-person list. Do not advertise it as an infallible live count simply because it is stored online.

Record confirmations for this evacuation

As a practical software requirement, give each drill or incident its own roll-call record. A confirmation from yesterday's drill must not satisfy today's check. Capture the person, the relevant assembly group, who recorded the observation and when it was recorded under the approved procedure.

Separate “not yet checked”, “confirmed at the assembly point” and an authorised explanation of a discrepancy. The school must define appropriate terminology and evidence. Do not make a report of possible absence disappear merely because another screen says the person was booked into a class.

If several staff members account for different groups, preserve their reports without counting the same person twice. Corrections should remain attributable. A global “mark class safe” action needs a carefully approved meaning; a convenient bulk button is not evidence that every pupil was actually accounted for.

Make the coordinator's handoff explicit

Tower Hamlets describes each teacher reporting to the nominated person in charge, confirming that people are accounted for or reporting how many are missing. It also identifies information for the Fire Brigade, including whether anyone is missing and their usual or last-seen location.

The application's summary should therefore support the school's nominated coordinator, not simply display a total number of taps. Keep unresolved identities, relevant location information and the source of each report intelligible to the authorised staff. A named person's unresolved status can matter even when two aggregate totals happen to match.

This is a reporting handoff, not an automated instruction to enter the premises. The same source says nobody should re-enter until told by the attending Fire Service or, for a drill, the senior person in charge. A completed digital checklist is not permission to return.

Plan for the tool being unavailable

Have the responsible team approve how the procedure works if a device, connection or school system is unavailable. Do not describe offline operation as supported until its actual behaviour has been demonstrated. Stale cached attendance and competing updates need visible handling, not an unexplained green completion badge.

Use synthetic people in a planned, supervised acceptance exercise. Test a contractor, a pupil assigned to a different group, a duplicate confirmation, an unresolved person, a correction and an unavailable device. Demonstrate the approved fallback without retrieving equipment from an unsafe area. Restrict access to the personal information needed by the authorised roles.

For the app acceptance criteria, agree what the coordinator must be able to see and what remains unresolved. Bring the school's approved procedure to a business-app discussion. The deliverable is a tested record-and-handoff aid within that procedure, not a claim that software alone guarantees everyone's safety.