ZebIQ Technology

// INSIGHTS

RFID and NFC Zone Access Control Across a Multi-Hall Venue

6 min read

Zone access sounds simple until you draw the venue plan. Six halls, a paid workshop room, a VIP lounge, an exhibitor-only build area and a media centre. Fourteen doorways. Three delegate categories that each see a different subset. Then someone asks for live occupancy numbers for the fire safety officer. The technology choice you make at this point determines whether the system reads people as they walk or asks them to stop and tap.

UHF RFID and NFC solve different problems

These get used interchangeably in event proposals. They are not interchangeable.

UHF RFID operates in the 865 to 867 MHz band allocated for India by WPC. Read range with a portal antenna is typically 2 to 6 metres depending on tag placement, body shielding and antenna power. Delegates walk through and are read without stopping. That is the appeal, and it is also the risk: a reader that can see a badge six metres away can also see the badge of someone standing in the corridor who never entered.

NFC operates at 13.56 MHz with a read range of a few centimetres. It requires an intentional tap. Slower per person, roughly 1 to 2 seconds, but effectively unambiguous. Nobody is accidentally admitted to the VIP lounge because they walked past the door.

The practical rule we apply:

  • Footfall counting and hall-level flow: UHF RFID, because you want frictionless passive reads
  • Paid or restricted zones: NFC tap, or UHF with a turnstile that enforces one person per read
  • Cloakroom, catering entitlements, lucky draws: NFC, since the interaction is already a deliberate stop
  • Anything where a wrong admission is expensive: never rely on read range alone

Most multi-hall venues end up with both. That is a correct answer, not a compromise.

Design parameters we work to

865-867 MHz
The UHF RFID band allocated for India by WPC, which constrains antenna and power selection
2-6 m
Realistic UHF portal read range once body shielding and badge placement are accounted for
Local cache
Every reader holds its own access list, so a network cut does not turn a controlled door into an open one

How the access layer is built

Entitlements live on the server, cached at the edge

Each reader stores the current access list locally and evaluates decisions itself. Central changes propagate when the network is up, but a decision never waits on it.

Direction-aware portals

Paired antennas determine whether a read is an entry or an exit. Without this, occupancy counts drift upward all day and become useless by afternoon.

Anti-passback rules

A badge that entered a zone and never exited cannot enter again from a different door. This is the practical check against one badge covering three people.

Live occupancy per hall

Current headcount per zone on a dashboard, with configurable thresholds. Useful for safety officers, and useful for exhibitors who want to know when their hall was busiest.

From venue plan to working doorways

  1. Walk the venue and mark every opening

    Including service doors, fire exits and the gap in the pipe-and-drape that everyone uses as a shortcut. Uncontrolled openings are what break occupancy maths.

  2. Fix the entitlement matrix

    Categories down one axis, zones across the other, and a yes or no in every cell. This document gets signed off before hardware is ordered.

  3. RF survey and antenna placement

    Metal structures, LED walls and truss reflect and absorb. We test read rates at the actual doorway, at badge height, with people walking, before finalising positions.

  4. Rehearse the exception

    Staff need one clear procedure for a denied read: check, override, log. If the override is undocumented, security invents their own and the audit trail is gone.

Failure modes worth knowing about

Tailgating is the honest limitation. A UHF portal without a physical turnstile cannot stop two people walking through together when only one badge reads. Any vendor telling you otherwise is selling you something. If a zone genuinely must be restricted, the answer is a turnstile or a human, with RFID doing the verification rather than the enforcement. We say this early because it usually changes the budget line.

The second issue is badge placement. A UHF tag pressed against the body or tucked under a jacket loses several metres of read range. Lanyard length and badge orientation affect read rates more than antenna power does, and the fix is a badge design decision plus a line of instruction at registration, not a bigger reader. The third is interference. Two portals facing each other across a narrow corridor will read each other's traffic, and a hall with heavy LED lighting can raise the noise floor enough to drop reads. Both are found by surveying on site. Neither is found by looking at a floor plan in a PDF.

What organisers usually want to know

Can we use the same badge for access and for lead retrieval?

Yes, and it is the sensible design. A dual-technology badge with a UHF inlay for zone reads and an NFC or QR element for deliberate interactions covers both. It costs more per badge than a plain printed badge, so it is worth confirming the per-unit price against your headcount early.

Is RFID worth it below 2,000 delegates?

Often not. Below that scale, QR scanning at doorways usually gives you the same data at a fraction of the hardware cost, and the queue impact is manageable. RFID starts paying for itself when read volume is high, doorways are many, or the client specifically needs passive footfall data.

Does zone tracking create a data protection issue?

It creates a data protection obligation. Movement data is personal data under the DPDP Act, so the purpose has to be disclosed at registration, retention has to be bounded, and what you share with sponsors should be aggregated rather than individual unless the delegate has consented to that specific use.