Starting point: third shift and no HR
The plant runs three shifts and the gate is staffed around the clock by one security guard. At 2:00 an employee from the night shift reports that the card is missing. They do not know whether it was left in the locker room, in the car or dropped on the way. HR and the access control administrator cannot be reached until the morning.
This is an implementation scenario, not a description of a specific event at a client. It shows how the response procedure works when the plant uses an existing access control (KD) system and InnerWeb runs alongside it as a system for attendance, qualifications and permits. InnerWeb is a software producer: it does not make readers or cards, so the physical blocking of the card stays in the KD system, while InnerWeb covers what concerns access and attendance.
Step 1: confirm identity without the card
The guard cannot rely on the employee's statement alone. The first step is to confirm identity with a document bearing a photo and check that the person is on the shift list. Only then does the guard open the loss report.
A workable procedure depends on a clear split of roles: the guard may report the loss and start the block, but may not issue a permanent card. The detailed split between security, HR and IT is described in a separate article on roles in the lost card procedure.
- a document with a photo and a check against the shift list,
- the time and circumstances of the report recorded in the register,
- a question about the last place the card was used, needed for the later review of swipes.
Time windows in the gate path
Step 2: the block and what the gate does with it
The physical block is carried out in the client's KD system. On the InnerWeb side, what matters is that a revoked card stops identifying its former owner: the card lookup at the gate skips cards with a revocation date. If someone finds the card and tries to use it at an entry check based on InnerWeb, the system will not assign the scan to the employee.
A detail important for security: an unknown code and a revoked code both return the same 404 error at the gate. The guard cannot tell from the screen whether a code does not exist or has been withdrawn, and the same rule applies to a person trying to use someone else's code. This is a deliberate limit on information, because a differentiated response would help identify which codes were once valid.
Step 3: temporary access until the end of the shift
The employee must finish the shift, so they need an identifier for those few hours. In the implementation scenario the solution is a temporary badge with a QR code, printed at the gate or in the secretariat. Printing the label for a person who has no badge issues it automatically, and the print page matches the label to the size reported by the printer driver.
One active badge per person applies, enforced by a transaction lock in the application. The badge token is 64 hexadecimal characters, comes from a random generator and is not derived from the person's number or the date, so it cannot be guessed. The full description of the print setting is in the implementation notes on the QR badge from the secretariat.
Step 4: scans in between and protection against error
A scan at the gate is an access control act. A green verdict records an entry or exit, while a red one records a refusal entry, which does not count as presence on the site. The refusal includes the reason and the names of missing trainings or qualifications, so the guard immediately sees whether the problem is the badge itself or an overdue training.
Scanning the same code again is rejected as a duplicate. The server applies a 5-second window and the interface an additional 2584 ms window, which protects against a double record when the scanner reads the label twice. The On-site list refreshes every 13 seconds, so in case of a night evacuation the guard sees who actually entered.
What stays in the records after the report
In the morning the security supervisor and HR receive a complete set: the time of the report, the role of the person who received it, the revocation date and all scans from the night. This is the basis for the review of swipes described in the investigation scenario.
The scale of the phenomenon is small but regular. A sample calculation shows that a plant with 500 employees and an annual loss rate of 3 percent handles 15 events a year, roughly one every 3 to 4 weeks. With events this rare, the procedure must be simple, because the guard will not practise it every day.
Checklist
Video
Frequently asked questions
Can the guard issue a new card themselves?
Not in the described scenario. The guard reports the loss and issues a temporary QR badge, while the permanent card is issued by the role named in the procedure, usually HR or the system administrator.
Why doesn't the gate say that the code is revoked?
An unknown code and a revoked code both return the same 404 error, so nobody can tell a code that never existed from one that was withdrawn.
What if the employee finds the card an hour later?
A card found after the block does not return to use. We describe the rules in the article on a found card after a block.
Let's walk through the night duty procedure
We will show on a demo how the gate records refusals and badges. Book a call about integration with your KD system.
Let's talk