InnerWeb
Skip to main content

FAQ: anti-passback and time zones at a production plant

Anti-passback and time zones are rules of the access control system, not functions of occupational safety software. Security and IT managers usually ask the same questions: who blocks a second entry, what must be installed at the gate and how this fits with attendance records. Below are the answers in the order they come up at meetings before the rules are switched on.

3
anti-passback variants: hard, soft, time-based
Source: general AC industry knowledge
5 s
window for ignoring a repeated scan at the security post
Source: InnerWeb feature documentation
2,000+
swipes per working day with several staffing agencies
Source: assumption from 2025-2026 deployments

Does InnerWeb block a second entry on the same badge?

No. Anti-passback is a rule of the controllers and the software of the access control (AC) system, which is where the decision to open the door or gate is made. InnerWeb is a software vendor, not a reader manufacturer. It integrates with the client's existing AC system and works alongside it as an independent supplementary system, together with time recording, HR and ERP.

The practical conclusion: if you want to block a second entry, you configure it in the AC system and in the controllers at the passage. InnerWeb's role starts after the swipe: the badge event reaches InnerWeb through a webhook, where it is linked to training, qualifications, permits and attendance. We therefore do not promise that the occupational safety system itself will stop a person using someone else's badge at the gate.

How do hard, soft and time-based anti-passback differ?

The rule variants differ in what the system does after it detects a repeated entry. Choosing a variant is a security decision, because it changes the consequences for people standing at the gate, not only the entry in the log.

For a plant with a first shift starting at 6:00 and heavy foot traffic, the soft variant at the start is usually the safer choice: it produces a report without blocking the queue.

  • Hard: the controller does not open the passage until the badge has a registered exit. It gives the highest control, but every direction error stops a person at the gate.
  • Soft: entry is allowed and the violation goes to a report. Suitable for a trial period and for zones with low risk.
  • Time-based: the badge returns to circulation after a set time, even without an exit. It limits the effects of a forgotten exit swipe, but weakens control during that time window.

Time limits in the described integration

Time limits in the described integrationHorizontal bar chart: maximum stay 12 hours, check-out task cycle 3 hours.02.557.51012.5hoursMaximum stay before automaticcheck-outMaximum stay before automatic check-out: 12 hours12Check-out task cycleCheck-out task cycle: 3 hours3
Source: InnerWeb feature documentation (AC integration, entry records)

What must be at the passage for anti-passback to work at all?

The rule needs a direction. Readers on both sides of the passage must report direction as entry or exit, and each direction should be a separate point in the AC system. Without this the controller does not know whether an event is an entry or an exit, and anti-passback has nothing to work on.

The most common trap is an exit without a reader: a gate opened by a button or a one-way turnstile. The badge then registers no exit, so after one shift the user becomes a violator without doing anything wrong. Before switching on the hard variant, check all exits, including emergency exits that are in practice used as shortcuts.

Time zones: what to put in the schedule and what not to?

A time zone in the AC system defines the hours and days when a group of badges may access a given passage. For a three-shift plant you describe the shift entry windows, breaks and peak hours, and outside the window the badge is rejected or goes into an exception waiting for approval by security.

An access schedule does not replace a work permit or a training decision. The zone says when entry is allowed, not whether a person has valid authorisations for the task. These two questions get separate answers: the first comes from the AC system, the second from the entry verdict in InnerWeb, which consists of four components: no missing training, no missing qualifications for hazardous work, a permit or visit for today, and an active account.

How do AC swipes reach InnerWeb and what about direction?

The integration point is the badge swipe webhook: the AC system sends an HTTP POST request to InnerWeb at every swipe, in real time. The call is authenticated with a token with a limited validity period, renewed automatically by the integration. The swipe location field distinguishes reader locations, and events from a location without a template in InnerWeb go to the log and do not trigger a training alarm.

The integration specification assumes that the AC system sends every event with the reader time, the direction (entry or exit) and an event identifier. On this basis the swipes can feed working time records, and the rules for pairing entries and exits and for rejecting duplicates are agreed together with the AC vendor. Readers without direction in the client's AC system are a technical fact on the AC side that must be settled before the start.

How many swipes should you plan for, and what about repeats?

At a plant with several staffing agencies, badge traffic can exceed 2,000 swipes per working day, so the integration must tolerate bursts of events and retries. On the AC side, set up queuing and retrying of sending, and on the receiving side treat a repeated event as normal, not as an emergency.

For scans at the security post a separate rule applies: a double scan of the same code within 5 seconds is ignored on the server side, with no new entry and with a message about a duplicate scan. This protects against a double tap, but it does not replace anti-passback at the gate.

Video

Frequently asked questions

Can anti-passback be switched on without changing the readers?

Yes, if the existing readers are on both sides of the passage and report direction. If an exit has no reader, the rule will generate false violations.

Which variant should we start with?

The soft one. You get a violation report without blocking people at the gate, and after reviewing the passages you decide which zones deserve the hard variant.

Does InnerWeb sell readers for anti-passback?

No. InnerWeb produces software and integrates with the AC system you already have. Readers and controllers remain with the client or the client's AC vendor.

Sources

Let's talk about integrating with your AC system

We will show how swipe events from your existing AC system connect with attendance, training and permits. Book a conversation with the InnerWeb team.

Let's talk