How Does a Turnstile System Work?
What Is a Turnstile System?
Two different things are usually called by the same name. A turnstile is a mechanism: a rotating tripod head, a pair of retracting flaps, a swinging panel, a full-height rotor in a cage. A turnstile system is everything that decides whether that mechanism should move, everything that verifies what happened when it did, and everything that keeps the record afterwards. Two buildings can install identical hardware and end up with entrances that behave nothing alike, because almost all of the behaviour lives in the system rather than in the metal.
That distinction matters more here than it does on a single-building project. A ministry compound, a university, a hospital group, a petrochemical complex at Jubail or Yanbu, these are estates. The entrance at one gate is one of dozens, governed by the same permission set, reported through the same software, and maintained by the same small team covering a long distance between sites. On an estate the question is almost never "which mechanism" and almost always "how does the system behave when something is wrong at a gate nobody is standing at".
This page is about the system. Where the mechanisms differ in detail, it summarises and links to the dedicated explanations of how a tripod turnstile works, how a flap barrier gate works and how a swing barrier works.
How Does a Turnstile System Work?
A turnstile system works in five stages. A person presents a credential, a card, a face or finger, a QR pass, a PIN. A reader captures it and converts it into a digital identifier. A controller decides, testing that identifier against the permission set that applies to this lane, in this direction, at this hour, on this day. If the test passes, the controller releases the mechanism. Sensors then confirm that a single authorised passage actually took place, and the event is written to the log with credential, lane, direction, outcome and timestamp.
Present, capture, decide, release, confirm, record. Everything below is detail beneath those six verbs, and the two that cause the most trouble in practice are the two nobody watches: confirm and record.
The Layers of a Turnstile System
The clearest way to understand a turnstile installation is as a stack of layers, each with one job. A fault at any layer produces a recognisably different symptom, which is why describing the stack properly is also the quickest route to diagnosing an entrance that is behaving oddly, particularly over the telephone, to a site three hundred kilometres away.
The credential layer
The credential is whatever the person carries, or is. Four families are in common use, and most working entrances run more than one at a time.
- Card or RFID: a proximity or smart card, a fob, or a UHF tag for hands-free reading. Quick, familiar and simple to issue and revoke. The weakness is that the card is not the person: it can be handed over at the door.
- Biometric: fingerprint, face, palm vein or iris. Binds the passage to the individual rather than to an object, which is why it is the usual choice where the turnstile event also serves as an attendance record. Read time and tolerance to dust, dry skin, strong sunlight and head coverings vary considerably between reader types, and that variation deserves attention here rather than at handover.
- QR code or mobile credential: a code on a phone screen or a printed pass, or a Bluetooth or NFC credential held in an application. The dominant method for visitors and short-notice contractors, because it can be issued remotely before arrival and expires without anybody having to collect anything back.
- PIN: keypad entry, normally as a second factor beside a card rather than on its own, since a PIN shares the card's weakness and is slower to enter at a busy lane.
The reader layer
The reader converts a presented credential into a digital identifier and passes it onward. It is the layer the user experiences, and it sets the practical speed of a lane far more than the mechanism does. Readers mount on the turnstile pedestal, on a separate post, or on the wall ahead of the lane, and they connect to the controller over Wiegand, OSDP, RS-485 or, increasingly, over IP.
Direction decides how many are needed. A lane controlled in both directions needs a reader at each end; a lane free to exit needs an entry reader plus an exit sensor or request-to-exit input. Settling this early matters because reader cut-outs in a pedestal head are factory work, not a site modification, and a pedestal that arrives at Dhahran with the wrong aperture waits for a replacement rather than a screwdriver.
The turnstile lane controller
The lane controller is the decision board inside the pedestal. It receives the identifier from the reader, evaluates it, drives or releases the mechanism, watches the passage sensors, raises alarms, buffers events and reports upward. On most current systems it also holds a cached copy of the permissions relevant to its lane, so it can decide on its own without asking the server. That property is what allows an entrance to survive a network failure, and it is treated in its own right further down.
The controller is also where local behaviour is configured: how long the mechanism stays released before timing out, what the lane does on a tailgate detection, whether an unauthorised push produces a buzzer or a silent alert at the control room, and how the lane responds to the emergency input.
The access control panel and permission database
Above the lanes sits the central layer, a panel, an on-premises server, or a hosted service, depending on the architecture. This is where the authoritative permission database lives: who exists, what credential each person holds, which doors, gates and lanes they may use, on which days, between which hours, and which access groups they belong to. It is also where logic a single lane cannot perform is resolved, anti-passback being the obvious case, since knowing whether a person is currently inside requires a view of every controlled route at once.
One database governing every route is the whole point of the layer. When a person leaves the organisation, a single revocation closes the office lane, the laboratory door and the vehicle gate together. Where each building keeps its own list, revocation becomes a checklist that somebody eventually forgets to finish, and the credential that outlives the employment is the one nobody can account for during an audit.
The network and management software
Lanes, panels and server are tied together over the building or campus network, commonly Ethernet with Power over Ethernet feeding readers and controllers, sometimes RS-485 trunks in retrofits, often both on an estate that has grown in stages. On top sits the management software, which is where the installation becomes usable: enrolling people, issuing and revoking credentials, building access groups and time schedules, monitoring lanes live, receiving alarms, and producing the reports the system was actually bought for, muster lists, occupancy counts, attendance extracts and exception reports on denied attempts and forced passages.
How Does a Turnstile System Work Step by Step?
| Step | What happens | How it works |
|---|---|---|
| 1 | Person approaches the lane | Presence sensing in the pedestals registers somebody in the approach zone. On some configurations this also wakes the reader or sets the directional indicator. |
| 2 | Credential is presented | A card is tapped, a face or finger is presented to the biometric terminal, a QR pass is held to the scanner, or a PIN is entered. |
| 3 | Reader captures and transmits the identifier | The reader converts the credential into a digital identifier and sends it to the lane controller over Wiegand, OSDP, RS-485 or IP. |
| 4 | Controller evaluates the request | The identifier is tested against the permission set held for that lane: valid credential, permitted lane, permitted direction, permitted time, and any anti-passback or occupancy condition. |
| 5 | Decision is issued | Grant or deny. A denial produces a red indicator, usually a tone, and a logged denied-attempt event. A grant proceeds to release. |
| 6 | Mechanism is released | The controller energises the drive or releases the lock: a tripod head is freed for one rotation, flaps retract, a swing panel opens, a full-height rotor is unlocked. Release is typically well under a second on motorised lanes. |
| 7 | Person passes through | Infrared beam arrays across the lane, or rotation sensing on the mechanism, follow the movement through the passage zone. |
| 8 | Passage is validated | The controller interprets the sensor pattern to establish that one person passed, in the authorised direction. Two bodies, a reversal, or a passage with no grant each produce a different pattern and a corresponding alarm. |
| 9 | Mechanism resets | The lane returns to its normal state. If no passage occurs within the timeout, the release is cancelled and the credential must be presented again, so an authorisation cannot be stored up and used later. |
| 10 | Event is written to the log | Credential, person, lane, direction, outcome and timestamp are recorded locally, then uploaded to the server where they feed reporting, occupancy, attendance and any linked video bookmark. |
Steps 4, 8 and 10 are what make this a system rather than a gate. A mechanism without them is a turnstile you push.
What the controller actually checks
Step 4 is more layered than "is this card on the list". A complete evaluation tests several conditions in sequence, and a failure at any one produces a denial.
| Check | What it establishes |
|---|---|
| Credential is known | The identifier exists in the permission set and has not been deleted. |
| Credential is active | It has not been suspended, reported lost, or passed its validity end date, the usual control for contractors, seasonal staff and temporary assignments. |
| Person is permitted at this lane | The access group the person belongs to includes this lane. A visitor pass may open the reception line and nothing beyond it. |
| Direction is permitted | Some lanes are entry-only or exit-only, and the same credential may be valid one way and not the other. |
| Time schedule allows it | Access groups carry day-and-time windows. A cleaning group may be valid only between defined hours; a contractor group only on working days of a defined shutdown period. |
| Anti-passback state allows it | If the credential is already recorded as inside the zone, a further entry may be refused or flagged, depending on configuration. |
| Additional conditions, where configured | A second credential, a supervisor authorisation, an occupancy limit on the zone beyond, or a valid safety induction or permit record held against the person. |
Which of these are enforced is a configuration decision and varies by software platform. A small administrative office may enforce only the first three. A petrochemical facility may enforce all of them, including refusing a contractor whose site induction expired the previous week, which is a safety control implemented at an entrance rather than a security one.
One Permission Database, Many Buildings
On a single-building project the central layer is a convenience. On a distributed estate it is the reason the project exists. A ministry with offices in several cities, a university with faculties spread across a campus and a teaching hospital attached, an industrial complex with administration, workshops, laboratories and a contractor village, each of these has one workforce and many entrances, and the design question is how one permission set governs all of them without becoming unmanageable.
Access groups, zones and schedules across an estate
The structure that makes this work is simple in principle and easy to get wrong in practice. People are placed in access groups rather than being granted individual permissions. Lanes and doors are gathered into zones. A group is granted a zone, on a schedule. Nobody holds a list of doors; everybody holds a role, and the role carries the doors.
The payoff appears at the moments that matter. A new building at a Riyadh compound is commissioned and its lanes are added to an existing zone, and several thousand people have correct access on the first morning without a single record being edited. A department relocates to Dammam and one group assignment changes. A person resigns and one revocation closes every lane on the estate at once. Where permissions have instead been granted person by person (which is what happens when an estate grows building by building without a structure agreed at the start) none of those operations is a single action, and the database slowly becomes a record of decisions nobody can reconstruct.
Two practical cautions. Keep the group count small enough that a reviewer can read the list and understand it; a hundred groups with overlapping memberships is harder to audit than no structure at all. And decide early whether site-level administrators may create groups themselves, because an estate where each site invents its own structure has a central database in name only.
Contractors and time-limited credentials
Contractor populations are the part of the permission architecture that most often defeats an otherwise sound design, and they are unavoidable on the project types this market runs: shutdown and turnaround crews at a process plant, fit-out teams in a development under construction, seasonal staff supporting the pilgrim movements at Makkah and Madinah, maintenance firms visiting a hospital estate on a rota.
The control that works is the validity end date held against the credential, not a reminder in somebody's calendar. A contractor credential is issued with an expiry, and when the date passes the credential stops working everywhere without anybody doing anything. Where the software supports it, the same record can be made conditional on a current induction or permit, so an expired safety qualification closes the lane rather than producing a conversation at the gate. The useful discipline is to make the default for any non-permanent population a dated credential, so that forgetting produces an expiry rather than an open-ended permission.
The companion discipline is reporting. A monthly exception report listing credentials with no expiry date, credentials unused for ninety days and contractor records still active after their project closed takes a few minutes to read and is the only reliable way to find the accumulation that otherwise builds up quietly across an estate.
Why each lane still decides for itself
A central database raises an obvious worry: if everything depends on one server, what happens at a gate at Yanbu when the link to it fails? The answer on most systems is that nothing happens, because the lane was never asking the server in the first place.
The lane controller holds a cached copy of the permission set that applies to its lane (the credential list, the groups and the schedules) and decides locally in milliseconds. The server is informed afterwards. When a switch fails, a fibre is cut, a server is rebooting or an update is running, the lane continues to grant and deny correctly from its cache, buffers its events, and uploads them when the link returns. Only changes made during the outage are unavailable until synchronisation catches up.
This is a design property, not a law of nature. Some lightweight or cloud-first architectures make the decision centrally and genuinely stop working when the link drops. It is worth confirming during specification that local caching exists, that it is enabled, that the controller's credential capacity covers the estate's population rather than one building's, and that events buffer rather than being discarded when the buffer fills. The failure mode only reveals itself on the day the network goes down, which is exactly the day a queue at a gate cannot wait for a diagnosis.
How Anti-Passback Works
Anti-passback addresses one specific abuse: a single credential used by more than one person. Somebody enters with a card and passes it back out to a colleague, who enters on the same credential. The sensors cannot see this, because both passages look entirely normal. The answer therefore has to come from the system's memory rather than from its eyes.
The system holds a state for every credential: in or out of the controlled zone. Entering flips the state to in. Exiting flips it back to out. If a credential already recorded as in attempts another entry with no exit in between, the system knows the card cannot physically be outside, and acts on that.
Hard, soft and timed anti-passback
| Mode | Behaviour | Typically suited to |
|---|---|---|
| Hard anti-passback | The second entry is refused outright. The person cannot pass until an exit is recorded, which usually means an administrator resetting their state. | Zones where duplicate use must be prevented rather than merely observed, controlled process areas, secure stores, and any zone carrying a live occupancy limit. |
| Soft anti-passback | The second entry is allowed but flagged and logged as a violation for review. | Offices, campuses and public-facing buildings that want the visibility without the risk of stranding people at a lane. |
| Timed anti-passback | The same credential cannot be reused at the same lane within a set interval, after which the state clears itself. | A lighter control that blocks immediate card-passing without requiring complete exit coverage across the zone. |
Why anti-passback fails in practice
Anti-passback is defeated by a single uncontrolled exit route, and this is the commonest reason it is switched off within a month of being switched on. If people can leave through a fire door, a loading bay, a stair discharging into a car park or a side gate that registers no exit, their credentials never flip back to out. They arrive the next morning already recorded as inside, the lane refuses them, a queue forms, and the administrator disables the feature rather than reset six hundred states by hand.
The implication is that anti-passback is a building design decision as much as a software setting. It works where every route in and out of the controlled zone is read in both directions, and it does not work where one is not. That has to be established by walking the perimeter during design and recording which routes are read, not discovered during operation. On an estate the walk has to be repeated per zone, because a boundary that is complete around an administration building is rarely complete around a workshop yard. Where full exit coverage is genuinely impossible, timed or soft anti-passback delivers part of the benefit without the operational failure.
Turnstile Mechanism Types Compared
The system layers described above are broadly the same whichever mechanism sits in the lane. What changes is physical control, throughput, appearance and accessibility. This table is deliberately summary-level; each type has a dedicated page carrying the mechanical detail.
| Type | Mechanism | Anti-tailgating method | Accessibility | Throughput | Typically suited to |
|---|---|---|---|---|---|
| Tripod turnstile | Three arms on a rotating head locked between detents; one authorisation frees one 120-degree rotation | Mechanical, the head physically permits a single rotation per grant | Not wheelchair accessible; needs a separate accessible route | Moderate | Plant and workshop gates, contractor entrances, campuses, stadium perimeters |
| Flap barrier / speed gate | Acrylic or polycarbonate flaps retracting into the pedestals | Sensor-based, infrared arrays detect a second body and the flaps can close against it | Wide-lane variants available for wheelchairs and luggage | High | Corporate lobbies, government reception floors, transport concourses, hotels |
| Swing barrier | A glass or metal panel swinging open about a vertical axis | Sensor-based, with panel width and lane length limiting close-following | Most suitable of the three for wheelchairs, trolleys and luggage; wide lanes are standard | Moderate to high | Hospitals, banks, museums, any entrance needing barrier-free access |
| Full-height turnstile | A floor-to-ceiling rotor in a cage, rotating one segment per authorisation | Physical, the cage geometry makes passing two people together impractical | Not accessible; requires an adjacent accessible gate | Lower | Perimeter fences, unstaffed gates, substations, process plant boundaries |
Selection follows from what the entrance has to do. Where the requirement is to physically restrict passage at an unstaffed perimeter in the middle of a plant, a full-height unit is the answer. Where the requirement is to move several hundred people through a reception floor in twenty minutes while looking like part of the architecture, a speed gate is. Most real entrances use more than one type in the same line.
What Dust and Heat Do to a Turnstile System
Most turnstile lanes in the Kingdom stand indoors, which leads people to assume that the environmental considerations governing an outdoor gate do not apply. On a distributed estate that assumption is wrong often enough to be worth treating properly, because the symptoms it produces look like equipment faults and get diagnosed as equipment faults.
Dust on readers and biometric windows
Fine airborne dust settles on every surface a lobby presents, and the surfaces that matter are the optical ones. A camera window on a face terminal, the platen of a fingerprint sensor and the window of a QR scanner all work on a signal that degrades as the surface films over. The visible consequence is not a failure but a slowdown: reads that take two attempts instead of one. At a lane handling four hundred people in a morning peak, a second attempt on one read in five is the difference between a queue that clears and a queue that grows, and nobody attributes it to a lens because nothing has broken.
The specification response is to choose reader types with the contamination in mind (sealed optical surfaces, card or mobile credentials in the dustiest positions, biometrics where the environment is controlled) and to put reader-window cleaning on its own schedule rather than inside a mechanical service visit that happens twice a year.
Dust on the passage sensor arrays
The passage array is the subsystem dust affects most consequentially, because its failure mode is an alarm rather than a silence. The array works on a signal margin. A film of dust on a lens attenuates the beam until the receiver reads an unbroken beam as broken, and the controller treats that as a body standing in the lane. The lane then refuses to confirm passage and close, or reopens mid-travel, or raises a tailgate alarm against nobody at all.
What follows is predictable and worth naming, because it undoes the installation. Nuisance alarms accumulate, the operator stops trusting the alarm, and somebody reduces the sensitivity to make them stop. The lane is now quiet and no longer detects the tailgating it was bought to detect. The fault was a dirty lens; the outcome is a disabled security function. On an estate where one team covers lanes at several sites, this is the single most useful thing to get into the maintenance routine, because a few minutes with a cloth prevents it and nothing reveals it once it has happened.
Heat, duty rate and the electronics
Summer ambient regularly reaches 45 to 50°C, and entrance equipment experiences more of that than its indoor classification suggests. A reception floor behind a glazed facade carries significant solar gain; a plant gatehouse at Jubail or a site entrance at a development under construction may be barely conditioned; a lane in a semi-open covered approach is effectively outdoors for the purpose of its electronics.
Two consequences matter. Published duty rates for motorised mechanisms are stated at a reference ambient, and the permissible rate falls as ambient rises, so a catalogue figure overstates what a lane will sustain through a July peak at a busy gate. And sustained elevated temperature shortens the life of power supply components and drive electronics long before anything fails outright, which shows up as a lane that needs attention more often than its neighbours without any obvious reason. State the conditions the equipment will actually experience when specifying, rather than relying on a general indoor rating.
Coastal salt and condition-based intervals
Sites along the Red Sea and the Gulf add salt-laden humidity to the dust. At Jeddah, Yanbu, Jubail, Dammam and Al Khobar the air moving through a lobby doorway carries chloride, and it concentrates where the air is coolest and wettest: the pedestal base, where mopping water collects and footwear-borne salt is deposited and redissolved, and the terminations inside it, where humid air gives up moisture on a cool night after a hot day. Corroding terminations produce intermittent faults (a reader that occasionally does not respond, a sensor pair that drops out at the same hour each morning) long before anything looks failed. Stainless fixings of an appropriate grade and deliberate inspection inside the pedestal base are the practical responses, and the grade matters more than the word, because the wrong stainless pits readily in a chloride environment.
The principle running through all of this is that intervals should follow conditions rather than a generic calendar. A lane in a conditioned reception floor inland and a lane at a coastal plant gate do not need the same schedule, and giving them the same one means over-visiting the first and under-visiting the second. Build the schedule from exposure (dust load, proximity to the coast, ambient, traffic) and add a rule that a significant dust event triggers a lens inspection across affected sites outside the normal cycle.
Planning Lane Count and Throughput
Total entrance capacity is straightforward arithmetic: lanes x per-lane rate = people per minute. If a lane handles 25 people per minute and an entrance has four lanes, the entrance handles 100 per minute, or 2,000 in a twenty-minute arrival peak. The arithmetic is not where designs go wrong. The per-lane rate is.
Catalogue throughput figures are measured under ideal conditions: a continuous stream of people, each with a credential already in hand, presenting it cleanly and walking through without hesitation. Real entrances do not behave like that. People arrive in clusters when a lift discharges or a staff bus pulls in. They find the card at the lane rather than before it. They stop to position themselves for a face terminal, or present a finger that needs a second attempt because it is dry or dusty. In practice the per-lane rate is set by credential presentation, not by mechanism speed, and the gap between catalogue and observed figures is routinely large.
The right method is to size from observed peak behaviour. Count what actually arrives in the busiest fifteen or twenty minutes, time how long a real person takes at a real reader with the credential type you intend to use, and calculate from that. On a refurbishment the data is available by standing in the existing entrance with a counter. On a new building it comes from headcount, shift pattern, transport arrival profile and, where the building serves the public, the seasonal pattern, which in parts of this market means designing for a peak that occurs for a few weeks of the year rather than for the daily average.
Two further points apply to any entrance line. Entry and exit peaks are rarely symmetrical, so most entrances use bidirectional lanes reconfigured by schedule, more lanes set to entry in the morning, flipped in the evening. And every entrance needs at least one lane wide enough for a wheelchair, which in practice also carries anyone with luggage, a trolley or a delivery. That wide lane should sit in the main line rather than being a side gate a guard opens on request, and it should be counted as a working lane in the arithmetic, because it is the lane everybody with anything in their hands will choose.
Emergency Egress and the Fire Strategy
A turnstile sits on an escape route, and its behaviour in an emergency is a life-safety matter rather than a security preference. The core decision is fail-safe versus fail-secure. Fail-safe means the lane releases and allows free passage on an emergency signal or a loss of power, flaps and swing panels retract or open and hold, tripod arms drop or the head free-wheels. Fail-secure means the lane stays locked and continues to restrict passage. Both are legitimate; they apply to different routes.
Lanes on a designated escape route in an occupied building are normally fail-safe, which covers the great majority of reception and lobby installations. Fail-secure is applied at perimeter and unoccupied-side positions where an alternative escape route exists and leaving the boundary open is unacceptable, and where a lane is set fail-secure, the escape provision has to come from somewhere else, usually an adjacent gate released on the same signal, and that provision belongs in the same design submission.
The release itself is driven by a hardwired contact from the fire alarm panel into the turnstile controller or lane power supply, normally supplemented by a manual release at the security desk. Three practical requirements follow. The interface must be a genuine hardwired contact rather than a software command travelling over the network, because the network is one of the things that may not be working. It must be tested on every lane as part of scheduled fire drills rather than only at handover. And the lane must revert to normal operation cleanly once the alarm is reset, which is the part that is rarely tested and frequently surprises people.
Which behaviour applies, and to which lanes, is settled with the building's fire strategy and the relevant authority, not selected from a product list. On an estate the determination has to be made per building rather than carried across, because the position that applies to an administration block is not automatically the position that applies to a hospital entrance or a plant gate.
Where Turnstile Systems Are Used in Saudi Arabia
- Government and ministry compounds: reception floors with a formal visitor process ahead of the lane, one permission database spanning several buildings on a site and frequently several sites, and reporting obligations that make the event log as important as the barrier.
- Corporate headquarters and commercial developments: speed gate lines in Riyadh and across the Eastern Province at Dhahran, Al Khobar and Dammam, usually with attendance capture and lift control behind the lane.
- Oil, gas and petrochemical facilities: staff and contractor gates at the industrial cities of Jubail and Yanbu, where induction and permit validity is often enforced at the lane and the contractor population turns over with every shutdown.
- Universities and research campuses: timetable-driven peaks across faculties at Riyadh, Jeddah, Dhahran and Abha, with the lane passage frequently doubling as an attendance record and student, staff and visitor routes separated at the entrance.
- Hospitals and health facilities: wide swing lanes dividing public areas from clinical zones, where trolley and wheelchair movement is the normal case rather than the exception, and where staff, outpatient and visitor flows need separating at the door.
- Pilgrim and seasonal infrastructure: administrative and service buildings supporting the movements at Makkah and Madinah, where the design peak occurs for a short season at a scale with few parallels and the system has to handle a large temporary credential population.
- Ports and logistics facilities: personnel gates at Jeddah Islamic Port and King Abdulaziz Port and at associated logistics estates, where pedestrian and vehicle access are governed from one credential database.
- Giga-project and new development sites: construction-phase workforce entrances and, later, the permanent entrances of the completed buildings, including the mixed-use developments now being delivered at Riyadh, Jeddah and Tabuk.
- Retail and mixed-use buildings: office cores and tenant-only areas behind a public environment, where entrance control starts at the core rather than at the street.
Across these building types the lane is rarely the whole answer. It is the moving part of an entrance that also contains identification, visitor processing, recording and, on some sites, screening stages, and it performs when it is specified as part of that entrance rather than bought on its own. TimeWatch supplies entrance control and access control equipment and is represented in Saudi Arabia through Shuruq Saudi as authorised national distributor for the Kingdom.
Integration With Other Systems
A turnstile system is one of the more heavily integrated elements in a building, because a passage event is useful to several other systems at once.
- Visitor management: a visitor is pre-registered, receives a QR pass before arrival, and that pass is accepted at the reception line for a defined window and location. The host is notified on arrival and the pass expires without anybody collecting anything back.
- Time and attendance: the passage becomes the attendance event. Because the person had to pass the lane to reach their workplace, the record is harder to fabricate than a separate punch at a wall unit, and one presentation serves both purposes. The biometric attendance platform and the entrance control platform are usually the same database rather than two.
- CCTV: cameras overlooking the lanes bookmark footage against each event, so any passage can be reviewed from its log entry rather than by scrubbing a timeline. This is what converts a tailgate alarm from a tone into evidence.
- Lift and destination control: the credential read at the lane calls a lift and allocates a car, or restricts the floors the person may select. It changes the entrance layout, because queueing moves from the lift bank to the lane.
- Screening equipment: walk-through metal detectors and baggage scanners from the inspection and screening range positioned ahead of the lane, so screening completes before the credential check and the turnstile remains the last point rather than the queue point.
- Vehicle gates and parking: the same credential database governs the boom barrier and the pedestrian lane, so one revocation closes both routes and the two sets of events reconcile.
- HR and directory systems: automated provisioning from the personnel record, so joiners are enrolled and leavers revoked without a manual step. On a large estate this is usually the difference between a database that stays accurate and one that does not.
- Fire alarm and building management: the hardwired emergency release, plus occupancy data shared for muster reporting during an evacuation.
Installing and Maintaining Lanes Across an Estate
Installation considerations
- Queue and dispersal space: the line needs clear space in front of it for people to form up and clear space behind it for them to disperse. A line placed too close to a lift lobby or a doorway moves the congestion rather than resolving it.
- Floor preparation and cable routing: pedestals fix to a level, load-bearing floor with conduits arriving in the right position, cast or chased before the stone or tile is laid. Retrofitting conduit into a finished floor is disruptive and often visible.
- Lane count from observed peaks: sized from counted arrival behaviour and realistic presentation times, not from catalogue throughput, and with the seasonal peak included where the building has one.
- Reader type and mounting height: decided early, because pedestal cut-outs are factory work. Face terminal positioning needs to suit the height range of the population and to avoid strong backlighting from a glazed facade, which is a recognition problem rather than a product fault.
- Direction strategy: which lanes are bidirectional, how morning and evening configurations are switched, and who holds authority to override.
- Accessible lane placement: in the main line, counted as a working lane.
- Network and power design: switch capacity, PoE capacity, cable runs within limits, and a UPS sized for a realistic outage duration. Confirm controller caching capacity against the estate population at this stage, not the building population.
- Emergency interface routing: hardwired from the fire panel, with the release path agreed in the fire strategy and the cabling installed accordingly.
- Exit route survey: walk every route out of each controlled zone before committing to anti-passback, and record which ones are read.
- Enrolment logistics: enrolling several thousand biometric templates across an estate takes planning and scheduled time. It is routinely underestimated and it is the usual reason a go-live date slips.
Maintenance at estate scale
- Clean reader surfaces and biometric windows on their own schedule, set by the dust exposure at each position rather than uniformly across the estate.
- Clean and verify alignment of the infrared sensor arrays; dust and knocked-out alignment are the usual cause of nuisance tailgate alarms, and both present identically.
- Inspect inside the pedestal base for corrosion at terminations, glands and fixings, the single most useful preventive check at coastal sites.
- Test the fire alarm release on every lane as part of scheduled fire drills, and confirm normal operation resumes cleanly after reset.
- Verify UPS and battery condition at the stated interval, and prove the entrance behaves as designed with mains removed.
- Confirm every controller is synchronising with the server and that no lane is quietly running on stale cached data, easy to miss at a remote site where nobody has reported a problem.
- Review denied-attempt, tailgate and forced-passage reports per site and compare between sites. A rate that differs sharply from comparable lanes usually indicates a sensor, an alignment or a route people have found around the system.
- Audit the credential database for records with no expiry, long-dormant credentials and contractor records outliving their projects.
- Inspect mechanism operation for smoothness and correct reset, and check pedestal fixings and panel or arm condition for impact damage, which trolleys and luggage cause more often than anybody reports.
- Keep firmware and software at supported versions, and test an update on one lane outside peak hours before rolling it across the estate.
Regulatory and Standards Context in Saudi Arabia
Security and life-safety installations in the Kingdom sit within the framework administered by the General Directorate of Civil Defense, the authority concerned with fire and life-safety arrangements on occupied premises. For a turnstile system the relevant questions are the ones raised above: whether a lane line forms part of a designated escape route, how the lanes behave on a fire alarm signal, how the interface to the alarm system is arranged, and how it is tested. On a building serving the public (a ministry office, a hospital, a university, a mixed-use development) those questions belong at design stage, while the lane layout and the emergency behaviour are both still open.
On the equipment side, specifications in the Kingdom commonly reference standards published by SASO (the Saudi Standards, Metrology and Quality Organization) and by GSO (the GCC Standardization Organization), along with the conformity and product-registration arrangements SASO administers for goods placed on the Saudi market. Large clients (government bodies, health authorities, universities and major developers) also publish their own technical specifications, which frequently go further than the general framework in areas such as accessibility provision, finish and operating environment.
Two points should be stated plainly. Nothing on this page should be read as a statement that any particular product is approved, certified or compliant under any of these frameworks: this section is context, not a claim, and conformity status is a property of a specific model and a specific supply, evidenced by documentation for that supply. And current requirements must be confirmed with the relevant authority for the specific project, because they change over time and vary by building type. The position applying to a plant gate, a hospital entrance and a ministry reception floor is not the same position.
Benefits and Limitations
Benefits
- Every passage is decided against a central permission set and recorded with credential, lane, direction, outcome and time, producing an audit trail manual checking cannot match.
- One database governs every controlled route across the estate, so a single revocation closes them all at once and a single group change moves a department.
- Dated credentials make contractor and temporary populations expire by themselves rather than by somebody remembering.
- Accurate live occupancy, which supports muster reporting during an evacuation and capacity management day to day.
- Attendance capture without a separate device or a second action by the user.
- Reduces the routine load on reception and security staff, who move from checking everybody to handling the exceptions the system raises.
- Continues to operate correctly through a network or server outage where local caching is properly configured, which matters most at the remote sites nobody is standing at.
Limitations and considerations
- A turnstile manages and records passage; it does not physically restrain a determined person. Waist-height lanes can be climbed or vaulted. The security value comes from the alarm the attempt raises, the video bookmarked against it and the response procedure behind them. An installation where nobody answers the alarm has bought a queue manager rather than a security control.
- Anti-passback depends on complete exit coverage and fails as a feature wherever an uncontrolled exit route exists.
- Throughput is limited by credential presentation, so the observed rate sits below the catalogue figure and the design has to allow for that.
- Tailgating detection involves a trade-off between nuisance alarms and missed events, and the setting needs tuning against real behaviour rather than being left at a default.
- Dust and heat act on the system quietly (through degraded reads, attenuated sensor beams and shortened electronics life) and the usual outcome is a security function disabled to stop the symptoms rather than a fault anybody records.
- The system depends on power, and the required run time has to be decided and provided for rather than assumed.
- Enrolment and administration are continuing work. A database nobody maintains degrades into a list of credentials nobody can account for.
- Space and structure constrain what is possible, particularly in retrofits into finished reception floors.
Exact behaviour (decision logic, caching capacity, sensor configuration, throughput, emergency release and integration options) depends on the specific mechanism, controller, software platform and site configuration. Figures should always be confirmed against the datasheet and software documentation for the equipment being specified.
Frequently Asked Questions
How does a turnstile system know who you are?
It does not, by itself. A reader captures a credential (a card, a face or finger, a QR pass or a PIN) and converts it into a digital identifier. The lane controller tests that identifier against the permission set held for that lane and decides whether to release the mechanism. The identity lives in the access control database, not in the turnstile.
What is anti-passback, and why does it get switched off?
Anti-passback stops one credential being used by more than one person by recording whether each credential is currently in or out of a zone and refusing or flagging a second entry with no exit in between. It gets switched off because a single uncontrolled exit route defeats it: if people leave through a door that records no exit, their credentials stay stuck inside and the lane refuses them the next morning.
Does a turnstile keep working if the network or the server goes down?
On most systems, yes. The lane controller holds a cached copy of the permissions for its lane, decides locally in milliseconds and buffers events until the link returns. Only changes made during the outage are unavailable. This is a design property rather than a universal one, so local caching, its credential capacity and its event buffering should be confirmed during specification rather than assumed.
Can one access control system govern turnstiles in several buildings?
Yes, and that is the usual reason a central platform is specified. People are placed in access groups, lanes and doors are gathered into zones, and a group is granted a zone on a schedule. A new building is added to an existing zone and several thousand people have correct access immediately, while one revocation closes every lane across the estate at once.
How are contractors given access for a limited period?
Through a validity end date held against the credential rather than a reminder in somebody's calendar. The credential simply stops working everywhere when the date passes. Where the software supports it, the same record can be made conditional on a current induction or permit, so an expired safety qualification closes the lane instead of producing a discussion at the gate.
How many turnstile lanes does an entrance need?
Multiply the number of lanes by a realistic per-lane rate and compare it with arrivals in the busiest fifteen to twenty minutes. Count the actual peak where an existing entrance can be observed, or derive it from headcount, shift pattern and transport arrivals on a new building. Include at least one accessible wide lane and count it as a working lane, because it carries anyone with luggage or a trolley.
How does a turnstile system detect tailgating?
Infrared beam arrays across the lane break and restore in a sequence as a person walks through, and the controller reads that sequence as a passage signature. One body produces a recognisable pattern; a second person following on the same authorisation produces a different one. Rotating mechanisms can also count detents to confirm a single rotation. Sensitivity is configurable and trades nuisance alarms against missed events.
Why do turnstile lanes raise alarms when nobody is in the lane?
Usually because dust has settled on the infrared beam lenses. The array works on a signal margin, and a film on a lens attenuates the beam until the receiver reads it as broken, which the controller treats as a body standing in the lane. The result is a tailgate or obstruction alarm against nobody. Lens cleaning and alignment checking resolve it far more often than electronics replacement does.
How often should turnstile readers and sensors be cleaned on a Saudi site?
Set the interval from conditions rather than from a generic calendar. A lane in a conditioned reception floor inland and a lane at a coastal plant gate need different schedules, so build the frequency from dust exposure, proximity to the coast, ambient temperature and traffic. Add a rule that a significant dust event triggers a lens inspection across affected sites outside the normal cycle.
What happens to turnstiles during a fire alarm?
Lanes on a designated escape route are normally configured fail-safe, so a hardwired contact from the fire alarm panel releases them for free passage. Lanes at a perimeter may be fail-secure where an alternative escape route exists. Which behaviour applies is settled with the building fire strategy and the relevant authority rather than selected from a product list, and it must be determined per building.
What standards and approvals apply to entrance control in Saudi Arabia?
Life-safety behaviour on occupied premises falls within the framework of the General Directorate of Civil Defense, and equipment specifications commonly reference standards published by SASO, the Saudi Standards, Metrology and Quality Organization, and by GSO, the GCC Standardization Organization. Large clients frequently add their own technical specifications. Because requirements change and vary by building type, the current position must be confirmed with the relevant authority for the specific project.
