RTLS for Secure Environments: A Buyer’s Guide for High-Security Facilities

Real-time location systems are commonplace in retail warehouses, hospital supply rooms, and manufacturing plants. But those environments share very little with a maximum-security prison, a forensic psychiatric hospital, or a correctional healthcare unit. When procurement teams at high-security facilities begin evaluating RTLS, they quickly discover that most vendor guides, comparison articles, and industry overviews were not written with their constraints in mind.

This guide addresses that gap. It reminds readers what RTLS is, and also how different technologies compare when deployed inside architecturally dense and operationally complex buildings, what security controls matter, and how to evaluate and select a system that will actually work once installed.


What “Secure Environments” Means for RTLS, and Why Standard Guidance Falls Short

Let’s start with a definition: A secure environment, in the context of RTLS, is any facility where the physical structure, operational security requirements, or regulatory obligations place constraints on location technology that go beyond ordinary commercial or healthcare settings. Prisons, jails, forensic hospitals, behavioral health units, and certain critical infrastructure sites all qualify.

What makes these environments so challenging is not any single factor but the combination of several that tend to appear together. The buildings themselves are built for containment, which means the same physical properties that prevent people from moving freely also interfere with radio signals. Operational requirements demand location accuracy at the room or cell level, because approximate location is not useful in a facility where two adjacent spaces may house very different risk profiles. And the consequences of a system failure are not measured in inconvenience but in safety.

Consider a correctional facility built in the 1980s: reinforced concrete construction throughout, steel cell doors on every wing, a cramped control room receiving radio calls from officers scattered across multiple floors. Radio frequency signals that travel comfortably through a modern drywall office environment are attenuated, reflected, and blocked in that setting. The metallic surfaces create multipath interference, where signals bounce unpredictably and arrive at receivers from multiple directions, degrading accuracy and causing false zone assignments. The small, densely partitioned spaces of a cellblock mean that zone-level accuracy — knowing someone is “in the north wing” — is nearly useless when the north wing contains sixty individual cells. And in a correctional or forensic healthcare setting, again, a gap in location coverage is not a stock discrepancy: it is a safety event.

Standard RTLS guidance rarely accounts for any of this. Most published comparisons assume clean RF environments, open floor plans, and tolerant accuracy requirements. They default to typical’ technoogies like BLE, Wi-Fi, and Ultra-Wideband (UWB). These Systems that rightly receive strong reviews in commercial settings may fail in meaningful ways the first time they encounter a reinforced concrete wall. Buyers in secure environments need different evaluation criteria entirely.


RTLS Basics: What It Is, How It Works, and Key Components

A real-time location system (RTLS) is a technology infrastructure that continuously tracks the physical position of tagged people or assets within a defined space and reports that position to a software platform, typically at near-real-time intervals.

Unlike GPS, which relies on satellite signals and is effectively unusable indoors, RTLS is designed specifically for enclosed environments where satellite visibility is unavailable. Understanding what sits inside that definition helps clarify what you are actually procuring, because RTLS is not a single product but a layered system of hardware and software that must work in concert.

At the physical layer, tags (small battery-powered devices worn on lanyards, clipped to badges, or attached to equipment), broadcast signals at regular intervals. Fixed infrastructure devices called locators, receivers, or anchors pick up those signals throughout the building and pass the raw data upstream. Gateways aggregate the data from multiple locators and route it to the location engine, which is the computational core of the system: the software or appliance that processes signal data, applies positioning algorithms, and produces a calculated position for each tag. Above all of that sits the management software, the interface through which operators see live location data, define zones, configure alert rules, and pull reports.

Every layer of this stack matters, and each layer introduces its own performance constraints. A well-designed location engine cannot compensate for locators placed too far apart for the signal technology being used. A sophisticated management interface cannot help if the tags lose connectivity when carried into a basement holding area. When evaluating vendors, it is worth asking questions at each layer rather than treating the system as a single product with a single performance specification.


Types of RTLS Technology and When to Use Each in Secure Sites

