InnerWeb
Skip to main content

Check-out after group training: the 13-minute window at reception

A visitor finishes a group induction, scans their code and, from the system's point of view, leaves the plant. The guard at reception sees the list of people on site shorter by the whole group, although everyone is still in the room. This is the situation the protection window after passing group training solves.

13 min
window after passing group training
Source: security panel function card
12 h
stay limit before automatic check-out
Source: security panel function card

Problem: a scan after training counted as an exit

At a production plant that receives visitors and contractors in groups, the induction takes place for the whole group at once, at the registration post. After passing the test, participants scan their code to confirm they are ready to enter the site.

The rule of the system says that the first scan of an authorized employee records an entry and the second records an exit. The scan itself is an act of control: there is no separate button to let someone in. In practice this meant that a participant already registered as entering would, after one more scan, drop off the list of people on site, even though they were still standing at reception with a coffee cup.

For the guard the effect is immediately visible. The list of people on site, which the evacuation relies on, is incomplete exactly when a dozen people are crowding the reception. The guard has to either guess or add names by hand, and both options cause errors.

Solution: a protection window after passing the training

A scan made up to 13 minutes after passing group training at the registration post is not counted as an exit. It only confirms presence. The participant scans their code, the system recognizes that the training has just been passed, and does not switch their status to exit.

The window is narrow for a concrete reason. It is long enough for the group to walk from the test screen to the gate and scan codes in the queue, and short enough that a real exit after a dozen minutes is already treated as an exit.

What the guard sees at the gate

The guard does not have to change anything in their work. The scan is still an act of control, and the list of people on site stays complete. If the same code is scanned a second time within a few seconds, the panel ignores it as a duplicate and shows a message that the scan was ignored, not an error. This matters in a queue where someone presents their code twice out of uncertainty.

What about a visitor who forgets to leave

The 13-minute window does not replace ordinary handling of a forgotten exit. A person who did not scan their exit is checked out automatically when they stay on site for more than 12 hours, and the task runs every 3 hours. The window protects the start of the visit, and the automatic check-out protects its end.

Time windows for handling scans

Time windows for handling scansHorizontal bar chart of three time windows: 13 minutes, 180 minutes and 720 minutes0200400600800minWindow after trainingWindow after training: 13 min13Check-out task cycleCheck-out task cycle: 180 min180Stay limitStay limit: 720 min720
Source: Security panel function card: 13 minutes, 3 hours, 12 hours converted to minutes

For the guard: how to recognize that the window worked

The guard should be able to check three things without calling the administrator. First, whether the group is visible on the list of people on site right after the training. Second, whether scanning an already scanned code within the window left the participant's status unchanged. Third, whether a refusal for a person without valid training is still recorded in the register: a refusal leaves a trace, and a person who was refused is not counted as being on site.

  • after the training the number of people on the list matches the number of participants
  • a second scan within the window shows that presence is confirmed
  • a scan after the window has passed is already an exit
  • a refusal for lack of training still goes to the register

For the plant: what changes in evacuation and reports

The list of people on site is the source of truth during evacuation drills and real alarms. Every gap in this list is a person nobody looks for at the assembly point. The protection window closes the most common gap that results from the scanning mechanism itself, not from human error.

For the shift report this means one thing: the outgoing shift can hand over to the incoming shift a list that matches the actual state. The details of the shift handover are described on a separate page about good practices for handing over a security shift.

Conclusions

The 13-minute window is a small rule with a large effect: it removes accidental exits caused by the natural behavior of training participants. The plant does not need to change its training procedure or hire an extra guard. A properly configured registration post is enough.

Video

Frequently asked questions

Does the window also work for a single visitor?

The window applies to group training at the registration post. A single scan at the gate is an ordinary act of control: the first records an entry, the second an exit.

What if a visitor leaves the plant in the 10th minute?

The system treats a scan within the window as confirmation of presence. If a person actually leaves the site, the guards should reflect this in the procedure, and if an exit is forgotten, automatic check-out applies after 12 hours.

Does a duplicate scan create an error in the register?

No. A repeated scan of the same code within a few seconds is ignored, and the panel shows that the scan was ignored.

Do you train visitors in groups?

We will show a registration post with a post-training window and a list of people on site. Let's arrange a short call.

Let's talk