What the change involves
In the manual model the scan serves as a preview, and a person clicks "let in". In the model with a scan as the decision, the system sets entry, exit or refusal from the current verdict and the on-site status, without a separate button. Every attempt, including a refusal, is recorded.
For security this means a change of role: the guard does not decide on the rule, but handles the exceptions. It is worth putting this into the procedure, so that nobody bypasses the scan by opening the gate by hand without a record.
Preparation stages
The order matters, because the button cannot be switched off effectively before the verdict has been checked on real groups.
Stage 1: defining the verdict components
The verdict has four components: no overdue training, no missing qualifications for dangerous work, a work permit in progress for today, and an active account. Before the go-live, check whether all four can be met for each group of people entering, that is employees, contractors and visitors. A group that by nature has no work permit for today will receive refusals.
Stage 2: attempts on the test gate
Pass through the gate with three scenarios: a person who meets everything, a person with overdue training, and a person without a work permit. Observe the messages shown to security and to the person scanning. The security team should know every refusal message and how to explain it.
Stage 3: parallel run
For the first days keep manual confirmation alongside the scan, but record the differences. A gap between the system's decision and the human's decision is material for improving the settings, not for a dispute with security.
Stage 4: switching off the button
Once the differences have disappeared, remove the manual button from the procedure. An exception path remains: a person who was refused goes to the shift manager, who has the authority to settle the case.
Stages of the move to a scan as the decision
Pitfalls of a scan as the decision
The first pitfall is a double scan. Two scans of the same code in a short interval are filtered out: the server applies a duplicate-scan window, and the browser additionally discards an identical string within a few seconds. This way a slower response does not overwrite a faster one on the screen. Security should know that presenting the code again right after the first scan changes nothing.
The second pitfall is people who entered and did not leave through the gate. The system closes a stay automatically after 12 hours, and the check runs every 3 hours. Without this, the on-site status would keep growing with people who left by another route, and the next scan would record an exit instead of an entry. The security manager should set expectations: closing after 12 hours completes the data, but does not replace the discipline of leaving through the gate.
The third pitfall is a refusal without explanation. A person refused at the gate wants to know why. Prepare a short instruction: which component of the verdict failed and whom to contact.
What to measure after go-live
After a month, compare the number of refusals per verdict component. If most are overdue training, the problem lies in training planning, not in the gate. If most are the lack of a work permit for today, the teams ordering the work are late with their applications. The gate data then becomes material for discussions with departments, rather than only a log of entries.
Checklist
Video
Frequently asked questions
Is every refusal recorded?
Yes. Every attempt at the gate, including a refusal, is recorded and can be reviewed in the history.
What about a person who did not leave through the gate?
The system closes their stay after 12 hours, and the check runs every 3 hours.
Will a double scan spoil the on-site status?
No. The server applies a duplicate-scan window, and the browser discards an identical string within a few seconds.
Let's plan the change at your gate
We will go through the four stages of the move to a scan as the decision with your security team. Book a conversation with the InnerWeb team.
Let's talk