Why returning and destroying are separate matters
Returning a badge is a physical action at reception. Revoking it is an action in the system. One does not replace the other: a returned badge with an active token may end up in the bin, and a copy found there will still work at the gate for as long as the token is active. On the other hand, a revoked token on a badge that someone kept opens nothing.
Reception should therefore treat the return as a signal to revoke, and destroying the printout as an extra layer of privacy protection. Rule one: the system is the source of truth about whether a badge works. Rule two: a printout after a visit has no value, so it is not kept without a reason.
Reception practices step by step
The order is chosen so that the visitor returns the badge on leaving the plant, and revocation does not require an extra visit.
On exit, a scan of the badge at the gate records the exit, and reception collects the printout. When a visitor leaves without a scan, the stay is closed after 12 hours: the check runs every 3 hours. This mechanism closes attendance, but it does not revoke the badge, so reception has to do that separately.
- collect the badge at the exit and record the time,
- revoke the token in the system if the visit will not be repeated in the coming days,
- destroy the printout in a shredder or in a confidential waste container,
- do not put badges into a shared bin in the break room,
- for a multi-day visit, leave the badge active and review it every day.
Time thresholds for closing a stay
Revocation does not overwrite the history
Revoking a badge does not overwrite the old row. The system issues a new token, and the old one stays in the history as revoked. For reception this has two practical consequences. First, the next visit of the same person gets a new code, so an old printout has no value. Second, if an auditor asks, it is possible to reconstruct which token was valid on the day of an event.
The invariant "at most one active badge per person" is enforced by a transaction with a row lock when a badge is issued. Reception therefore does not need to check by hand whether a visitor has a second active badge. It is enough not to bypass the panel when issuing.
The first print issues a new badge
The first print of a label for a person without a badge automatically issues a new badge and records the fact of printing. This streamlines returns: a visitor who comes back after a week does not need a separate request, because the print itself creates a new token. Reception should only remember that the previous token had to be revoked earlier or at the moment a new one is issued.
A copy of the printout kept by a visitor as a souvenir is not a risk if the token has been revoked. A scan of such a copy ends with the message "unknown code", just like a scan of a code that never existed.
Register and control during the shift
At the end of a shift the reception manager should compare the list of issued badges with the list of returned ones. The difference is badges to revoke or to be explained with the person who invited the visitor. It is worth setting a fixed time for this check, so that it is not done in passing alongside other tasks.
If the plant issues many badges in one day, a simple rule helps: all badges from that day that have not returned to reception by the end of the shift are revoked at a set time. A new visit then starts with a new badge.
Checklist
Video
Frequently asked questions
Is it enough to destroy the printout?
No. Destroying the printout protects privacy, but the system decides whether the code is valid. The token has to be revoked in the panel.
What about a visitor who leaves without a scan?
After 12 hours of stay the system closes the person automatically, and the check runs every 3 hours. The badge has to be revoked separately.
Can a visitor keep the badge as a souvenir?
Only after the token has been revoked. A scan of such a copy gives the message "unknown code", the same as for a code that never existed.
Let's tidy up the circulation of badges
We will go through the whole circulation with your reception desk, from issue to destruction. Book a conversation with the InnerWeb team.
Let's talk