InnerWeb
Skip to main content

Anti-passback violation report: best practices

The anti-passback violation report is useful only when a security officer can tell a borrowed card from a reader fault. Below are practices for reading the report: violation patterns, control questions and the role of InnerWeb, which adds the context of entry, refusal and location.

5 seconds
window for ignoring a double scan on the server side
Source: unit card
12 hours
stay limit before automatic checkout
Source: unit card

What the report really says

Anti-passback is a rule of the access control system that does not allow the same card to be used for a second entry without a registered exit. A violation report is therefore a record of a situation in which the system saw a second entry without an exit. It does not say why it happened.

The same line in the report can mean three different things: a person who lent their card to a colleague, a person who left through a gate without an exit reader, or a reader fault that did not record the direction. Resolving it requires additional data.

Violation patterns and their causes

Anti-passback occurs in variants: hard blocks entry, soft records an entry without blocking, timed releases the card after a set time. In soft mode the report is the only tool, so it is worth learning to read the patterns.

Borrowed card pattern

The same card enters in two places in an interval that is physically impossible to cover, or enters through one gate when, according to the report, the person is already inside. Repetition for the same person strengthens the hypothesis.

Reader fault pattern

Violations concentrated on one reader, for many different people, in a short time. If the same reader generates violations for ten people on a shift, the problem lies in the hardware or in the direction configuration, not in people.

Gate without an exit reader pattern

Violations always appear at the start of the next shift and concern people who left through one particular gate. This is an error in the description of passages, which is corrected on the access control side.

Example split of 40 violations per day by cause

Example split of 40 violations per day by causePie chart: example split of 40 violations into passage description error 16, reader fault 10, human error 12 and suspected misuse 2Passage description error: 16 events (40%)Reader fault: 10 events (25%)Human error: 12 events (30%)Suspected misuse: 2 events (5%)40eventsPassage description error16 events (40%)Reader fault10 events (25%)Human error12 events (30%)Suspected misuse2 events (5%)
Source: Example calculation: assumed split of 40 events per day; each plant should measure its own

Control questions before resolving

The security officer should go through the same questions for each violation. A fixed pattern shortens the time to resolve and reduces disputes with employees.

  • Is the violation single, or does it repeat for this person
  • Does the same reader give violations for many people
  • Does every passage have a reader in both directions
  • Was there a fault or power interruption at that time
  • Where was the person according to location

What InnerWeb adds to the resolution

A card swipe in the access control system only says that a person passed a point, not where they are afterwards. Linking it with the location on the map and the evacuation list is the added value of InnerWeb. When the access control report shows the entry of a person who according to the map has been in the hall for an hour, the borrowed card hypothesis weakens and the reader fault hypothesis grows.

In the security panel the first scan with a green verdict records an entry, the second an exit, and a scan with a red verdict records a refusal that is not counted as presence. A double scan of the same code within 5 seconds is ignored on the server side. As a result part of the false violations, arising from a nervous double tap, never reach the InnerWeb register.

The boundary must be kept in mind: the anti-passback report is created in the access control system, and InnerWeb is an independent complementary system. It does not replace the access control report, it only helps to interpret it.

Resolution and recording of the decision

Each resolution should end in one of a few categories: equipment fault, passage description error, human error without bad intent, suspected misuse. Only the last category goes further to the supervisor and HR.

A person staying on site longer than 12 hours is checked out automatically, and the entry is marked as automatically closed. Such an entry is not a violation by the employee, and the officer should distinguish it from other entries.

Checklist

Video

Frequently asked questions

Does InnerWeb generate the anti-passback report?

No. The report is created in the access control system. InnerWeb adds location, the register of entries and refusals, and the context of the verdict.

How do I recognise a reader fault?

Violations concentrate on one reader for many different people in a short time, which points to hardware or direction configuration.

Is automatic checkout a violation?

No. An entry closed automatically after 12 hours is marked separately and should not be treated as misuse.

Sources

Let's combine the access control report with location

We will show how a security officer sees a violation together with location and the entry verdict in one place.

Let's talk