Anti-passback is a rule used in card access control systems that stops a card from being used to enter a second time before it has been used to exit. Its purpose is to prevent someone who has just gone in from passing their card back over the turnstile or fence to the next person, letting several people in on one card.
Set up correctly, it both stops card sharing and gives you a reliable answer to the question "who is inside right now?". This article explains how anti-passback works, the different modes, where it helps and where it causes trouble, and how to set it up step by step. Other guides on doors and cards are in our access control and attendance hub.
How does anti-passback access control work?
The system keeps a location state for every card: "outside" or "inside" (or, in a zoned setup, "in Production", "in Warehouse" and so on). When the card is read at an entry reader, the state flips to "inside"; if the same card is presented for entry again without an exit read in between, the system treats it as a violation. The same logic exposes cloned cards: if the genuine card is inside and its copy is presented at the entry, a violation is logged; we look at this scenario in access card cloning risk.
Two conditions must hold for this to work:
- There must be a reader on both entry and exit. A door that does not record exits cannot enforce anti-passback, because the system never learns that the person has left.
- The perimeter must be closed. If people can leave a zone without presenting a card, through a propped fire door, a loading bay or a side door with no reader, their card stays "inside" and is refused at the next day's entry.
The second condition is where anti-passback projects most often go wrong on site. Map every exit from a zone before switching the rule on in software.
Is anti-passback the same as tailgating prevention?
No. Anti-passback stops the same card being reused. In tailgating no card is used at all: an authorised person badges in and someone else follows before the door closes. That is solved by physical measures rather than a software rule: turnstiles that admit one person at a time, sensors on speed gates, and door-held-open alarms. We compare the options in our turnstile types guide.
On critical doors, IP camera monitoring can be added so that events are verified on video; central camera management with ONVIF makes it easier to match an access event to the footage. The two measures complement each other: the turnstile lets one person through, and anti-passback stops that person's card being handed on.
Anti-passback modes: which one, when?
| Mode | Behaviour | Strength | Watch out for | Best suited to |
|---|---|---|---|---|
| Hard | Refuses the violating entry; the door stays shut | Actually stops card sharing | Needs a closed perimeter; a poor setup locks out legitimate users | Data centres, warehouses, high-risk zones |
| Soft | Allows the entry but logs the violation and raises an alert | Keeps operations moving while collecting data | Deterrence depends on someone reviewing the logs | Transition periods, main entrances, pilots |
| Timed | Will not accept the same card at the same reader for a set period | Needs no exit reader | Makes sharing harder rather than impossible | Car parks, canteens, one-way entrances |
| Zoned (global) | Tracks location across zones and checks the sequence through nested zones | Shows who is where, zone by zone | Needs entry and exit reads at every zone boundary | Factories, hospitals, campuses |
In practice the soundest approach is to start in soft mode, review the violation logs for a few weeks, fix unread exits and process gaps, and only then switch to hard mode where it is genuinely needed. Where door sequence is a contamination rule, we show how hard mode works together with an airlock in cleanroom access control.
What happens when the network drops?
Zoned anti-passback depends on the card's location state being shared between controllers. When a controller loses its link to the server there are two choices: the door keeps working on local rules and location data is reconciled once the link returns, or that door fails safe and refuses entry. Decide in advance, zone by zone, based on risk; otherwise a short network outage turns into a queue at the turnstiles during the morning shift change. We look at this in more detail in our article on access control offline mode.
Anti-passback at vehicle entrances
The same logic applies in parking management systems: a card used to let one vehicle in should not let a second vehicle in before the first has left. Here timed or entry/exit-matched anti-passback is common, designed together with the barrier hardware.
What you lose without anti-passback
Card sharing looks like a minor disciplinary matter, but it undermines two important sets of data.
First, attendance records. If a colleague badges someone in at the start of a shift, the time and attendance record shows a person at work who is not there. Absence is expensive: in the US, productivity losses linked to absenteeism have been estimated to cost employers $225.8 billion a year, or $1,685 per employee (CDC Foundation, press release on worker illness and injury costs, 2015). The figure is American and dates from 2015, but the principle holds everywhere: any gap between the record and reality ends up in payroll.
Second, the "who is inside?" list. In a fire or a gas leak, the people counted at the assembly point have to match the system's "inside" list. If cards are shared or exits are not recorded, the list either shows people who are not there or misses people who are.
According to Türkiye's Social Security Institution (SGK), 766,039 workers insured under Article 4-1/a had a work accident in 2025, and 1,931 died as a result of work accidents. (SGK Statistical Yearbook 2025)
We cover how to get an accurate list in an emergency in our article on the emergency muster list.
Seven steps to a sound setup
- Draw the zones and their boundaries. Mark the gate, production, warehouse, office, server room and the crossing points between them on a floor plan. Our article on zone-based access in factories helps with structuring the zone hierarchy.
- Ensure entry and exit reads at every boundary. List crossing points without an exit reader; either add one or leave that zone out of anti-passback.
- Close or monitor unread exits. Fire doors must stay openable at all times as the regulations require; monitor them with alarms and have them generate a record when opened.
- Choose the mode per zone. For example, soft at the main entrance, hard in critical zones and timed in the car park and canteen (to stop duplicate meal reads).
- Define a reset rule. Returning every card to "outside" at midnight or at the end of a shift stops a single forgotten exit read from locking someone out the next day.
- Write the exception process. Who corrects the record for someone who forgot their card, left through a door during a reader fault or was evacuated, and on what grounds? Every correction should be logged.
- Pilot and review violations. A few weeks of soft-mode logs reveal both genuine card sharing and installation mistakes.
How we set up anti-passback at Digital Bridge
Anti-passback is not a tick box in software; it is a rule designed together with the door hardware, the cabling and your processes. On card access control projects we work in this order:
- Survey and perimeter analysis. We inspect every entry and exit point of each zone on site and map unread exits and fire doors.
- Permission and zone map. We write down with you which mode each zone needs.
- Hardware. We add exit readers, single-person turnstiles or door-held-open alarms where needed, and bring vehicle entrances into the same design with barrier and parking systems.
- Integration. We connect clean attendance data to timesheets and payroll through our HR, payroll and personnel management work.
Because the same team builds the software and the hardware, there is one party responsible if the rule behaves unexpectedly on site. After the needs analysis you receive a written proposal setting out scope, phases and cost.
SmartPass and knowing who is where
The real value anti-passback produces is reliable location data. Our own product, SmartPass, puts that information at the centre of daily operations:
- Zone hierarchy. Zones such as gate, production, warehouse and office are defined as a hierarchy, and permissions are granted per zone.
- Live monitoring and emergencies. Who is inside right now is listed zone by zone, and in an emergency every door can be locked in a single action.
- Rules in plain language. Written as "The production team may enter the Warehouse zone during working hours"; if two rules conflict, the system states clearly which one applies. A rule simulator shows the effect of a rule before it goes live.
- Door, attendance and canteen in one read. The same card read opens the door, creates the attendance record and deducts a meal if one is due; the single-use, time-limited QR code given to a visitor is subject to the same rules.
- Audit trail. Every change, including a manual correction to a record, is logged with its old and new value.
During the survey we agree with you which zones should use anti-passback, and in which mode, based on your existing doors and turnstiles.
Next step
Mark your zones on a floor plan along with every entry and exit point, and note any exits without a reader. Bring that plan when you get in touch, and we will work out with you where anti-passback makes sense and in which mode, and show how SmartPass would run with your own rules.