How Does a Turnstile System Work?
What Is a Turnstile System?
Two different things get called by the same name. A turnstile is a mechanism, a swinging panel, a pair of retracting flaps, a rotating tripod head, a full-height rotor. 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 towers can install identical lanes and end up with entrances that behave nothing alike, because nearly all of the behaviour lives in the system rather than the hardware.
In this market the distinction has a very specific edge. The glass line in a Business Bay or Dubai Marina lobby looks like a single installation, and physically it is. Behind it, one entrance may be serving forty tenant companies with separate staff lists, separate joiners and leavers, separate visitors and separate expectations about who holds the record. The lanes are shared; the permissions must not be. Getting that architecture right is the difference between an entrance that quietly works for a decade and one that becomes a standing dispute between building management and tenants.
This page is about the system. Where the mechanisms differ in detail, it summarises and links to the dedicated explanations of how a swing barrier works, how a flap barrier gate works and how a tripod turnstile works.
How Does a Turnstile System Work?
A turnstile system works in five stages. A person presents a credential, a card, a face, a QR pass on a phone, 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 one 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. The sequence is identical in a free zone office suite, a hotel back-of-house corridor and a mall office core. What changes between buildings is who owns the permission database, how cleanly it separates the populations using the lane, and what the authority having jurisdiction expects the lane line to do when the fire alarm activates.
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 makes the stack the quickest route to diagnosing an entrance that is misbehaving, and the quickest way to settle which party in a multi-tenant building is responsible for fixing it.
The credential layer
The credential is whatever the person carries, or is. Four families are in common use, and most working lobbies run more than one at a time.
- Card or RFID: a proximity or smart card, a fob, or a UHF tag. Familiar here in a way worth noting: residents and drivers already understand windscreen-tag identification from road tolling, so the idea that a tag is read at a distance needs no explaining to a tenant or a visitor. The weakness is that the card is not the person, and in a shared lobby it can be handed back at the door.
- Biometric: face recognition dominates in corporate towers and free zone offices because it is contactless and quick; fingerprint and palm readers remain where the population is fixed and enrolment is straightforward. Binding the passage to the individual is also what makes the event usable as an attendance record.
- QR code or mobile credential: a code on a phone screen or a credential held in an application over Bluetooth or NFC. The dominant method for visitors, and increasingly for residents and guests in serviced buildings where an application already exists.
- PIN: keypad entry, normally as a second factor alongside a card rather than on its own, since it shares the card's weakness and is slower at a busy lane.
The reader layer
The reader converts a presented credential into a digital identifier and passes it on. 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 pedestal head, on a separate post, or on the wall ahead of the lane, and they connect to the controller over Wiegand, OSDP, RS-485 or IP.
Direction decides how many are needed: a lane controlled both ways needs a reader at each end, while a lane free to exit needs an entry reader plus an exit sensor. Settle this before pedestals are ordered, because head cut-outs are factory work. Face terminal positioning deserves the same early attention, since a glazed lobby facade behind an approaching user is a recognition problem rather than a product fault and is common in lobbies here.
The turnstile lane controller
The lane controller is the decision board inside the pedestal. It receives the identifier, evaluates it, drives or releases the mechanism, watches the passage sensors, raises alarms, buffers events and reports upward. On most current systems it holds a cached copy of the permissions relevant to its lane and decides locally without asking the server, the property that lets an entrance survive a network failure, treated in its own right below.
It is also where local behaviour is set: release timeout, response to a tailgate detection, whether an unauthorised push produces a tone at the lane or a silent alert at the security desk, 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 platform. This is where the authoritative permission database lives: who exists, what credential they hold, which lanes and doors 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 inside requires a view of every controlled route at once.
In a multi-tenant building this layer is also where the commercial relationships live, which is why it is the part most often specified last and regretted first. Who operates it, who can see which records, and what a tenant may do without asking the building are all decisions taken in this layer, and they are considerably easier to set up at commissioning than to renegotiate once a building is occupied.
The network and management software
Lanes, panels and server are tied together over the building network, commonly Ethernet with Power over Ethernet feeding readers and controllers, sometimes RS-485 trunks in retrofits. On top sits the management software: enrolment, credential issue and revocation, access groups and schedules, live monitoring, alarm handling, and the reports the installation was bought for, occupancy, muster lists, attendance extracts, exception reports on denied attempts and forced passages. In a shared building the reporting layer is often what each tenant actually wants from the system, and whether tenants can self-serve those reports is a specification question rather than an afterthought.
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 wakes the reader or sets the directional indicator. |
| 2 | Credential is presented | A card is tapped, a face is presented to the 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 swing panel opens, flaps retract, a tripod head is freed for one rotation, a full-height rotor unlocks. 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 nobody passes within the timeout, the release is cancelled and the credential must be presented again, so an authorisation cannot be stored up for 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 visitors, contractors and fit-out teams. |
| Person is permitted at this lane | The access group the person belongs to includes this lane. A visitor pass may open the lobby 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 housekeeping group may be valid only between defined hours; a fit-out contractor group only during permitted working periods. |
| 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 (in a shared building) a tenant partition that scopes the credential to one company's floors. |
Which of these are enforced is a configuration decision and varies by software platform. A small single-occupier office may enforce only the first three; a tower with a tenant partition, a visitor process and a lift destination system behind the lanes may enforce all of them on every presentation.
Permission Architecture in a Multi-Tenant Building
This is the section that distinguishes entrance control in this market from entrance control almost anywhere a single organisation occupies its own building. The physical problem is simple: one lobby, one lane line, many employers. The design problem is that the lane hardware is shared and the permission data must not be.
Separating tenants on shared lane hardware
The structure that works is a partition in the permission database rather than a separation in the hardware. Each tenant becomes a container, a company, a partition, a site, depending on what the platform calls it. People are enrolled into their tenant's container, placed in access groups that belong to that container, and those groups are granted the shared lobby lanes plus whatever is behind them for that tenant: specific floors through the lift system, specific suite doors, specific parking zones.
Three properties follow, and all three should be tested at commissioning rather than assumed. A tenant administrator can see and manage only their own people. A tenant's report shows their own traffic and nobody else's. And a change made by one tenant cannot affect another tenant's access, including by accident, the configuration error that grants one company's group a neighbour's floor is considerably easier to make than to detect.
What the lanes themselves hold is the union of all of this: every valid credential in the building, with the lane permission that lets it through the lobby line. That is why the controller's credential capacity is a real specification number in a tower rather than a line on a datasheet nobody reads. A lane sized for one occupier's headcount will not hold a fully let building's population, and the symptom when it overflows is not an error message but a credential that intermittently does not work.
Who issues a credential, and who revokes it
The governance question matters more than any hardware decision in a shared building, and it has only a few workable answers. Building management may issue every credential centrally, which gives a clean record and a slow process. Each tenant may issue their own within their partition, which is quick and puts revocation where the knowledge is. Or the building may issue and the tenant may request, which is the usual compromise and the one that needs the clearest service definition.
Whichever model is chosen, revocation is the part that decides whether the system stays trustworthy. A tenant employee resigns on a Thursday; if nobody tells building management, the credential works on Friday, and next year, and after the tenant has vacated. Two controls prevent that drift, and both belong in the handover documentation rather than in somebody's memory. Give every tenant-issued credential a validity end date aligned to something that genuinely expires (a lease period, a visa cycle, an annual re-confirmation) so that inaction produces an expiry rather than an open-ended permission. And run a periodic reconciliation in which each tenant confirms their active list, with unconfirmed records suspended rather than deleted so a mistake is recoverable.
Visitors, contractors and the building's own staff
A tower lobby carries at least four populations and they need different treatment. Tenant staff hold long-lived credentials inside their partition. Visitors are pre-registered by the tenant, receive a QR pass before arrival, and that pass is valid at the lobby line for a defined window and for that tenant's floors only. Fit-out and service contractors hold dated credentials scoped to the floors and hours their permit covers. Building staff (security, housekeeping, maintenance) sit outside every tenant partition and typically hold the broadest permissions in the building, which is precisely why their records deserve the tightest review.
The common failure is treating all four as one list. When a building issues the same open credential to a tenant's fit-out contractor as to its own maintenance team, the permission database stops describing the building and nobody notices until an incident requires it to.
Why each lane still decides for itself
A central database raises an obvious worry: if everything depends on one platform, what happens when the link fails during a morning peak? On most systems 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 for its lane and decides locally in milliseconds, informing the server afterwards. When a switch fails, a link drops, a server is rebooting or an update is running, the lane keeps granting and denying 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 rather than a universal one. Some lightweight or cloud-first architectures make the decision centrally and genuinely stop working when the link drops, a question with extra weight in a tower where the access platform may be operated by a third party on a network the building does not control. Confirm during design that local caching exists, that it is enabled, that controller credential capacity covers a fully let building, and that events buffer rather than being discarded. The failure mode only reveals itself on the day the link goes down, which is exactly the day a lobby full of people 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 hands it back out to a colleague, who enters on the same credential. The sensors cannot see this because both passages look entirely normal, so the answer has to come from the system's memory rather than its eyes.
The system holds a state for every credential: in or out of the controlled zone. Entering flips it 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, secure suites, server and switch rooms, 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. | Tower lobbies, residential communities and hotels that want the visibility without 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. |
Why anti-passback fails in practice
Anti-passback is defeated by a single uncontrolled exit route, and that is the commonest reason it is switched off within a month of being switched on. If people can leave through a fire stair discharging to the street, a loading bay, a car park link or a service door 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 in front of the tenants who complain most loudly, and the administrator disables the feature rather than reset several 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 not 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, and in a tower the walk has to include the car park levels, the service core and the retail link, which are exactly the routes a lobby-focused design forgets. 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 |
|---|---|---|---|---|---|
| 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 | Hotels, serviced buildings, hospitals, residential towers, any entrance needing an accessible lane |
| 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 tower lobbies, free zone office cores, airport and transport concourses |
| 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 | Labour accommodation, construction and site gates, logistics facilities, stadium perimeters |
| 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, yard and port boundaries, substations |
Selection follows from what the entrance has to do, and a well-designed line usually mixes types rather than choosing one. A common arrangement in a tower lobby pairs several flap lanes for volume with one wide swing lane for accessibility, luggage and deliveries, with the lane count driven by the shift-change peak rather than by the floor area available.
The Regulatory Context for Turnstile Systems in the UAE
This is the part of entrance control specification that differs most from other markets, and it is worth understanding before equipment is chosen rather than afterwards. Nothing in this section should be read as a statement of current rules. Requirements differ between emirates, differ again inside free zones, and change over time. They must be confirmed per project with the relevant authority.
SIRA governs the system and the installer, not only the device
Security systems in Dubai, and the companies that supply and install them, operate within the regulatory framework of SIRA, the Security Industry Regulatory Agency. The point that matters for a page about systems rather than devices is that the framework addresses the security provision as a whole and the companies delivering it, not a single item of hardware considered in isolation. A turnstile lane does not sit outside that framework because it looks like lobby furniture, and neither does the access control platform behind it, the video system bookmarking its events, or the company commissioning either.
The planning consequence is straightforward. Establish early, with the relevant authority, what applies to your building and your system type: which elements of the installation fall within scope, what is expected of the companies carrying out the work, and what documentation the project will need to produce. Doing that at design stage is considerably less disruptive than discovering a requirement during handover, when the lobby floor is finished and the lanes are grouted in. No supplier (including TimeWatch) should be understood as conferring regulatory status on a project, and no product should be described as approved or certified unless the issuing authority has said so in writing for that specific case.
Civil defence and the egress behaviour of the lane line
The life-safety aspects of an installation fall under civil defence authority, Dubai Civil Defence within that emirate, and equivalent authorities elsewhere in the country. For a turnstile system the central question is what the lane line does when the building's fire alarm activates: whether every lane releases and holds to clear the egress route, how the alarm signal reaches the lane controllers, whether that interface is monitored, and how it is tested.
Framing it as the lane line rather than a lane is deliberate, and it is the practical difference between a system-level design and a device-level one. An evacuating population does not use the entrance in its normal direction or its normal proportion; every lane becomes an exit lane at once, including the ones configured entry-only an hour earlier. The egress case therefore has to be assessed across the whole line, together with the floor area in front of it and the doors beyond it, and it belongs in the same conversation as the lane count rather than after it.
Because this is a life-safety function it should be designed as an interface between two systems rather than bolted on at the end as a pair of wires. The fire alarm contractor and the entrance control installer need to agree the signal type, the fail direction, the cabling route and the test method, and that agreement needs to be documented for the authority. The interface should then be tested as part of the building's scheduled fire drills, not only at handover.
Abu Dhabi, the northern emirates and free zones
Abu Dhabi operates its own framework administered by its own bodies, and a package prepared for a Dubai tower does not transfer unchanged to a building in Mussafah or on the islands. The northern emirates (Sharjah, Ajman, Umm Al Quwain, Ras Al Khaimah and Fujairah) each have their own municipal and civil defence arrangements, and an operator running buildings across several emirates should expect to confirm requirements separately for each rather than standardising a specification and assuming it travels.
Free zones add a further layer. Zones such as Jebel Ali and Dubai South commonly apply their own site rules, fit-out permitting processes and contractor registration requirements on top of emirate-level regulation, and for an office fit-out inside a zone those rules are the ones that actually govern what happens at the suite door. The sequence that works is: establish the zone authority's requirements first, then the emirate-level requirements, then specify the system.
Emergency Egress Applies to the Whole Lane Line
The core configuration 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, 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 behaviours are configurable and both are legitimate, for different routes.
The practitioner point made on the swing barrier page applies here too, and applies to every lane at once: this is a decision made with the fire strategy, and in the UAE it is more than that, because civil defence authorities govern how entrance control behaves on fire alarm. That makes it a regulatory determination rather than a configuration preference, and it changes who has to be in the room. The decision belongs to whoever owns life safety for that route, confirmed with the authority having jurisdiction, with the security requirement represented rather than deciding.
Three consequences follow for a system-level design. Decide before the lane layout is fixed: if the line is required to be fail-safe and the security concept depended on it being fail-secure, the resolution is an additional controlled boundary further inside the building, which is a floor-plan change rather than a controller change. Describe the behaviour in words, not labels, because fail-safe and fail-secure are used loosely in correspondence and mean opposite things; write down what physically happens on alarm and on power loss so the authority, the fire contractor and the installer read the same requirement. And make the interface hardwired rather than a software command over the network, because the network is one of the things that may not be working, then prove the line returns to normal operation cleanly after the alarm is reset, the part that is rarely tested and frequently surprises people.
Sizing a Lobby Lane Line
Total entrance capacity is straightforward arithmetic: lanes x per-lane rate = people per minute. If a lane handles 25 people per minute and a lobby has four lanes, the entrance handles 100 per minute, or 2,000 in a twenty-minute 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 prepared people presenting cleanly and walking through without hesitation. Real lobbies do not behave like that. People arrive in clusters when a lift discharges or a shuttle pulls up. They find the card at the lane rather than before it. They stop to position themselves for a face terminal. They carry a coffee in one hand and a laptop bag in the other. In practice the per-lane rate is set by credential presentation rather than mechanism speed, and the gap between catalogue and observed figures is routinely large.
Size from observed peak behaviour instead: count what 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 lobby with a counter; on a new tower it comes from net lettable area, expected occupancy density, lift capacity and the arrival profile the building's transport links produce. Two further points apply here. Morning and evening peaks are rarely symmetrical, so most lines use bidirectional lanes reconfigured by schedule. And the accessible wide lane belongs in the main line and should be counted as a working lane, because in a building with hotels, residences or deliveries it carries luggage, trolleys and prams as a matter of routine rather than as an exception.
Heat, Humidity and Shamal Dust Inside a Lobby
A turnstile line is indoor equipment, which leads people to assume that the environmental considerations governing an outdoor gate do not apply. Here that assumption is wrong often enough to be worth addressing directly. A lobby opens onto the outside, its doors cycle continuously, and most development in the country sits close enough to the Gulf that the air moving through that doorway carries both humidity and chloride.
Three effects matter at system level, and they show up in different places from the ones an outdoor specification anticipates. Electrical terminations in the pedestal base are the coolest point in the enclosure, which makes them where humid air gives up moisture on a cool night after a hot day. Salt-bearing condensate on terminal blocks produces intermittent faults long before anything looks failed (a reader that occasionally does not respond, a sensor pair that drops out at the same hour each morning) and in a system context those present as software problems and get investigated as software problems. Pedestal base fixings corrode where mopping water, wash-down and footwear-borne salt collect, and plated carbon steel anchors fail there long before anything visible happens above. Stainless of an appropriate grade is the response, and the grade matters more than the word.
Dust on the passage sensor arrays is the one that undoes the installation rather than merely annoying it. The array works on a signal margin, and a film of fine dust on a lens attenuates the beam until the receiver reads an unbroken beam as broken. The controller treats that as a body standing in the lane, so the lane will not confirm passage and close, or it reopens mid-travel, or it raises a tailgate alarm against nobody. After a shamal event the dust load across a portfolio rises at once. What follows is predictable: nuisance alarms accumulate, the desk stops trusting the alarm, and somebody reduces sensitivity to make them stop, at which point the lane is quiet and no longer detects the tailgating it was installed to detect. A post-event lens clean across all lanes prevents that chain, and folding the trigger into the maintenance routine works better than a fixed calendar alone.
Heat belongs in the same paragraph as a specification note rather than a maintenance one. Published duty rates for motorised mechanisms are stated at a reference ambient and fall as ambient rises, and a lobby behind a glazed facade in summer carries more solar gain than an indoor rating anticipates. State the conditions the equipment will actually experience when specifying, and require confirmation that the unit suits them.
Where Turnstile Systems Are Used in the UAE
- Multi-tenant corporate towers: the dominant application. Ground-floor lane lines in Business Bay, Dubai Marina and the Abu Dhabi commercial districts, with a tenant-partitioned permission database, visitors on pre-issued QR passes and lift destination control behind the lanes.
- Free zone offices and business centres: suite and floor entrances within zones such as Jebel Ali and Dubai South, where the fit-out sits inside a zone permitting framework and the occupier population turns over frequently.
- Hotels and serviced buildings: back-of-house and staff entrances, club and spa access, and serviced-residence lobbies, where the credential is often a mobile one tied to an existing guest or resident application and the wide lane carries luggage routinely.
- Malls and mixed-use developments: office cores and tenant-only areas behind a public mall environment, where entrance control starts at the core rather than at the street and the permission database spans several building uses at once.
- Multi-tower residential communities: lobby lanes in each tower on a shared community credential, where deliveries arrive continuously and the tailgating response has to suit a residential population rather than a corporate one.
- Logistics and port-related facilities: personnel gates at Jebel Ali and at Khalifa Port and KIZAD, where pedestrian and vehicle access are governed from one credential database and shift arrival is sharply peaked.
- Aviation and transport facilities: staff and crew entrances at Dubai International, Al Maktoum International and Zayed International, sized around shift patterns rather than passenger flow and usually behind a screening stage.
- Labour accommodation and construction sites: high-volume tripod and full-height lines at welfare and site gates, where the entrance record also supports workforce reporting.
- Government, municipal and institutional buildings: controlled public entry with an accessibility obligation and a formal visitor process ahead of the lane, alongside universities and hospitals where staff, student or patient and visitor routes are separated at the entrance.
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 and services entrance control and associated access equipment for buildings across the United Arab Emirates, from Dubai and Abu Dhabi through Sharjah and Ajman to Ras Al Khaimah, Fujairah and Umm Al Quwain.
Integration With Other Systems
- Visitor management: a tenant pre-registers a visitor, who receives a QR pass before arrival that the lobby line accepts for a defined window and for that tenant's floors only. 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 desk, the record is harder to fabricate than a separate punch at a wall unit, and one presentation serves both purposes. In a shared building this is usually a per-tenant service rather than a building-wide one.
- Lift and destination control: a validated passage calls a lift and allocates a car, or restricts the floors the person may select, which is also how a tenant partition becomes physical. In tall towers here this is close to standard practice, and it changes the lobby layout because queueing moves from the lift bank to the lane line.
- CCTV and video analytics: cameras overlooking the lanes bookmark footage against each event, so a tailgate alarm can be reviewed from its log entry rather than by scrubbing recordings. This is what converts an alarm from a tone into evidence.
- Screening equipment: walk-through metal detectors and baggage scanners positioned ahead of the lane so screening completes before the credential check, keeping the turnstile as the last point rather than the queue point.
- Vehicle gates and parking: the same credential database governs the barrier and the pedestrian lane, so one revocation closes both routes and the two sets of events reconcile.
- Fire alarm and building management: the hardwired emergency release described above, plus occupancy data shared for muster reporting during an evacuation.
- Community and tenant management platforms: in residential communities and serviced buildings, credential issue and revocation increasingly run from the same platform occupiers use for other services, which is a software integration specified at the same time as the lanes.
Installation and Maintenance Considerations
- Queue and dispersal space: the line needs clear space in front for people to form up and clear space behind for them to disperse. A line placed too close to a lift lobby moves the congestion rather than resolving it.
- Cable routing before the floor finish: power and data conduits cast or chased in before stone or tile is laid. Retrofitting them into a finished tower lobby is disruptive, visible and often impossible without closing the entrance.
- Lane count and lane mix from observed peaks: sized from counted arrival behaviour and realistic presentation times, with the narrow-to-wide ratio fixed at design stage against the luggage, trolley and delivery traffic the building will actually see.
- Controller capacity for a fully let building: confirm credential capacity and event buffering against the occupied population rather than the first tenant's headcount.
- Tenant partition tested at commissioning: prove that a tenant administrator sees only their own records and that one tenant's change cannot affect another's access.
- Corrosion specification: base fixing grade, gland selection and sealing detail agreed at design stage against the building's exposure, not chosen on site.
- Beam alignment recorded at commissioning across the full lane length, so later drift can be identified as drift rather than investigated as a fault.
- Emergency interface: hardwired from the fire panel, documented, tested at commissioning and then as part of scheduled fire drills, with behaviour matching what was agreed with the authority rather than what the controller defaults to.
- Authority coordination: permitting, approvals and any required documentation for the emirate and, where applicable, the free zone, confirmed before equipment is ordered.
- Scheduled lens and reader cleaning, with an additional inspection after any significant dust event, treated as its own item rather than as part of a mechanical service visit.
- Periodic database review: tenant reconciliation of active credentials, records with no expiry date, long-dormant credentials and contractor records outliving their permits.
- Alarm log review: a rising tailgate rate is usually a sensor or alignment problem rather than a change in behaviour, and reading the trend is how that gets caught before somebody reduces the sensitivity.
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 that manual checking cannot match.
- A tenant-partitioned database lets one lane line serve many employers while keeping records, administration and reporting separate.
- One database governs every controlled route in the building, so a single revocation closes the lobby line, the suite door and the parking barrier together.
- 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 platform outage where local caching is properly configured.
Limitations and considerations
- A turnstile manages and records passage; it does not physically restrain a determined person. Waist and chest-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, which in a tower usually means the car park levels or the service core.
- Governance is the hard part in a shared building. Credential issue, revocation and reporting responsibilities have to be agreed between building management and tenants, and a system with unclear ownership degrades into a list nobody can account for.
- 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 right setting differs between a corporate floor and a residential or hotel population.
- Humid salt-bearing air and shamal dust act on the system quietly, through corroded terminations and attenuated sensor beams, and both present as electronic or software faults rather than as environmental ones.
- Regulatory requirements are not uniform. What satisfies one emirate or free zone may not transfer to another, and requirements change, so each project needs its own confirmation, particularly for emergency behaviour.
Exact behaviour (decision logic, caching capacity, partition model, 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, 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.
How can one lobby serve many tenant companies on the same lanes?
Through a partition in the permission database rather than a separation in the hardware. Each tenant becomes a container, people are enrolled into their own tenant's container, and their access groups are granted the shared lobby lanes plus that tenant's floors and doors. The lanes hold every valid credential in the building; the administration, reporting and visibility stay separate per tenant.
Who issues and revokes access cards in a multi-tenant tower?
That is a governance decision taken at design stage, not a technical one. Building management may issue centrally, each tenant may issue within their own partition, or the building may issue on tenant request. Whichever model is chosen, give credentials a validity end date tied to something that genuinely expires and run a periodic reconciliation in which each tenant confirms their active list.
Do turnstile systems in Dubai fall under SIRA regulation?
Security systems in Dubai, and the companies that supply and install them, operate within the regulatory framework of the Security Industry Regulatory Agency, so equipment selection and installer engagement are a regulated matter rather than purely a commercial decision. The framework addresses the security provision as a whole, not one item of hardware. Requirements differ between emirates and change over time, so confirm the current position directly with the relevant authority.
Who decides what the turnstile lanes do on a fire alarm?
Not the controller settings, and not the security manager alone. Civil defence authorities govern how entrance control behaves on fire alarm, which makes the fail-safe versus fail-secure choice a regulatory determination here rather than a configuration preference. It applies to the whole lane line, because every lane becomes an exit lane during an evacuation, and it must be confirmed per project rather than carried over from another building.
Do turnstiles work 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 caching, credential capacity and event buffering should be confirmed during design, particularly where a third party operates the platform.
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 car park link or a service door that records no exit, their credentials stay stuck inside and the lane refuses them the next morning.
How many turnstile lanes does a tower lobby 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 lobby can be observed, or derive it from net lettable area, occupancy density, lift capacity and the arrival profile the transport links produce. Include at least one accessible wide lane and count it as a working lane.
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. Sensitivity is configurable, and a residential or hotel population needs a different setting from a corporate floor.
Does shamal dust affect turnstile sensors inside a lobby?
Yes, more than most people expect. A lobby opens onto the outside and its doors cycle continuously. The infrared array works on a signal margin, and a film of dust on a lens attenuates the beam until the receiver reads it as broken, producing obstruction and tailgate alarms against nobody. A lens clean across all lanes after a significant dust event prevents the week of nuisance alarms that otherwise follows.
Can someone get past a turnstile without a credential?
A waist or chest-height lane can be climbed or vaulted by somebody determined to do so. The system manages and records passage rather than physically restraining people. The security value comes from the alarm the attempt raises, the video bookmarked to the event and the response that follows. Where physical restriction is the requirement, a full-height turnstile in a cage is the appropriate equipment.
