InnerWeb
Skip to main content

Private phone as a QR carrier for contractors: a pilot case

A corrugated packaging plant wanted contractors to enter the site with a QR code in their own phone, instead of a badge issued at every visit. The security manager tested this in a pilot next to the existing cards. Below we describe what changed in the gate process and what stayed the same.

256 bits
length of the random token in the QR code
Source: InnerWeb function documentation
5 s
window for ignoring a repeated scan by the same person
Source: InnerWeb function documentation

Starting point: a badge issued at every visit

The plant worked in a typical setup: the contractor reported to the gatehouse, security checked the invitation and issued a badge with a code. After the visit the badge had to be returned, and some were never brought back. With several dozen people a day, this handling took time from both sides and created a queue at the gate during shift changes.

The security manager asked a specific question: could the same code that had been printed on the label go to the phone of the person entering, if no card readers were replaced and no app was installed. The problem concerned the concept of a packaging plant, not a new identification technology.

What was done: the code in a message instead of on a label

The QR code in the InnerWeb system takes the form of an address with a random token 64 hexadecimal characters long, that is 256 bits, generated by a random number generator. The token is not derived from a person's number, identifier or date, so it cannot be guessed or calculated from outside data.

In the pilot, the contractor received the same code in an e-mail, and when there was no address but a phone number, in an SMS with a link. The code opens in the phone's browser, so nobody had to install a mobile app. At the gate, security scanned the phone screen with the same scanner it had previously used for labels.

One code, four uses

The same code serves the gate, the invitation e-mail, field inspection and training login. For the contractor this means one image to show instead of several: the same picture on the phone works at the gate and at the training tablet.

No card reader replacement

A plant with an access control system can introduce the QR code in the phone next to the supplier's KD cards, without replacing readers. InnerWeb is a software producer, not a maker of readers or cards, so it did not touch the gate infrastructure: the cards kept working and the phone was a second path.

Changes in the gate process

The most important change concerned the moment the contractor receives the code. The message with the code goes out only when the person has passed the required trainings. Permits, the visit itself and the health declaration do not block sending, so security does not see people who got the code before training and do not meet the entry condition.

Second change: the code is sent once per person. The guarantee comes from an atomic column in the database, not from the order of calls of several triggers, so the contractor does not receive three identical messages from three events. Third: the message has a subject in the recipient's language, including Polish and German, the first name in the greeting and the registration date, which reduces the number of questions to the gatehouse.

  • The code goes out after the required trainings are passed, not after the invitation alone.
  • One message per person, regardless of the number of triggers.
  • E-mail or SMS with a link, depending on the channel the person has.
  • No channel at all: nothing is sent and the person goes to reception.

What stayed the same

A scan on the training tablet does not log the person in by itself. The system shows the first name, last name and company of the code owner, and training starts only after confirming with the button 'Is this you?'. This solves the screenshot problem: even a copied code is not enough when the person at the tablet is not the one whose data is shown.

The recognition of the scanned string follows one rule on the server side, shared with the gate. The browser does not parse the code, so two versions of recognition logic that could drift apart do not arise. A repeated scan of the same person within 5 seconds does not create a new entry event, which protects the record from duplicates when the phone is held up twice.

Conclusions for the security manager

First conclusion: the pilot is best run in parallel with the cards, not instead of them. A contractor without a charged phone or without signal still goes through the old path, so the gate does not lose throughput. It is worth agreeing in advance with security what the gatekeeper does when the phone does not work, and describing it in the post instructions.

Second conclusion: scan time of the phone must be measured, because a dimmed or cracked screen takes longer than a card. The plant should collect this data itself during the pilot instead of taking assumptions from outside. Third: a private phone requires clear information for the contractor about what data the system processes, namely first name, last name, company and entry events, without access to the content of the phone.

Video

Frequently asked questions

Does the contractor need to install an app?

No. The code opens in the phone's browser at the plant's address, and the scan at the gate is done by security's scanner.

What if the contractor has no e-mail?

If they have a phone number, the code is sent by SMS with a link. If there is no channel at all, nothing is sent and reception handles the person.

Is a copied screenshot enough to enter?

Not at the training tablet: the system shows the owner's data and requires confirmation. At the gate the code can be revoked, and the system issues a new one.

Let us check the QR code in your plant's phone

We will show the pilot next to your existing cards, without replacing readers and without an app. Let's schedule a short call about your gate and trainings.

Let's talk