Why a missing exit is a separate problem
Anti-passback makes sure the same card does not enter twice without an exit, but exit records are a separate matter: the list of people on site, time records and evacuation. If an exit was not registered, the person still appears as present, although they left the site long ago.
At a plant with several staffing agencies, card traffic can exceed 2 000 punches per working day, so even a few percent of missing exits produce several dozen wrong entries a day. The integration must catch them, not only record them.
Stage 1: agreeing the scope with the access control vendor
The integrator starts with a conversation with the access control vendor about what data leaves the system with each punch. InnerWeb does not manufacture or replace readers: it integrates with the existing access control system, so everything that is to be visible in InnerWeb must first leave the access control system.
The integration point is the card punch webhook. The access control system sends an HTTP POST request to InnerWeb on every punch, and the call is authenticated with a short-lived token, renewed automatically by the integration.
Sample number of missing exits at 2 000 punches per day
Stage 2: direction on the readers on both sides
The rules for time zones and shift schedules require the readers in both directions of a passage to report the direction, entry or exit. Without this, no system, neither the access control system nor the supplementary one, can establish a missing exit.
The integrator should check every passage on the site plan and confirm that it has an entry reader and an exit reader. Passages with a single reader, with gates opened from the inside by a button, or with an emergency exit generate exits that the access control system does not see.
Stage 3: requirements for events from the access control system
The requirements are worth writing into the integration specification with the access control vendor right at the start. The access control system sends events in real time, with the event time taken from the reader, the passage direction (entry or exit) and an event identifier. InnerWeb receives them through an authenticated webhook and builds the exit records and working time on that basis.
The rules for pairing entries with exits and for rejecting duplicates are set in the specification with the access control vendor: the same event identifier must not be stored twice, and a repeated scan within a few seconds is ignored. The vendor and the integrator approve these rules before go-live, because the reliability of the attendance list depends on them.
The location field distinguishes the locations of the readers. Events from a location without a template in InnerWeb go to the log and do not trigger a training alarm. A health and safety training alarm is raised only for locations that have a template in InnerWeb, and the training requirement can be set for all companies except the listed exceptions.
Until the event integration with the access control system goes live, the exit records in InnerWeb rely on scans at the security panel and at the registration station.
Stage 4: missing exit in InnerWeb and how it is closed
For an internal employee, a day without a recorded exit is marked as a missing exit, and the employee confirms the time themselves. For an external company the default stay limit is 12 hours, and automatic check-out records the exit. A person who remains on site for longer than 12 hours is checked out automatically; the task runs every 3 hours.
A card punch in the access control system only says that a person passed a point, not where the person is after passing it. Linking it with the location on the map and the evacuation list makes it possible to confirm whether a person with a missing exit has actually left the site.
Pitfalls that repeat in deployments
We have collected the typical places where direction integration fails. Each of them is worth checking before the start.
- A gate with one reader and an exit opened by a button
- A reader renamed without informing the integrator
- An integration token without automatic renewal
- Bursts of punches before the start of a shift without a queue
- No direction and no event identifier for each reader in the specification
Video
Frequently asked questions
Do punches from the access control system feed the time records?
Yes, when the access control system sends events with the reader time, the direction and an event identifier. The rules for pairing entries with exits are set in the specification with the access control vendor.
What about a person who did not scan out?
An external company is checked out automatically after 12 hours, and an internal employee receives a missing exit mark and confirms the time themselves.
Does InnerWeb replace the readers?
No. InnerWeb is a software vendor and integrates with the client's existing access control system.
Sources
Let's agree the scope with the access control vendor
We will hold a conversation with the integrator about the passage direction, the event identifier and the rules for pairing entries with exits, which are set in the specification.
Let's talk