Speed Gate Tailgating Detection: How Effective Is It?
Essential Security Supplies
Speed gate tailgating detection can identify many attempts by a second person to follow through on one credential, but detection does not automatically prevent entry. Effectiveness depends on the lane's optical or infrared sensor coverage, the spacing and behaviour of pedestrians, the configured alarm or gate response, and whether staff act on alerts. Very close followers, side-by-side users, children and luggage demand particular testing. A witnessed site-specific commissioning test is more useful than an unsupported universal detection percentage.
How effective is speed gate tailgating detection?
For a properly configured lane, a close follower using the same authorisation or a person travelling in the wrong direction may generate an abnormal-passage event. The result is not universal: some installations provide an audible or remote alarm, others attempt a controlled leaf movement when safe, and some rely on a nearby guard. Optical sensing may struggle to distinguish unusual silhouettes, closely grouped people and carried objects. Ask whether the objective is to detect an event, deter an attempt or physically restrict passage. A speed gate alone is not a guaranteed anti-intrusion barrier.
Separate a barrier from a security decision
A speed gate controls pedestrian passage, but it does not guarantee that one credential equals one person. Detection depends on sensor design, lane geometry, user behaviour and configuration. Identify the required response to a second person before choosing equipment; an alarm-only lane provides a different outcome from a supervised entrance with an active guard response. For broader design choices, see pedestrian access control, throughput and anti-tailgating. Anti-passback can help limit credential reuse, but is not a substitute for detecting two people passing on one valid credential.
Ask how the sensors recognise occupancy
Manufacturers may use infrared beams, optical arrays or other occupancy sensing. Request a sequence diagram for closely spaced users, backpacks, children, luggage and people changing direction. Test the exact product and controller firmware where the distinction matters. A marketing phrase such as anti-tailgating is not a substitute for measured detection behaviour.
Sensor acceptance: Record the minimum follower gap tested, and the outcomes for bags, children, side-by-side passage and pauses within the lane. Document missed events and nuisance alarms against the agreed criteria.
Map permitted and prohibited movements
Walk through normal entry, exit, reverse travel, simultaneous opposite movement and an authorised person stopping mid-lane. Confirm what the lane indicates, logs and does in each case. The access control system may approve a credential while the gate controller separately handles lane safety and passage confirmation.
Check throughput and accessibility
Faster passage can increase the challenge of reliably distinguishing closely following users. Review user mix, peak arrivals, mobility aids, deliveries and the need for an accessible alternative. Use the NZ speed gate lane sizing guide to plan clear widths and peak-period flow. Do not configure an overly aggressive response that creates foreseeable contact or blocks a required route.
Decide who receives the alarm
A useful alert specifies lane, direction, time and event type, and reaches someone who can act. Integrating with access control or CCTV may provide context, but each integration must be verified for the exact interfaces. Test alarm routing and operator procedures rather than assuming event logs will be reviewed later.
Alarm acceptance: Record the destination of each event, the responsible operator, the agreed response time and the procedure for CCTV verification or intervention. Test communications faults as well as a successful alarm.
Design for safe evacuation
Determine the site’s approved emergency mode, fire-system interface and any required free passage. The intended response during an alarm may differ from routine anti-tailgating control. Safety and accessibility requirements take precedence over security blocking behaviour. In New Zealand, access-controlled barriers on an escape route may fall within specified system SS 3/2 (access-controlled doors) on a building's compliance schedule. Confirm the applicable classification with the building consent authority and fire engineer, including safe release during fire alarm and power failure. Where SS 3/2 applies, the compliance schedule may require six-monthly inspection by an Independent Qualified Person (IQP); follow the schedule for that particular building.
Commission with repeatable pedestrian scenarios
Agree pass criteria before testing. The matrix below gives example objectives, not a manufacturer's promised detection rate. Record each test's conditions, sensor settings, controller version, alarms and actual results. Repeat with a realistic walking pace and peak-period traffic; higher sensitivity may increase nuisance alarms or reduce throughput.
| Scenario | Expected event or response | Pass criterion to agree |
|---|---|---|
| One authorised pedestrian | Normal single passage, no false alarm | Passage recorded without obstruction |
| Close follower on one credential | Tailgating alarm; safe configured gate response | Alarm reaches operator and is logged |
| Two people side by side | Abnormal occupancy or limitation documented | Observed response meets agreed risk control |
| Adult with child or large wheeled case | Safe passage without hazardous closure | Safety behaviour and nuisance events recorded |
| Reverse or wrong-way travel | Direction or intrusion alert if supported | Correct event, indication and operator routing |
| Fire signal or loss of power | Approved emergency passage behaviour | Matches fire-engineered and manufacturer design |
Worked product selection: The FERN360 SGFHSW-600 full-height swing speed gate is a catalogue option, not evidence of a specific detection percentage. Before specifying it, obtain the current manufacturer's sensor map, passage sequence, controller options and emergency-operation instructions. Verify whether alarm-only, leaf-closing or reverse-direction responses are supported on the exact model, rather than assuming they are universal.
A defensible specification brief
For a New Zealand project, separate confirmed facts from design decisions. Record site identity, operating hours, users, interfaces, exposure conditions, drawings available and the named person who approves the operating sequence. The most expensive later changes often arise from an assumption that was not stated in the brief. The specification should describe the outcome needed while leaving product performance to verified technical documents. A sensible handover starts with a one-page requirement register listing each decision, the approving stakeholder, the evidence needed and the commissioning test that will prove it.
What to request from a supplier
Request the current installation instructions, the exact model and part number, dimensional drawings, controller and power requirements, accessories, firmware or software dependencies where relevant, and maintenance documentation. Confirm which items are supplied and which are separate trades. Ask for written clarification of uncertain compatibility rather than relying on a product photograph or shorthand range name. This matters especially when a project combines equipment from several manufacturers or contains legacy infrastructure that no longer matches the current catalogue.
Design coordination and responsibilities
Agree which contractor owns civils, electrical supply, access-control programming, network changes, mechanical work, safety risk assessment and the final integrated test. Record physical and electrical boundaries between packages. If a design cannot be signed off because a model is not yet selected, mark that dependency as open rather than allowing installation to proceed on assumed dimensions. This discipline helps avoid rework and makes handover defects easier to trace to the responsible scope.
Common mistakes to avoid
Do not order hardware before surveying the actual opening or site. Do not substitute an attractive specification from a neighbouring model. Do not accept a demonstration that tests only the happy path. Do not omit practical service access, weather exposure, emergency operation or an alternative procedure when a controller fails. Most importantly, do not treat a functioning component as proof that the entire integrated system works safely and as intended.
A practical handover record
The handover pack should identify installed models, serial numbers where useful, firmware versions where relevant, as-built cabling and layout, user roles, maintenance instructions and supplier contacts. Include photographs of concealed work before finishes are closed and a schedule of tests with actual results. Record defects and agreed follow-up actions separately from accepted functions. A dated sign-off protects the installer and gives the operator a workable reference for future maintenance and changes.
Commissioning checklist for the installer
- Identify the exact installed model, its documentation and operating configuration.
- Photograph and check the site conditions against the approved drawings.
- Verify power, wiring, mechanical fixings and environmental protection as applicable.
- Test routine operation with a representative pedestrian scenarios.
- Test rejected or unusual inputs, loss of power and relevant emergency functions.
- Confirm fault reporting, operator response, maintenance access and as-built records.
- Record the responsible person and retest any faults before final sign-off.
Related ESSL guide: Speed Gates offers complementary product-range information. Use this article for the installation or troubleshooting decision.
Frequently asked questions
Can speed gates stop tailgating or only detect it?
Speed gates can detect suspicious passage and trigger an alarm or a configured safe gate response. They do not guarantee physical prevention; effectiveness depends on model, settings, lane design and staff response.
Can speed gates detect two people walking side by side?
Some sensor systems may identify abnormal occupancy, but side-by-side passage is a challenging case. Test the exact lane with realistic people and baggage, and record any detection limitations.
How is anti-tailgating different from anti-passback?
Anti-tailgating concerns more than one person passing on a single authorisation. Anti-passback controls how credentials may be reused across readers or zones; it does not itself prove that only one person passed.
What happens to speed gates during a fire alarm?
The approved evacuation strategy and manufacturer configuration determine how gates respond. For New Zealand escape routes, confirm relevant compliance schedule and fire-engineering requirements, and test fire-input and power-loss behaviour on site.
Next step for New Zealand security projects
Prepare the site drawings, equipment schedule, user requirements and unresolved technical questions before requesting a trade specification review from Essential Security Supplies. Confirm the exact current product model and installation documents prior to ordering. This article provides planning guidance; it does not certify a particular installation or make claims about unverified stock, pricing or compatibility.
