Principle: a new code, the old one stops working
Revoking a badge does not overwrite the old entry. The system issues a new code and the old one stops working. A lost phone with the old code therefore becomes useless, and the history of events remains complete for an audit.
The code is a random token, not the employee's number, so the new code does not resemble the previous one and cannot be guessed from it. The employee does not lose their identity in the system: only the carrier changes.
Step 1: report and verify the person
The employee reports the loss to their supervisor, to HR or to security, depending on the plant's rules. The most important thing is a quick confirmation of the identity of the person reporting, because someone who is not the account owner should not revoke another person's code.
The plant sets out in its procedure who may take a report outside working hours. A good practice is a single security duty number, whose holder knows this procedure.
Step 2: revoking the old code
The operator issues a new code in the panel, and the old one loses its validity. From that moment a scan of the old code does not open the passage. If the plant also uses the KD vendor's cards in parallel, their blocking is done in the KD system, so the report covers both carriers.
In the security panel the token is printed only on the physical label and is not returned in the responses of the interface, so the operator does not need to note it down or copy it.
Step 3: issuing the new code
The new code reaches the employee through the same channel the plant already has. The message with the QR code has a subject in the person's language, the first name in the greeting, the registration date and a code of 233 x 233 pixels with a link to the plant. When the employee has no e-mail address but has a phone number, the code is sent by SMS with a link.
If the employee does not yet have a new phone, security prints a label with the code. The default size is 86 x 54 mm, and the code is not printed smaller than 13 mm. A failed send releases the send flag and the queue retries, so the code is not lost silently.
Step 4: the training account stays
The employee's training account is linked to the person, not to the phone. After the new code is issued, the employee logs in to training with the same account, and the system again shows the first name, last name and company with the 'Is it you?' confirmation. Completed training is not lost.
The message with the code is sent only after the required training has been passed, so an employee with a full set of permissions receives a new code without additional induction. The plant does not need to repeat the introduction because of a change of phone.
Evidence for the audit
After the event, record in the log: the date of the report, the person who took it, the time of revoking, the channel for issuing the new code and the time of the first successful scan. These five entries show the auditor that the procedure works and that the lost phone did not leave an open gate.
Pitfalls and good habits
The most common pitfall is blocking the employee's account instead of the code alone. The person then loses access to training and has to wait for it to be assigned again. The procedure should state clearly that the code is revoked and the account stays.
The second pitfall is the lack of a duty person outside working hours: a phone lost after a night shift waits until morning, and the old code still works. The third is forgetting the KD card when the employee has both: the report covers both carriers, and the card is blocked in the vendor's KD system.
A good habit is also to rehearse the procedure once during the pilot on an invented report. In this way HR and security know the order of steps, and the plant has its first piece of evidence for an audit.
Guest and contractor instead of an employee
For a guest or a contractor the procedure is shorter, because the person is registered at reception with only a first name, last name and phone number. After a phone is lost, reception issues a new code, prints a label and records the event. For a guest there is no training account to keep, but for a contractor with completed training it is worth checking that the new code is still linked to their person.
This way the plant has one procedure for all groups, and the differences concern only who takes the report.
Checklist
Video
Frequently asked questions
Does the employee have to repeat training after changing the phone?
No. The training account is linked to the person, and the new code carries the same identity to the training screen.
Can the old code still be scanned?
A scan of the old code does not open the passage, because the system issues a new code and the old one stops working.
Who can revoke a code outside working hours?
The person named in the plant's procedure, for example the security duty officer. The rules for duty are set by the plant together with HR.
Rehearse the procedure with HR and security
We will show the revoking and issuing of a new code on an example plant, and help you write a short procedure into the instructions.
Let's talk