InnerWeb
Skip to main content

Guests arriving by car at the gate: how to separate them from pedestrians

When guests arriving by car and pedestrians use the same scanner, a queue of cars can block the entry of employees. We collect seven recommendations for the head of security: how to separate the paths, what the gate register records and when to use a second scan as an exit.

5 s
window for merging repeated scans of the same code
Source: feature sheet
13 s
refresh interval of the evacuation list
Source: feature sheet

Who these recommendations are for

We address these recommendations to the head of security and the plant director, at a plant where employees, pedestrian guests and people arriving by car all enter through the same gate. The typical symptom of the problem is a queue of cars in front of the barrier, in which a driver gets out to scan a QR code while pedestrians behind him rush to get in before the shift.

For comparison: scanning the QR code on a badge or the card number is the control itself. There is no separate button to let someone in, so the scanner station is a physical bottleneck. Every second the scanner station is occupied by a driver with a car lengthens the queue, which nobody sees in the register, because the register only sees the scans.

Seven recommendations

The recommendations below are ordered from the cheapest in organisational terms to those that require changes on the site. Each has a justification that follows from how the system works at the gate.

1. Separate the scanner stations

Pedestrians and drivers should have separate scanner stations, ideally with a separate screen for the duty officer. If this is not possible, set peak hours for pedestrians and reserve them for pedestrian traffic. The gain is immediate: a driver with a car does not block the entry of an employee.

2. Do not stop the car at the scanner

If the scanner is to be operated from a car window, mount it at the height of the driver's window. Stopping the car only so the driver can get out lengthens the process. Where the height cannot be reached, the duty officer scans the code from the driver's phone held up to the glass.

3. One scan per person rule

Passengers enter the site separately, each with their own code. Two scans of the same code within 5 seconds are recorded as one event, because the scanner can read the same code several times in a fraction of a second. A second scan does not reverse the direction of entry or exit.

4. Exit as a second scan

A second scan by a person who is already on site and has a green verdict records the exit. Explain this to drivers on a sign at the gate, because without the exit being recorded the list of people on site grows and no longer reflects the actual state.

5. Recording blocked attempts

Every scan is saved as a gate entry, including a blocked attempt. As a result the list of people currently on site is a fact from the register, not an assumption. Review blocked attempts once a week, because they show where the path leads people the wrong way.

6. Evacuation list as a test

The evacuation list is built from QR scans at the gate, refreshes every 13 seconds and divides people into six groups: guests, couriers, suppliers, plant employees, external companies and uncertain. If the uncertain group grows, entries and exits are not being scanned consistently.

7. Rule for company vehicles

For suppliers with a prior notice use the deliveries module, not the guest path. This makes it easier to assign the driver to a gate, dock or warehouse, and separates him from guest traffic.

Waiting time of the last of 8 cars in the queue at the scanner

Waiting time of the last of 8 cars in the queue at the scannerBar chart: the last of eight vehicles waits 24 minutes with three-minute handling and 8 minutes with one-minute handling.0510152025minHandling 3 min per vehicle: 24 min24 minHandling 3 min per vehicleHandling 1 min per vehicle: 8 min8 minHandling 1 min per vehicle
Source: Example calculation: 8 vehicles in the queue, handling time of 3 min (paper) and 1 min (scan) as illustrative assumptions

How to implement it within a month

In the first week measure the current state: how many times a day a queue of cars stops pedestrian entry and for how long. In the second week set up separate paths or peak hours. In the third introduce the one scan per person rule and a message about scanning the exit. In the fourth check the evacuation list and the number of entries in the uncertain group.

This rhythm makes it possible to assess whether the change worked before investing in additional infrastructure. If the queue still forms, the problem lies in the number of vehicles at peak time, not in the path.

What the system does not promise

InnerWeb does not read licence plates, does not control the barrier and does not manufacture readers. Separating the paths is the plant's decision, while the system provides the register, the verdict and the list of people on site. The rules for the physical movement of vehicles should be agreed with the technical department and the supplier of the entry infrastructure.

Video

Frequently asked questions

Must pedestrian guests and guests in cars have separate scanners?

They do not have to, but it is the simplest way to avoid a blockage. If this is not possible, split the peak hours or place the scanner where both groups can reach it without stopping the car.

What happens when a driver scans the code twice?

Two scans of the same code within 5 seconds are recorded as one event. A second scan does not reverse the direction of entry or exit.

Who can see that guests arriving by car are on site?

The list of people currently on site comes from the gate register, so it is visible in the security panel and on the evacuation list, divided into six groups.

Let us measure the queue at your gate

We will show the guard panel and the evacuation list in a demo, and together we will agree the paths for pedestrians and vehicles.

Let's talk