InnerWeb
Skip to main content

Guard post with a scanner: best practices for the head of security

A guard post with a scanner has one task in the peak hour: let several dozen people through without jams and without losing control. Below are practices for the head of security on arranging the scanner, the screen, the labels and the response to situations in which the code does not work.

5 s
window for ignoring a double scan
Source: card
2 characters
minimum to search for a company on the gate screen
Source: card

What the guard needs at peak hour

In the shift's peak hour there are several dozen people at the gate, and each scan must give the guard a clear answer: let in or not. A post that forces searching the screen with the eyes slows traffic down. A post that gives a readable person card after one scan allows keeping the pace without lowering control.

For the head of security three things matter: how the equipment is arranged, the readability of the screen and the scenario for when the scan does not work. Each of them has its place in the practices below.

Practices for the post

Six practices that can be implemented without changing the system.

1. Scanner within reach, screen in view

The scanner should lie or hang so that the guard scans the code without standing up and without turning away from the person at the barrier. Place the screen with the person card at the same eye level. The person card at the gate shows a photo, a green mark Entry allowed or a crossed-out red No consent mark, and the full lists of qualifications and trainings with the number of days until expiry, so the guard reads the verdict by its colour before reading the text.

2. Photo instead of asking for the name

The photo on the person card lets the guard check whether the badge is shown by the right person, without a conversation at the barrier. A simple rule: the guard compares the face with the photo and asks a question only when in doubt. This way the control is faster and more resistant to swapped badges.

3. Manual verification as a standard scenario

When the code does not work, the guard does not need to stop the queue. Searching for a company on the gate screen (from 2 characters) shows its employees with a column for today's permit, and allows checking the person manually. Internal companies are not on this list, because their employees have their own badges. This scenario is worth rehearsing during a trial shift, so the guard does not have to look for the function under pressure.

4. Do not react to a double scan as to an error

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. At peak hour it happens that the guard or the guest scans twice in a hurry. The message means the entry is already recorded and nothing needs to be repeated.

5. A second scanner or a spare cable

The scanner is the element most often replaced at a post. A second unit configured like the first shortens downtime. In USB-COM mode the scanner may appear as two ports of the same device, but the panel opens all ports of the device and removes duplicates within a 2584 ms window, so working with two scanners at one post does not produce duplicate entries.

6. Labels and printing prepared before the peak

The badge printout scales to the label size given by the printer driver. Before the peak, check that the printer has the right label size and a spare roll. A badge with the plant logo and without the server name is neutral and needs no further correction.

Timing and search thresholds at the guard post

Timing and search thresholds at the guard postBar chart with three thresholds: 34 ms scanner character gap, 2584 ms removal of duplicate ports and 5000 ms ignoring of a double scan.010002000300040005000msScanner character gap: 34 ms34 msScanner character gapDuplicate USB-COM ports: 2584 ms2584 msDuplicate USB-COM portsDouble scan: 5000 ms5000 msDouble scan
Source: Documentation of the security panel and QR gate functions

Security of the post itself

The code from the badge is treated only as a string to match against a pattern, never as an address to open, HTML code or a command, and its length is limited. A foreign code, for example from a forged badge, will not launch anything on the guard's computer. For the head of security this means the post needs no separate policy for foreign codes: it is enough that the guard refuses the person with an unknown code and directs them to reception.

Blocked entry attempts go to the register as refusal entries, which gives the head of security data for review: how many attempts there were, at what times and for what reasons.

How to measure whether the post works

The simplest measure is the number of refusals and manual verifications in the peak hour. An increase in manual verifications signals a problem with the scanner or the badges, and an increase in refusals due to training points to a problem on the side of those who invite guests. Review these numbers once a week during the first month, and then once a month.

Checklist

Video

Frequently asked questions

What to do when the scanner does not read the code?

Use manual verification: search for the company from 2 characters and check the person in the column for today's permit. The queue does not need to be stopped.

Will two scanners at one post create duplicate entries?

No. Duplicate ports of the same device are removed within a 2584 ms window, and a double scan of the same code within 5 seconds is ignored on the server side.

Are internal employees on the company search list?

No. Internal companies are not on this list, because their employees use their own badges.

Arranging a guard post?

We will show the person card, manual verification and the refusal register on a test post, and help arrange the equipment for the peak hour.

Let's talk