The question during an evacuation Present is not the same as access Contractors and visitors too

Custom attendance registration software

During an evacuation, there is one question: is everyone out? To answer it, you need to know who was inside, and that is not the same as who has a pass. Someone who followed through a held-open door is not in any system, and neither is the contractor who came in through the loading door at seven o'clock.

Why your access control system does not answer this question

An access control system records that someone passed a reader somewhere. That is not the same as presence. Someone who scans in and leaves again through an emergency exit is still shown as inside. Someone who tailgates a colleague holding the door open never appears at all. In a building where a hundred people work, those two numbers can quickly drift tens apart.

Then there are the groups without a pass: visitors, engineers, temporary staff, suppliers and contractors. They are the least familiar with the building and the most vulnerable during an evacuation. In practice, they are listed in a paper book at reception, which has not been signed out by the end of the day.

So the challenge isn't technology but completeness. An attendance list that is eighty per cent accurate is more dangerous in an evacuation than no list at all, because the emergency response team goes inside for someone who isn't there. Everything in this system revolves around how to capture that last twenty per cent without getting in the way of the work. You can read more about what emergency response involves at Arboportaal.

How we build this

We start with the groups that are currently missing, not the people who already check in properly. That's where the gap is, and so that's where the value lies.

1
Mapping the gaps

Who comes to your site and by what route: your own people, agency workers, visitors, engineers, drivers. For each group, the question is who currently records their presence. Usually half of those groups turn out to be recorded nowhere.

2
Choosing a workable route for each group

What works for an office employee doesn't work for a driver who stays twenty minutes. One method for everyone always leaves one group that skips it.

3
Building the evacuation list first

Every sprint ends with something you can check for yourself, and we start with the screen that is used during an evacuation. Anything that isn't needed on that screen doesn't need to be recorded either.

4
Practising with a real evacuation

We take part in your evacuation drill. It's the only test that counts, and it shows whether the list is accurate and whether someone can read it on a phone in the rain.

What the software actually does

It all comes down to one screen that is correct at the moment it's needed. The other components exist to keep that screen populated.

Live attendance list

Who is on site right now, at which location or in which part of the building, distinguishing between your own employees, visitors and external staff. Available on a phone, even if the network in the building goes down.

Signing in within seconds

A code at the entrance, a scan of a pass or a confirmation on the phone. If signing in takes longer than walking through, people skip it, and then the list is worthless.

Visitors and contractors registered in advance

A host registers their visitor, the visitor receives a code and checks themselves in. For contractors, you can attach conditions, such as a safety briefing that has been read.

Automatic check-out and clean-up

People forget to check out, and that is the main source of contamination. Rules per group, such as checking out at the end of a shift or after a period of inactivity, keep the list usable without anyone cleaning it up manually.

Evacuation mode

One screen showing who was inside when the alarm sounded, ticked off person by person, with what is still outstanding. That's a different screen from the daily list, and it has to work without anyone having to think.

Integration with what you already have

Your access control system, your HR system and your time tracking already know something. We use that as a signal and fill in where the gap is, rather than building a second administration.

Who we build for

Who comes to your site determines how much this matters. Four situations.

Manufacturing and industry

Shift work, agency workers and supplier engineers all mixed together. Here the evacuation list isn't administration but a safety measure, and the number of external people is often larger than you'd think. If a risk assessment is also part of the picture, see RI&E and action plan.

Building sites and project locations

Changing crews from changing subcontractors, with no permanent reception. If an inspection log for work equipment is also part of the picture, see work equipment inspection log; that one covers equipment, where this page covers people.

Offices with flexible working

Nobody knows any more who is in on a Tuesday. Alongside the safety side, occupancy plays a role here: how many workstations and how many lunches, and that's the same registration with a different purpose. If your main concern is receiving and signing in guests, visitor registration software is the other answer; this page is about the complete list of who is inside.

Healthcare and education