The choice of signal technology is probably the single most consequential decision in any RTLS procurement for a secure facility, and it is also the area where general guidance most consistently misleads buyers. A technology that performs excellently in an airport terminal or an open-plan hospital ward may be wholly unsuitable for a correctional environment, not because the vendor oversold it but because the physical conditions are genuinely different. Understanding the tradeoffs of each technology before a vendor sets foot in your building puts you in a much stronger position.

  • Ultra-Wideband (UWB) achieves centimeter-level accuracy through either time-of-flight (ToF), time-difference-of-arrival (TDoA), or angle-of-arrival (AoA) signal measurement. Essentially, it determines positions based on when and/or where a tag signal is received. Frequently cited as a premium option, UWB uses a very short ‘ping’ of data across a broad spectrum (hence ‘wideband’) and therefore performs well even in highly reflective spaces where it can distinguish between multiple reflected signals. However, it can be expensive to deploy at scale and signals cannot easily pass through concrete and steel correctional buildings.
  • Bluetooth Low Energy (BLE) is widely available and cost-effective, and in a clean RF environment it delivers reasonable room or even sub-room-level accuracy (with 1 meter). The problem in secure environments is that BLE signals are susceptible to interference in congested RF conditions. A cellblock wing with dozens of active devices, security radios, and Wi-Fi access points can create the kind of congestion that causes BLE location data to become unreliable precisely when it matters most. Signals an also be hampered by muilt-path reflections making positioning less reliable.
  • Wi-Fi RTLS repurposes existing wireless infrastructure for location purposes, which is appealing from a capital cost perspective. In practice, the networks in correctional and forensic hospital buildings are often already congested with operational traffic, and adding continuous location updates to that load increases both network strain and location latency. Accuracy is typically limited to zone-level, which is insufficient for staff duress or cell-level inmate tracking.
  • Active RFID uses battery-powered tags that transmit continuously to dedicated readers, providing ongoing position updates without requiring a reader to be physically adjacent to the tag. Unlike passive RFID — which only communicates at very close range when a reader energizes an unpowered tag — active RFID is suited to environments where continuous real-time tracking across a wide area is the requirement.
  • Infrared (IR) achieves reliable room-level accuracy precisely because IR signals do not penetrate walls, which means a tag in one room cannot be detected by a receiver in the next. That containment is useful for location purposes, but IR also has strict line-of-sight requirements. In environments where staff may have their tags tucked under clothing or in a pocket, the system can fail at exactly the moment it is needed.
  • Ultrasound RTLS operates on a different physical principle entirely, using high-frequency sound waves rather than electromagnetic signals to determine location. Because ultrasonic signals do not travel through solid walls, they are naturally contained within the spaces they are deployed in. That containment is not a limitation in a secure environment; it is an asset. A tag inside a cell is heard only by the receiver in that cell, not by receivers in adjacent cells, which is the behavior that operational accuracy demands. Ultrasound is also immune to the RF interference that affects every radio-based technology on this list.
  • 900 MHz LoRa (Long Range) radio operates at a significantly lower frequency than Wi-Fi, BLE, or UWB, which gives it materially better penetration through dense materials including reinforced concrete and multi-floor structures. LoRa signals travel farther and through more layers of construction than higher-frequency alternatives, making them well suited to the communication backbone of an RTLS deployment in a large, dense building.

For secure facilities that need both reliable long-range signal delivery through dense construction and precise room-level or sub-room accuracy, the most practical architecture combines those two properties rather than asking a single technology to deliver both. Actall’s ATLAS platform is built on exactly that logic: 900 MHz LoRa handles communication between tags and gateways, reliably penetrating thick walls and multi-floor structures, while a 2.4 GHz channel handles short-range location pings that deliver sub-room positioning accuracy. The system operates on its own dedicated infrastructure, independent of facility Wi-Fi, and does not require network expansion.

For facilities where the primary requirement is fast, reliable alarm enunciation with room-level certainty and no RF interference risk, Actall’s PALS Sentry product line uses ultrasonic technology, a proven approach in clinical and correctional settings that the company has refined since 1997.


RTLS vs RFID vs GPS: Understanding the Differences

