Why a refused scan followed by an entry deserves a closer look

When a credential is rejected and someone still walks in seconds later, that pair of events is worth separating from everything else. It is the clearest signal of a person passing on someone else’s entry. Treating it as its own review category turns thousands of routine entrances into a short list a manager can actually check.

A rejection is information, not just a failure

Most denied scans are harmless. An expired membership, a wet reader, a member who forgot to renew. On their own they tell you very little, and nobody has time to read them all.

The pattern changes when the refusal is followed within a few seconds by a successful passage. Now you have two facts sitting next to each other: someone was told no, and the barrier turned anyway. Either that person fixed the problem at the desk, or they walked through behind the next member. An accepted scan only proves a credential worked. It does not prove how many bodies moved through the lane. That count is a separate question, and it needs its own answer.

Turning a huge log into a five-minute job

Comparing entrance activity against access events lets the system mark only the mismatches — one scan, two people — and hold the matching footage for a human to look at. Review happens locally. Nobody claims the system knows who the second person is; it only shows that a second person was there.

For an unstaffed club at 05:00, this is the difference between guessing and knowing. The software decides the rule. The physical barrier — a tripod turnstile in a budget-driven site, a speed gate where the entrance carries the brand — is what makes the rule real. Without the mechanical stop, a denied scan is just a note on a screen.