How the system counts entry, exit and refusal
The starting rule is simple: the first scan with a green verdict records an entry, the second records an exit, and a scan with a red verdict records a refusal, which does not count as attendance on the premises. This rule creates a problem: two scans in a row could be read as an entry followed immediately by an exit.
Before you start settling duplicates, establish which scan you mean. Scans at the security post or the reception desk and swipes from the AC readers are two different event streams with different rules.
Case 1: a double tap within seconds
A double scan of the same code within 5 seconds is ignored on the server side: no new entry is recorded, and a message about a duplicate scan is shown. Security sees that the first scan was accepted and the second rejected as a repeat, so it does not treat it as an exit.
Settling this requires no manual work: a duplicate does not create an entry to correct. The administrator should only check the log if repeats are unusually frequent, which usually points to a weak reader or a QR code displayed on a screen that reflects light.
Time windows of the repeat scan rules
Case 2: tailgating and several people on one badge
Tailgating means several people entering on one swipe. Deduplication on the InnerWeb side will not detect it, because the second swipe never happens. It is limited by the AC rules: turnstiles, anti-passback and security observation. InnerWeb does not implement anti-passback, so we do not promise to stop an entry on someone else's badge.
What you can do on the data side: compare the number of people on the list with their locations on the map and on the evacuation list. A badge swipe only says that someone passed a point, not where they are after passing it. Linking it with location is the added value of InnerWeb and lets you notice that someone is on the premises without an entry record.
Case 3: a rescan after group training
After a group training session at the reception desk, a further scan within 13 minutes is treated as confirmation of attendance, not as an exit. This solves a common problem: the group finishes the briefing, and the instructor scans them again to confirm that everyone is present. Without this exception every such scan would close the visit.
The practical consequence: the 13-minute window applies only after group training. If someone really leaves after a short training, for example because of feeling unwell, security must record it, because a scan within that time does not close the entry.
Settling with heavy traffic and series of events
At a plant with several staffing agencies, badge traffic can exceed 2,000 swipes per working day, so the webhook must tolerate bursts of events and repeats. We recommend that the AC system retries sending after an error, and that the receiver accepts repeated events safely, because retries after a network failure look like duplicates.
The integration with the AC system is described as specification requirements: the AC system sends events in real time, with the event time read from the reader, the direction (entry or exit) and an event identifier, and InnerWeb receives them through an authenticated webhook. The event identifier allows a repeated send after a network failure to be recognised safely, and the reader time distinguishes a double tap from two independent swipes. The pairing rules for entries and exits and for rejecting duplicates are set in the specification together with the AC vendor. If the readers in the client's AC system do not distinguish direction, this is a technical fact on the AC side and must be taken into account in that specification; until it is agreed, settle duplicates by the time and place of the swipe.
- An event within the 5-second window from the same code: ignore, no correction.
- A scan after group training up to 13 minutes: attendance confirmation.
- No exit swipe: exception queue or automatic check-out after 12 hours.
- Suspected tailgating: a security report and a comparison with the location on the map.
Video
Frequently asked questions
Does a second scan always mean an exit?
No. A duplicate within 5 seconds is ignored, and after group training a scan within 13 minutes is an attendance confirmation.
Will InnerWeb stop two people entering on one badge?
No. That is a task for the AC rules and gates. InnerWeb compares the data with the location and the list of people on the premises.
What about a swipe without direction in the AC system?
If the reader in the AC system does not distinguish direction, this is a limitation on the AC side. The integration requirements assume events with reader time, direction and identifier, and the pairing rules for entries and exits are set in the specification with the AC vendor.
Put the attendance list in order
We will show how scans from the gate and the reception desk combine into one list of people on the premises. Write to the InnerWeb team.
Let's talk