Visitors, volunteers and pupils alongside staff, with sites that stay open all day. What matters most here is that signing in never holds anyone up and that the list can be read per part of the building.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

One design requirement outranks all others: this system must work at the moment something goes wrong. That means the list stays available on a phone if the building's network goes down and when the power is off.

If you record attendance at a school and need to report unauthorised absence on time, take a look at our app for absence registration and truancy reporting.

Node.js / Python / .NET PostgreSQL Native iOS and Android Local copy of the list for emergencies QR and NFC sign-in Integration with access control system Integration with HR or time tracking Automatic check-out rules per group Visitor invitation by email or link Evacuation mode with sign-off Retention periods enforced by the system Roles per site Audit logging Hosting in the EU

Why Appfront

A list that is eighty per cent accurate is dangerous

Emergency responders go into the building for someone who isn't there. That is why we design for completeness rather than for features.

Faster than walking straight through, otherwise it won't happen

Our benchmark is that signing in takes less time than holding the door open. If the design doesn't achieve that, it isn't finished.

Everyone forgets to check out

That isn't a behaviour problem but a design problem. We solve it with rules per group rather than with reminders.

Handling who was where with care

This data shows who was where and when. We keep retention periods tight and separate the safety function from every other use.

Security and privacy

Attendance data is personal data with an awkward property: it is useful for safety and tempting for everything else. Who was here at half past three last Tuesday is a question that is quickly asked after a theft, a conflict or a conversation about attendance patterns. That is why we separate the uses: the evacuation function knows the current list, while looking back through the history is a separate permission that is logged.

Retention periods are the most important design decision here. For the safety function you need today's data, not last year's; for an incident investigation, a limited period. You set that period together with your data protection officer, and the system enforces it so that nobody ever has to clean up manually. If you have a works council, introducing the system is also something to discuss with them beforehand: attendance registration touches on the monitoring of employees, even when that isn't the intention. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about on-site attendance

No, and that difference is the reason this page exists. An access control system records passages past readers; attendance answers the question of who is inside right now. Anyone who leaves through an emergency exit or follows a colleague in doesn't add up in the one system. We do use your access control system as a signal, but it is not the source.

No, and we recommend keeping the two separate. Time tracking is about hours worked and pay; attendance is about safety. Mixing them causes two problems: employees start to distrust the attendance registration, and then the evacuation list becomes unreliable again. They can be integrated, but as two systems with their own purpose.

By making check-in so light that it never gets in the way: a code at the entrance, an invitation sent in advance with a link, or a tablet at reception. For contractors, you can attach a condition, such as confirming a safety briefing. That doubles as proof that they have had it.

They will, guaranteed, so we solve it in the design. You set a rule per group: automatic check-out at the end of a shift, after a period of inactivity, or when passing through an exit. Without rules like these, the list fills up within a week with people who left long ago.

That is the most important requirement here, because that is exactly when you need the list. The app keeps a local copy on the phones of your emergency response team, so the last known status stays available. Also discuss who holds those phones and whether they are charged; that is not a software question, but it determines whether it works.

For the safety function there is usually a sound legal basis, but the details matter: which data, how long it is retained and who may look back at it. You assess that with your data protection officer. Discuss it with your works council too, because attendance registration touches on monitoring of employees, even when that is not the purpose.

Often it can, and it reduces admin: employees are then added and removed automatically as they join and leave. Your HR system remains the source for who is employed; we only track who is present. Which integration is possible depends on your package; we map that out via integrations before committing to anything. That is handled through integrations.

That depends on the number of locations, the number of groups you want to register and whether it integrates with access control or HR. The attendance list with evacuation mode is usually usable quickly and delivers the most value; the visitor portal and the integrations cost more. We give a well-founded estimate after the discovery phase.

Building attendance registration?

Ask yourself how many people are on your site right now and where that number would come from. If the answer is a hesitation, you know why this system exists. We build this as a standalone app and as part of a broader custom software project.

Edit content