These three terms appear frequently in procurement conversations and are often used interchangeably, which creates real confusion when specifications are being written. The distinctions are straightforward but worth stating precisely, because conflating them leads to requirements documents that vendors interpret very differently from one another.

  • GPS (Global Positioning System) uses signals from satellites to calculate outdoor positions. It does not function reliably indoors, inside reinforced structures, or underground. It is not a relevant technology for personnel or asset tracking inside a secure facility, regardless of what marketing materials may suggest.
  • Passive RFID uses tags that contain no battery and no independent power source. When a powered reader passes within range — typically a few centimeters to around a meter — it energizes the tag and reads a stored identifier. Passive RFID is useful for access control, inventory scanning, and supply chain applications, but it does not provide continuous real-time position data. You learn that a tag passed a specific reader at a specific time, not where that tag is right now.
  • Active RFID uses battery-powered tags that broadcast independently and continuously, which means the system always knows where the tag is, not just where it last crossed a fixed point. RTLS is the broader infrastructure and software category that processes active tag signals — whether from active RFID, ultrasound, UWB, BLE, or other technologies — and presents the result as real-time positional information. If a system only logs entry and exit events at defined checkpoints, it is a proximity detection or access control system, not a true RTLS.

Use Cases in Secure Operations

The value of RTLS in a secure environment is most clearly understood through the operational problems it solves, because the use cases here differ in character from those in commercial settings. Location data in a prison or forensic hospital is not primarily about efficiency or asset utilization; it is about safety, control, and accountability. The following use cases illustrate where RTLS delivers measurable operational improvement in this context.

The most time-critical use case is staff duress. When an officer or clinician is in distress, the seconds it takes a responding team to identify and reach the correct location can determine whether an intervention succeeds. With RTLS, a duress activation from a wearable tag immediately displays the staff member’s precise location on a monitoring interface, removing the uncertainty that costs time in a radio-call-and-search response model. The value of this capability depends entirely on the accuracy of the location data, which is why sub-room or room-level precision matters in a way that zone-level accuracy cannot satisfy.

Inmate and patient movement monitoring serves a different but related purpose. Automated tracking of movement across defined zones supports schedule compliance, reduces unauthorized movement between wings or units, and produces an auditable record that carries both operational and evidentiary value. Zone-based access enforcement extends that capability into proactive boundary management: facilities can configure real-time alerts when a tag crosses into a restricted area, enabling control room staff to respond to boundary events without relying on officers to physically observe every corridor simultaneously.

Asset tracking addresses the specific accountability requirements of secure environments, where medical devices, restraint hardware, pharmaceutical carts, and other critical equipment must be where they are expected to be when they are needed. Continuous tracking reduces loss, supports chain-of-custody requirements, and removes the manual search process that currently consumes staff time in many facilities.

Underpinning all of these use cases is compliance reporting. Continuous location data creates documentation that accreditation bodies and regulators increasingly require: observation frequency records, incident timeline reconstructions, and automated evidence of where staff and residents were during defined periods.


Deployment Challenges in High-Security Facilities

Even when the right technology has been selected, deployment in a secure facility involves challenges that general RTLS implementation guidance does not address. Understanding them before procurement reduces the risk of a system that performs well in a vendor demonstration but underperforms in the building it was installed in.

Signal propagation is the most common source of post-installation surprise. Vendors may conduct initial site surveys using tools and methodologies calibrated for commercial environments, which produce inaccurate predictions when applied to reinforced concrete construction with dense metallic fixtures. The RF environment inside a cellblock is genuinely different from the one inside an open-plan office, and a survey that does not account for that difference will produce an infrastructure layout that leaves gaps. Facilities should require vendors to conduct a site-specific RF assessment under realistic occupancy conditions before any hardware specification is finalized — and should treat any vendor who is reluctant to do this as a risk.

Network independence is a related requirement that is often underestimated at the procurement stage. Many secure facilities have security policies or network architecture constraints that prevent RTLS traffic from being routed through general-purpose facility networks. Beyond policy, there is a practical resilience argument: a system that shares its communication backbone with other facility systems inherits those systems’ failure modes. Dedicated radio infrastructure operating on its own frequency band eliminates that dependency entirely.

Tag design is another area where secure-environment deployments diverge significantly from commercial ones. Tags worn by inmates or forensic patients need to withstand deliberate physical abuse. Tags worn by clinical staff need to be discreet enough not to telegraph their presence to an agitated patient, but fast to activate under stress. These are not the same design requirements, and a platform that offers only a single tag form factor will force operational compromise somewhere.

