Protect & respond · Feature guide

CCTV tailgating detection for access control

When two people pass through an entrance close together, a camera can flag the movement for review. To determine whether the second entry was unauthorised, your team may need to compare the video with access-control events. Counting movement and checking permission are different tasks.

Illustration of two office employees following through one access gate with one card event
AI-generated illustration of tailgating detection. The scene and overlays explain the concept; they are not a PGAK screenshot or measured result.

How it works

Flag people or vehicles crossing a monitored boundary close together.

Where it could help your business

Review closely spaced entries at a controlled office entrance.

Test real entrance behaviour: visitors carrying bags, staff holding doors, deliveries and shift changes. Agree how close entries must be to trigger a review. Where possible, show the relevant access event and camera clip together.

What your camera setup needs

Camera events need access-control context to determine authorisation. Close movement alone is not proof of a breach.

Does tailgating detection stop someone entering?

Detection by itself only identifies an event. Physical prevention requires appropriately designed access hardware and a response process.

Check it on your own site

Bring a camera model list and explain the event you want to find or detect. We can use that to scope a compatibility assessment. Ask for a written proposal naming the supported functions, processing hardware, licences and pilot checks before agreeing to an installation.

Check my camera setup →

Calculator · C13

Tailgating detection: estimate it for your site

Use your own measurements. The result is the staff time released, shown separately from any cash, using the formula below. It runs in your browser and nothing is sent anywhere.

Fields start empty. A blank is “not entered”, not zero; type 0 where 0 is true.

Money (optional)

Salary plus benefits and overheads, per working hour. Needed only if you enter a realisation above 0%.

0% unless you can name the mechanism — overtime that stops, a post not refilled, a contract reduced.

Only from your own records. May be negative.

Licences, support, connectivity. Enter 0 if there is none.

Hardware, installation, commissioning. Enter 0 if there is none.

Enter every amount on the same basis — all including GST or all excluding it. Nothing here adds or removes tax. Values are nominal rupees, not discounted.

Result

Enter your own figures, or load the worked example, to see the result.

How it is calculated

hours = events × (old − new) ÷ 60 − exception hours

Worked example (illustrative inputs)

200 events; 3 old; 1 new; 1 exception hour.

staff time released: 5.667 hours a month.

Formula version 1.0.0.

What this does not tell you

  • Hours released are capacity, not cash. They become cash only through a mechanism you state — overtime that stops, a post that is not refilled — entered as the realisation fraction.
  • The 'after' values are your assumptions or pilot measurements. PGAK publishes no effectiveness figure for this feature.
  • Results must not drive automated punishment, pay deductions, access denial or employment decisions. Use requires appropriate notice, a lawful purpose and human review of every exception.

Evidence status: Supplier/integration or marketed capability; PGAK availability and site performance require verification.

Request a site-specific assessment with these assumptions

Your result stays on this page either way. If you want it checked against your cameras and quotation, leave a number; mention the figures on the call. Nothing you typed into the calculator is sent with this form.

Request a camera assessment. Timing and scope agreed on the call. By submitting, you ask PGAK to contact you about this enquiry. Privacy notice.