InnerWeb
Skip to main content

Testing employee phones before a QR code scan

A pilot with a QR code on the phone is most often spoiled not by the system but by small details: a dimmed screen, a cracked film, a code that is too small, or a browser that does not open the link. This guide describes a test on a sample of phones that the IT department can run in half a day before the first scan at the gate.

13 mm
minimum size of a printed code
Source: feature card: Security Guard Panel & QR Gate Control

Why test before the pilot

Employees' phones differ in age, operating system, screen protection and power-saving settings. When a problem appears at the gate, it costs the guard's time and irritates the queue. The same problem found on a table in the IT room costs a minute.

The test requires no tools beyond a few phones, the scanner used at the gate and a printed label. You enter the result into a table, which you later attach to the pilot note.

Step 1: choose a sample

Take phones from different groups: the oldest and the newest, with and without a protective film, with different browsers. A good sample is a dozen or more devices, including several phones of workers from the shop floor, because their screens are often the most scratched.

A private phone remains voluntary: you ask the employee to take part in the test, and you record the results without personal data, only as a description of the device and the result.

Time of individual test steps

Time of individual test stepsHorizontal bar chart: five test steps with a total time of 240 minutes020406080100minSelecting the sampleSelecting the sample: 30 min30Scan at the gateScan at the gate: 90 min90Size and printoutSize and printout: 30 min30Browser and linkBrowser and link: 60 min60Results tableResults table: 30 min30
Source: Test plan on this page (240 minutes, about half a working day)

Step 2: scan with what stands at the gate

The security panel reads the code from a HID scanner, from a USB-COM scanner through the browser, and from a camera. All these paths feed the same recognition rule, so repeat the test on the equipment that security actually uses, and not on the first scanner available.

For each phone make three attempts: at full brightness, at brightness reduced by half, and with power saving switched on. Record whether the scan succeeded on the first attempt.

Step 3: check the size and the printout of the code

The default size of the QR code label is 86 x 54 mm, and the code is not printed smaller than 13 mm. Check on the printout that the code is not covered by film, a fold or a stain. In a test with the phone screen, compare whether the code is displayed in full and with a margin.

The message with the QR code contains a code of 233 x 233 pixels with a link to the plant. Scan such a code from a dozen centimetres and from arm's length, because employees hold their phones differently.

Step 4: check the browser and the link

A code scanned with the camera opens the plant address, and its token is passed to the training screen, which displays the identity confirmation. So check whether the phone's default browser opens the link without an error, without a pop-up block and without a requirement to log in to an app store.

The last element is the screen 'Is it you?': the system shows the first name, last name and company of the code owner, and training starts only after confirmation. The test should reach this screen on every phone in the sample.

How to record the result and what to do with it

The results table has five columns: description of the phone, brightness, film, browser and result. Group the failures by cause, then remove the most common one: change the brightness settings in the instruction for the workforce, replace the film at the gate, or change the scanner. For phones that do not pass the test, prepare a printed label.

The test result can be turned into a sentence for the pilot plan: how many phones in the sample pass the scan on the first attempt and what is done with the rest. The plant measures this figure itself, because it depends on its own workforce and equipment.

Most common causes and quick fixes

Test results usually cluster around a few causes. A dimmed screen is solved by an instruction for the workforce asking for full brightness at the gate. A protective film with a reflective coating requires changing the phone or scanner setting. A code that is too small on the printout improves by keeping the label size at 86 x 54 mm. A browser that blocks the link requires changing the default browser or using a label.

It is worth preparing one page of instructions for the workforce with three sentences: switch on full brightness, hold the phone straight, show the code to the scanner. Attach the instruction to the message with the code or post it at the gate.

Checklist

Video

Frequently asked questions

Does the test require an app on the phones?

No. The code opens in a browser, so the test checks the camera, the screen and the browser, not the installation of an app.

How many phones are enough for the test?

A dozen devices from different groups catch the most common causes. Choose the number to match the variety of equipment in your workforce.

What about phones that do not pass the test?

They receive a printed label with the code or a card issued at reception. In this way the pilot covers all employees.

Run the test together with your IT department

We will provide a test sheet and sample QR codes for printing. Let us arrange a short conversation about the pilot.

Let's talk