An RTLS (real-time location system) does what occupancy sensors cannot: it tells you not just that a zone is busy, but which tagged asset or person is where, continuously. That capability is genuinely valuable in some offices and expensive overkill in most.
This guide covers what RTLS adds over simple occupancy sensing, how UWB compares with BLE and Wi-Fi RTT, where tracking earns its keep, and how to prepare ceilings, power and network during Cat-B fit-out so RTLS can be added later without reopening the ceiling.
What RTLS adds over simple occupancy sensing
Occupancy sensing answers "how many"; RTLS answers "what and where". A PIR or count-based sensor tells you a meeting room is full. An RTLS tells you that asset tag 4471, the shared spectrum analyser, has been on floor 3 since Tuesday.
That distinction changes what you can do. With zone-level presence and asset tracking you get:
- Asset location and history: find shared equipment in minutes, and see utilisation per asset rather than per room.
- Zone-level presence: neighbourhood-level occupancy for space planning, finer than floor counts and coarser than desks.
- Workflow analytics: how work moves between zones and rooms, useful in labs, studios and service operations.
For straightforward hybrid workplace questions such as desk and room utilisation, occupancy sensing plus booking data is usually enough. Our utilisation study methodology covers that path. Reach for RTLS when identity and movement, not just counts, are the question.
UWB vs BLE vs Wi-Fi RTT: accuracy, cost, infrastructure
Pick the technology by the accuracy your question actually needs. Room-level answers are cheap. Shelf-level answers are not.
| UWB | BLE (beacons/AoA) | Wi-Fi RTT | |
|---|---|---|---|
| Typical accuracy | Sub-metre to room-level | Room to zone; metres with AoA | Zone to room-level |
| Infrastructure | Dense anchor grid, wired anchors | Low-cost beacons, battery or PoE | Uses capable APs; needs RTT support |
| Relative cost | Highest | Lowest to moderate | Low if APs support it |
| Tag power | Battery tags, coin-cell life | Battery tags, long life | Phone-based, no dedicated tags |
| Best for | High-value assets, safety, precision workflows | Zone presence, asset lookup | Phone-based zone presence |
UWB wins on precision and works reliably around metal and multipath, which matters in labs and workshops. BLE wins on cost and battery life. Wi-Fi RTT is attractive because it reuses the network, but coverage depends entirely on your AP placement, which was designed for connectivity, not geometry. In practice many offices start BLE and add UWB only where precision pays.
Where RTLS earns its keep, and where it is overkill
RTLS pays for itself when a tagged thing is expensive, shared and often lost. That describes test equipment in engineering labs, medical devices in clinics, tool cribs in R&D workshops and demo kits that travel between teams. It also earns its keep in safety use cases, such as lone-worker zones or restricted areas where presence must be known.
It is overkill for ordinary offices. Tracking people desk to desk in a standard hybrid workplace buys resentment, not insight; count-based sensors and booking data answer those questions at a fraction of the cost. Shared equipment on ten floors is an RTLS case. Forty laptops never leave the building is not.
A honest test before you budget: name the decision you will make differently because you know an asset's location in real time. If you cannot name it, start with occupancy sensing and revisit. Our intentional smart office design guide walks through that filtering.
Privacy governance and employee trust
RTLS that tracks people without governance will poison trust in every other system you run. The rules are simple to state and require discipline to keep: track roles and assets, not individuals, unless a specific safety case justifies it; aggregate and anonymise analytics data; and say plainly what is collected, why and who sees it.
Put the governance in writing before installation. Cover data retention, access control, what dashboards show, and that location data is not used for individual performance management. Our occupancy sensor privacy design and smart office data governance guides give the framework.
Employee consent is a design deliverable, not a comms afterthought. Budget the conversation alongside the anchors.
Preparing ceilings, power and network during fit-out
The cheapest RTLS is the one you planned for during fit-out, even if you install it two years later. Anchors need line of sight, power and a wired uplink, which is exactly what the ceiling package controls.
Practical moves to build in now:
- Ceiling grid with spare capacity: design anchor positions into the ceiling layout, or at minimum keep the grid accessible so adding anchors does not mean demolition. Coordinate with the ceiling and MEP coordination process.
- Power and containment: run spare conduit and low-voltage cabling from the comms room to plausible anchor zones. Spare Cat6 runs cost little at first fix and a lot later.
- Network: reserve PoE budget, switch ports and a VLAN for location infrastructure in the network design brief, so RTLS never competes with core traffic.
- Power and heat checks: anchors are small loads, but a dense UWB grid adds up; include them in the electrical load schedule.
Document all of it in the asset register at handover, so a future integrator opens a drawing instead of the ceiling.
Frequently asked questions
Occupancy sensors count presence in a zone. RTLS identifies what or who is there and tracks movement continuously, enabling asset location and workflow analytics as well as utilisation data.
UWB is more accurate and more reliable around metal, but costs more in anchors and tags. BLE covers room and zone level at far lower cost. Choose by the accuracy your question needs.
Usually not. Desk and meeting-room questions are answered well by occupancy sensors and booking data. RTLS earns its keep with shared high-value equipment, labs or safety use cases.
Keep ceilings accessible, run spare conduit and Cat6 to anchor zones, reserve PoE ports and a VLAN, and document anchor geometry in the handover pack.