InnerWeb
Skip to main content

How to set entry windows for shifts in the ACS: a guide

An entry window is the time range in which the card of a given group opens the passage. A badly chosen window either blocks people at the start of a shift or lets them in at any hour. This guide shows how the ACS administrator and the shift planner define windows for shifts, breaks and peaks in six steps, and how to verify them afterwards on data.

6
steps for setting entry windows
Source: guide based on deployment practice
2,000+
swipes per working day the integration must handle
Source: assumption from 2025-2026 deployments

Before you start: what is in the ACS and what is in InnerWeb

Entry windows are set in the access control system, in the time zones of the controllers. InnerWeb does not produce or replace readers and does not replace the ACS: it integrates with the existing system through the card swipe webhook. On the InnerWeb side, the entry verdict and attendance appear, which are worth keeping consistent with the windows.

You need three documents for the work: current shift rosters from the planner, the list of passages with reader directions, and the list of card groups, for example production, maintenance, agencies, guests. Without these three elements the windows will be guessed.

Steps 1 and 2: shifts and the margin

Step 1: list the shifts with their hours, for example 6:00-14:00, 14:00-22:00 and 22:00-6:00. Step 2: add an entry and exit margin. People arrive before the shift and leave after it, so the window opens earlier and closes later than the shift.

Choose the margin based on real data, not intuition. Take the swipes from one month from your ACS and check how many people enter 10, 20 and 30 minutes before the shift. The first setting usually turns out too narrow for the night shift, because commuting from more distant towns is less predictable.

  • Window opening: shift start minus the entry margin (illustrative example: 30 minutes).
  • Window closing for entries: shift start plus tolerance for lateness.
  • Exit window: until the end of the shift plus the exit margin, and exit is always allowed.

Sample distribution of entries before a shift (illustration)

Sample distribution of entries before a shift (illustration)Illustrative bar chart: 25, 45, 25 and 5 percent of entries in consecutive ranges before the shift start.01020304050% of entries30-20 min before: 25 % of entries2530-20 min before20-10 min before: 45 % of entries4520-10 min before10-0 min before: 25 % of entries2510-0 min beforeAfter start: 5 % of entries5After start
Source: Illustrative data for practice with your own swipes; they do not describe any plant

Steps 3 and 4: breaks and peak hours

Step 3: decide whether a break means leaving the premises. If employees go to a shop or the car park, you need exit and return windows, otherwise the break happens inside and the window does not change. Step 4: assess the peak at the gate. At a passage serving several hundred people per shift, set the window earlier, not wider: an earlier opening spreads the traffic over time.

At passages with queues, do not tighten the rules during peak hours. If a reader rejects a card because of the window, security must have a ready exception path, otherwise people wait in the queue for a decision.

Step 5: reader direction and the link with attendance

The time zone rules and shift schedules require the readers on both sides of the passage to report the direction, entry or exit. Without this you cannot build an anti-passback rule or a reliable attendance list, and the windows cannot distinguish an entry from an exit.

The swipe location field distinguishes reader locations. Events from a location without a template in InnerWeb go to the log and do not trigger a training alarm, so after adding a passage in the ACS, also add it in InnerWeb if you want the training requirement to work there. The training requirement can be set for all companies except the listed exceptions.

Step 6: exceptions and verification on data

Step 6: agree how exceptions are handled: shift swaps, overtime, weekend work. Instead of widening the windows for everyone, create short exceptions for specific people or groups with an expiry date. An exception without an end date is the beginning of a gap in the system.

Verification: after two weeks, compare the number of refusals with the window as the reason against the number of all refusals. If the windows account for more than a small part of refusals, widen the margin. With traffic above 2,000 swipes per working day, the integration must also be resilient to bursts of events and repetitions, so check the logs of the receiver for duplicates during peak hours.

Video

Frequently asked questions

Are the windows set in InnerWeb?

No. Entry windows are set in the ACS. InnerWeb receives swipe events through a webhook and links them with attendance, trainings and permits.

How wide should the window be before a shift?

Set it based on data: check the swipes from one month and see when most people enter. There is no single value for all plants.

What about a swipe at a location that does not exist in InnerWeb?

The event goes to the log and does not trigger a training alarm, so add the new passage in InnerWeb as well.

Sources

Verify the windows on your data

We will help analyse swipes from your ACS and plan entry windows for shifts. Book a meeting with the InnerWeb team.

Let's talk