How to use this checklist
The checklist concerns a rule that works in the controllers and the software of the access control (AC) system, not in InnerWeb. InnerWeb is a software vendor and integrates with the existing AC system; it does not replace readers. InnerWeb's role in this list is limited to receiving swipe events and linking them with attendance.
Go through the list with the security manager at the first gate, with a sheet of paper and photos of the passage. Each point has a clear yes or no answer; a point with a no does not block the start only if it has a described workaround.
Equipment and directions: does the rule have something to work on?
The time zone and shift schedule rules require the readers on both sides of the passage to report direction, entry or exit. This is a precondition without which anti-passback has nothing to work on, and the most common source of false violations after the start.
Also check the exits that nobody planned as exits: delivery gates, a door to a smoking area, emergency doors used every day. If people leave without a swipe, the rule will block their return.
Sample split of checklist points (illustration)
Rule variant, exceptions and the report path
Anti-passback exists in variants: hard (entry blocked), soft (entry logged in a report without blocking) and time-based (the badge returns to circulation after a set time). At the first gate start with the soft variant and review the report after a week, before you decide on the hard one.
Exceptions must have an owner and an end date, for example permissions for groups that do not swipe out, such as delivery drivers. The report path means deciding who reads the violation report, how often, and what they do about repeat offenders, and what happens to groups affected by a configuration error.
Link with InnerWeb and the attendance records
The integration point is the badge swipe webhook (an HTTP POST request at every swipe) with a token of limited validity, renewed automatically by the integration. The integration specification requires the AC system to send events in real time, with the event time from the reader, the direction entry or exit and an event identifier. Agree the rules for pairing entries and exits and for rejecting duplicates with the AC vendor.
A person who stays on the premises for longer than 12 hours is checked out automatically, and the task runs every 3 hours. For anti-passback this means that after an automatic check-out InnerWeb does not release the badge in the AC system: the release is governed by the controller rules.
Test on a pilot group and communication
Before starting for the whole workforce, switch the rule on for a pilot group, for example the maintenance department, and observe it for a week. Collect the number of violations per day, their causes and the security response time. Tell people what will change: that after entering the badge must be swiped at the exit, and that the soft variant will not stop anyone.
When changing to the hard variant, appoint a person with authority to release a badge manually on every shift, including the night shift.
Checklist
Video
Frequently asked questions
Can anti-passback be switched on at all gates at the same time?
It can, but it is better to start with one gate in the soft variant. The first week's report will show direction errors before they reach the whole workforce.
Does InnerWeb release a blocked badge in the AC system?
No. Releasing a badge is a function of the controllers and the AC software. InnerWeb receives swipe events and links them with attendance.
Who should read the violation report?
One named person from security, at a fixed rhythm. A report without an owner grows and stops being read.
Let's go through the list together
The InnerWeb team will help connect events from your AC system with attendance and the report. Book a conversation before the start of the first gate.
Let's talk