In forensic hospital and broader healthcare settings, interference from clinical equipment adds a further complication. Imaging systems, physiological monitors, infusion pumps, and other powered medical devices generate RF emissions that affect radio-based location systems in ways that are difficult to predict without direct measurement. Systems that do not depend on RF for room-level resolution, including ultrasound-based systems, are substantially more resilient in these environments.


How to Choose the Right RTLS for a Secure Environment

The most useful evaluation framework for secure facilities starts not with vendors but with requirements, because the requirements in this sector are specific enough that they will quickly eliminate unsuitable systems. Working through clear criteria before issuing an RFP or attending vendor demonstrations produces a far more productive procurement process than discovering critical gaps after a preferred vendor has been selected.

Start with accuracy. Define the minimum location granularity each use case actually requires, and write it down as a pass/fail criterion. Whilst centimeter level precision everywhere may feel useful, if it’s not critical the system will be over specified and expensive. Staff duress typically demands room-level or sub-room accuracy because a zone-level result does not get responders to the right door. Asset tracking in a large facility may tolerate lower resolution. Specifying this before reviewing products ensures you are comparing systems against a fixed bar rather than accepting whatever each vendor offers as sufficient.

Infrastructure independence should be treated the same way. Either the system can operate on its own dedicated radio network without depending on facility Wi-Fi, or it cannot. For most high-security sites, this is not a preference but a requirement, and stating it as one filters out a significant portion of the market early.

Performance in dense construction is where vendor experience matters most. Ask for documented evidence of deployments in environments with reinforced concrete construction, not performance specifications derived from commercial or open hospital ward settings. A vendor that can reference comparable, contactable installations in corrections or forensic healthcare carries substantially more credibility than one whose reference sites are logistics centers or corporate campuses.

On-premises hosting capability should be confirmed before any commercial conversation progresses. Some vendors offer on-premises deployment as a secondary option with reduced functionality; verify that the full platform is available without a cloud dependency, and confirm this in writing. Integration pathways deserve equal scrutiny: location data generates its operational value through connection to access control systems, video management, incident management platforms, and custody or health records. Identify which integrations have been implemented and tested in comparable facilities, not merely listed as theoretically available.


Implementation and Governance

A successful RTLS deployment in a secure facility does not end with hardware installation and software configuration. The operational and governance elements that follow commissioning determine whether the system delivers sustained value or gradually loses the trust of operational staff.

The site survey and RF assessment that precede infrastructure design should be treated as a distinct project phase with defined deliverables, not a preliminary formality. In dense construction environments, the difference between a thorough survey and a superficial one frequently shows up as coverage gaps that require remediation after installation, at considerably higher cost than designing correctly from the outset. Surveys should be conducted with the facility in realistic operating conditions, including typical occupancy and representative equipment in place.

Zone configuration deserves similar care. The boundaries that define where one location ends and another begins should be determined collaboratively with operational staff — who understand the practical significance of each space — and then tested rigorously before go-live. Adjacent zone bleed, where a tag physically inside one space is reported as being in a neighboring space, is a specific failure mode in dense, partitioned environments. It needs to be identified and corrected during commissioning, not discovered by staff responding to a real incident.

Staff training is routinely compressed in deployment timelines and almost always should not be. Control room operators, responding staff, and supervisors each need training specific to their role and to how RTLS data integrates with their existing workflows. Alert response protocols should be updated to reference the new location data before the system goes live, so that staff are not improvising how to use the information during an actual event.

Where the RTLS connects to access control, VMS, or incident management platforms, full end-to-end integration testing should precede operational deployment. Testing that confirms each system works individually but does not verify that alerts, location data, and events flow correctly between platforms will leave gaps that only become visible when the pressure is real.

Finally, data governance policies for location history need to be established before deployment rather than after. Retention periods, role-based access controls for historical location data, chain-of-custody procedures for incident-related records, and protocols for responding to data access requests all need to be defined and documented with input from operational, legal, and compliance stakeholders. These decisions are considerably easier to make before a system is live than during an investigation.


Actall has specialized in RTLS for architecturally complex and operationally demanding environments since 1997. The ATLAS platform and PALS Sentry product line are designed specifically for corrections, forensic behavioral health, and mainstream medical facilities where standard location technologies fall short. To discuss your facility’s requirements, contact Actall at actall.net.