InnerWeb
Skip to main content

Guest after group training and a scan a few minutes later: is it an exit from the plant?

A guest after group training may scan the code a few minutes after completing the training, and in a simple system they would be recorded as leaving. We describe this situation from the perspective of the evacuation coordinator, who is responsible for keeping the list of people on site accurate at every minute.

13 min
window for confirming presence after group training
Source: card
5 s
window for ignoring a double scan
Source: card
12 h
threshold for automatic check-out
Source: card

Situation: a group of guests after training at the reception post

A group of contractors or guests arrives at the plant. Before entering the site they attend a joint introductory training at the reception post, and after passing it each person scans their own code. With a dozen or so people at once, someone scans the code a few minutes after the training, either because they are not sure the previous scan was recorded or because the queue at the post is moving.

For the evacuation coordinator this is a situation with real risk. The list of people on site is the basis he uses during an evacuation. If the system treats such a scan as an exit, the person disappears from the list although still in the building. If the system accepts every scan as an entry, the list swells with people who have left.

The description is a typical situation from organising guest traffic, not the story of a single plant. It shows which rules the system must have so that the list of people on site stays reliable even when people behave in groups.

How the system distinguishes confirmation from exit

In the security panel the scan itself is an act of control: there is no separate button to let someone in. The first scan with a green verdict records an entry, the second an exit, and a scan with a red verdict records a refusal. This rule is clear for the guard, but with group training it needs an exception.

The exception is built into the system: after completing group training at the reception post, the next scan within 13 minutes is treated as confirmation of presence, not an exit. After 13 minutes the normal rule of entry and exit applies. Thanks to this, a person who scans a second time directly after training remains on the list of people on site.

The second layer of protection is a filter for double scans. A double scan of the same code within 5 seconds is ignored on the server side: no new entry, with an informational message about a duplicate scan. The two mechanisms cover two different situations: the same reflex within a few seconds, and a scan a few minutes after training.

Why exactly 13 minutes

The window must be longer than the time the group needs to finish the training, while the reception post and the gate handle the queue. At the same time it is short enough that a genuine exit by a person who is really leaving the site is recognised as an exit once this time has passed. This is a compromise, not a universal rule, and the coordinator should know its value.

Time windows that protect the list of people on site

Time windows that protect the list of people on siteBar chart: 5-second window for a double scan, 13 minutes after training, 180-minute check-out cycle and 720-minute check-out threshold.0200400600800minDouble scan (5 s): 0.08 min0.08 minDouble scan (5 s)Confirmation after training: 13 min13 minConfirmation aftertrainingCheck-out cycle (3 h): 180 min180 minCheck-out cycle (3 h)Check-out threshold (12 h): 720 min720 minCheck-out threshold(12 h)
Source: Documentation of the security panel and QR gate functions

What it means for the evacuation list

The list of people on site is built from recorded entries and exits. A blocked entry attempt is also written to the register as a refusal entry, but it does not count as presence on the site or on the evacuation list. This way a person the gate did not admit is not searched for inside the building during an evacuation.

From the coordinator's perspective three distinctions matter. First, confirming presence after training does not change the status: the guest is still on the list. Second, an exit is recorded only after the 13-minute window, so a group leaving the site at the end of the day is settled normally. Third, a refusal is not presence, so the list does not contain people who did not enter.

These rules are worth knowing in advance, because it is the coordinator, not the guard, who is responsible for the result at the moment of an alarm. Register entries are evidence for later analysis: they show who was recorded as present, and when.

Forgotten exits: the other side of the same problem

The window after training protects against a false exit, but it does not solve forgotten exits. A person who left the site without scanning remains on the list of people on site. The system has a separate mechanism for this: a person staying on the site for more than 12 hours is checked out automatically, the task runs every 3 hours (8 times a day), and the entry is marked as closed automatically.

For the coordinator this means the list of people on site is cleaned with a delay of up to several hours after the threshold is exceeded. During an evacuation, an entry marked as closed automatically should therefore be treated as a signal to verify, not as proof of exit.

Conclusions for the evacuation coordinator

Establish and write into the reception post instructions that a group after training scans once, and a second scan within 13 minutes is a confirmation. Inform the training leaders not to ask the group to scan again when leaving the reception post.

Make sure the guard knows that the duplicate scan message is information, not an error. Once a month review the entries closed automatically: their number shows how often an exit scan is skipped and whether the signalling at the gate needs improving.

Checklist

Video

Frequently asked questions

Will a guest who scanned the code after training disappear from the list of people on site?

No. The next scan within 13 minutes of completing group training is treated as confirmation of presence, so the guest stays on the list.

What if someone really leaves 10 minutes after training?

Within the 13-minute window the scan is a confirmation, so the exit is recorded only at a later scan after that time. For such exceptions it is worth informing the security team.

Is a refused entry visible on the evacuation list?

No. A refusal entry goes to the register, but it does not count as presence on the site or on the evacuation list.

How often does the system close forgotten exits?

The task runs every 3 hours, 8 times a day, and checks out people who have stayed on the site for more than 12 hours.

Want to see the list of people on site in action?

We will show, on demonstration data, how a group of guests passes through the reception post and the gate, and what the evacuation list looks like.

Let's talk