InnerWeb
Skip to main content

Replacing and revoking QR code badges: good practices

A lost badge, one passed to a colleague or left in a car is an everyday problem at every gate. Good practice does not mean searching for the badge; it means making it stop working quickly and issuing a new one without losing history. We describe how this works in the system and how to set up a procedure for security.

64 characters
length of the token in the QR code
Source: feature card
32 bytes
randomness of the token
Source: feature card

Basic rule: revoke, do not search

When a badge goes missing, security should not start by asking where it is. It should start by revoking it. Revoking issues the person a new token, and the old row stays in the history. The old code stops working at the gate, so a badge found by someone else does not open the entry, and the trace of past entries remains for investigation.

This model is safer than deleting the code, because it does not destroy evidence. During an audit or an incident it is possible to reconstruct which code was active at a given moment and who printed it last.

Why the code cannot be guessed or checked

The QR code on the label encodes an address with a random 64-character hexadecimal token, that is 32 random bytes. It is never a sequential number, an identifier or a date, so nobody can derive one code from another.

The public code address redirects without checking the token and does not reveal whether the token is valid, revoked or invented. A person who finds a badge or tries to guess does not learn anything about the state of the code. The check happens only at the gate and in the security panel.

Good practices step by step

The procedure below is short enough for a guard to remember during a shift.

Lost badge

Security identifies the person, revokes the badge and prints a new one. Only the administrator or security can print the label after logging in, so the person cannot print one for themselves. The new label has a different token from the old one.

Badge passed on to another person

A badge is linked to a specific person, with their first name, last name and company. When security finds that the code has been used by someone else, it revokes it and documents the incident. The data on the label helps compare the face with the name already at the gate.

Simple reprint

When a label is only damaged and the badge has not been compromised, a reprint is enough. A reprint does not change the token; it only updates the record of who printed last and when. Distinguishing a replacement from a reprint is the guard's most important decision.

What to write into the rules

The entry rules should say one thing: a lost badge is reported immediately, and security has the right to revoke it without discussion. It is worth adding that issuing a new badge is not a penalty but a security measure, so guests and external companies report losses without fear.

It is also good to decide who is authorised to revoke at night or at weekends. The administrator or security role in the system should cover all shifts, not only the day shift.

Checklist

Video

Frequently asked questions

After revocation, can the old code still be scanned?

The scanner will read it, but the gate will reject it as revoked. The public code address does not reveal its state to outsiders.

Do we lose the entry history after a replacement?

No. The old row stays in the history, and the new token is added.

Can someone guess a working code?

Practically not. The token has 64 hexadecimal characters from 32 random bytes, and the code address does not reveal whether a guessed token exists.

Who can print a new label?

The administrator or security role after logging in.

Set up a procedure for your security team

We will show the security panel with badge revocation and print history. Book a call with InnerWeb.

Let's talk