InnerWeb
Skip to main content

Plant Evacuation and Attendance List: A Guide for Plant Directors and OHS Managers

In the first minute of an alarm, the incident commander needs one answer: who is physically on site right now. This guide shows who is responsible for the attendance list, how to build it from entry and exit scans, and what record remains after the evacuation as audit evidence.

4
conditions checked at the gate scan
13 s
evacuation list refresh interval
24 h
window for flagging unconfirmed persons

Why a paper list fails in an industrial plant

A large plant hosts employees from several shifts, supplier drivers, couriers, visitors and contractor staff doing maintenance work at the same time. Each group signs in somewhere different: employees in the working time records, visitors in the entry log, contractors on a list announced by their coordinator. During an alarm someone has to merge these sources by hand into one sheet, and that takes time exactly when time is short.

The second weakness is that the data goes stale. A planned list, meaning who was supposed to come today, does not say who actually entered or who has already left. In a gatehouse audit, check one thing: is the evacuation list generated from actual entries and exits, rather than from a rota or an advance notification? Only gate scans answer the question about the real situation.

Who is responsible for evacuation and for the list

Responsibility for organising evacuation rests with the employer and follows from the Polish Labour Code and fire protection regulations on evacuation. Where several employers operate on one site, Article 208 of the Labour Code requires them to cooperate and appoint a coordinator who oversees compliance with safety rules. In practice, a plant with dozens of contractors needs one shared picture of who is on site, not as many lists as there are companies.

It is worth writing the division of roles into the procedure: who runs the operation and decides to evacuate, who opens and prints the list, who collects the sheets at the assembly point and who closes the headcount. The gatehouse supplies the data, the incident commander uses it and group coordinators verify it. Separating these functions means nobody is both the sole collector and the sole recipient of the data.

Time to prepare the list during an alarm

Time to prepare the list during an alarmChart comparing the illustrative time to prepare the list by hand and from scans051015minList compiled by hand (Gathering sources): 15 min15 minList from scans (Gathering sources): 0 min0 minGathering sourcesList compiled by hand (Writing out the list): 10 min10 minList from scans (Writing out the list): 1 min1 minWriting out the list
  • List compiled by hand
  • List from scans
Source: Illustrative calculation: assumptions of 15 min to gather sources and 10 min to write out the list by hand; 1 min to print from scans

How to build an attendance list from scans

The foundation is a single source: a QR code scan from a badge or phone at the gate. The first scan records entry, the second records exit. In a sample deployment at a manufacturer of insulation materials running continuous operations, the system checks 4 conditions at every scan: valid training, qualifications for permit-to-work tasks, a permit for today and an active account. If any one is missing, access is refused and the reason is shown on screen. The same scan therefore feeds both access control and the evacuation list, with no second register.

The list in the InnerWeb system refreshes every 13 seconds and splits people into six groups: visitors, couriers, suppliers, plant employees, contractors (with a tab per company) and unconfirmed persons. Trade-offs are settled in favour of showing too many people rather than too few: it is better to search for someone who is already gone than to overlook someone who stayed.

Unconfirmed persons and the 24-hour window

An unconfirmed person is someone who entered but did not scan out. In the described deployment, the window for flagging such people is 24 hours: until then the record is treated as possible presence and shown in a separate group. During an evacuation, the unconfirmed group is the list to check first, by voice, by phone or through the contractor's coordinator.

What the list does not do

The list relies on gate scans, so it does not know where a person is inside a building and it is not an electronic roll call at the assembly point. The system does not control the turnstile or the barrier: the guard admits people physically, while the system provides a verdict and a record. A printout does not replace the plant evacuation procedure.

Printout, assembly point and headcount

The evacuation printout is one page per group. This lets the incident commander hand sheets to coordinators at the assembly point: one for plant employees, one for each contractor, one for visitors. The coordinator ticks off those present and reports missing names to the incident commander. Manual ticking is deliberately kept, because it is what confirms presence at the assembly point.

Before an evacuation, check that the gatehouse printer works, that an offline backup printout exists and that coordinators know their groups. A procedure without these simple elements ends in improvisation at the first real alarm.

Audit evidence and the Polish Civil Protection Act

The Polish Act of 5 December 2024 on Civil Protection and Civil Defence has applied since 1 January 2025, and selected provisions enter into force on 1 January 2027. It does not contain a single catalogue of evacuation duties for plants: they are mainly affected by rules on protective structures and places of temporary shelter, on the warning system and on benefits during a state of emergency. The full catalogue of workplace obligations and the content of the 2026 amendment remain to be confirmed in the text of the acts, so we base the evacuation plan on fire regulations and the Labour Code and treat the Act as context.

For an auditor, the trail is what counts. The scan register with entry and exit times, the list printout with its generation time and the headcount record from the assembly point form an evidence chain from the event to its closure. Such records support the requirement of a documented drill and a post-evacuation report; they do not, of course, replace the assessment of inspection authorities.

Five implementation steps for a plant

The order matters, because the quality of the list depends on the quality of the scans.

  • Import the contractor register and assign badges, because without this access control makes no sense.
  • Require a scan for every entry and every exit, including visitors and couriers.
  • Record in the procedure who opens the list, who prints it and who runs the headcount.
  • Run a drill with a printout and count the people at the assembly point.
  • Record the conclusions and adjust the procedure before starting the next cycle.

Checklist

Video

Frequently asked questions

Does the evacuation list replace the evacuation plan?

No. The list is a tool for establishing who is on site. The evacuation plan, routes, signage and procedures remain in the plant's documents.

Does the system know a person's location inside a building?

No. The list relies on gate scans, so it shows who entered the site and has not left, without indoor location.

What about people who forgot to scan out?

They go into the unconfirmed group and appear on the list. During an evacuation they are checked first.

How often does the list refresh?

Every 13 seconds, so the screen during an alarm shows a state very close to the current one.

Sources

Let's talk about an evacuation list at your plant

In a demo we will show how the list is built from gate scans and what the printout for coordinators looks like. Book a conversation with the InnerWeb team.

Let's talk