Do you actually need real-time tracking — or trustworthy locations?
Most asset-location problems are record problems, not real-time problems: audits, PMI schedules, and incident response need a location that is current and provable, not a dot moving on a screen. Continuous RTLS earns its infrastructure when seconds matter around the clock; attestation-based confirmation — updating the record every time a person verifiably interacts with the asset — delivers audit-grade location data at a fraction of the cost.
What question are you actually answering?
Before comparing systems, it's worth separating two questions that get conflated constantly in RTLS sales conversations: "where is this asset right now, live" and "where is this asset, provably, as of the last time it mattered." They sound similar. They call for completely different architectures.
"Where is it now, live" is a genuine real-time question. It shows up in active wander management for at-risk patients, where a delay of minutes is a safety incident. It shows up in emergency department throughput, where staff need bed and bay status the instant it changes. It shows up in staff duress monitoring, where the whole point is knowing a location the second a button is pressed. These use cases have no substitute for continuous location — the value is in the "now."
"Where is it, provably, when I need it" is a different question, and it's the one behind most equipment-tracking pain. Audit prep needs a defensible location for every asset on the list as of a known date, not a live feed. PMI (preventive maintenance and inspection) compliance needs to know an inspector can find the device when its service window opens. Incident response after a device is implicated in an adverse event needs a documented chain of custody, not a real-time ping — by the time anyone is asking the question, the moment has already passed. Read more on this distinction in building an audit-ready asset inventory and using location data in incident response.
The mistake many buyers make is pricing out continuous RTLS to answer the second kind of question. It works — RTLS infrastructure can certainly tell you where something was five minutes ago — but it's solving for a freshness interval measured in seconds when the actual requirement is measured in days or weeks.
What does continuous RTLS give you — and cost you?
Continuous RTLS pairs battery-powered tags with fixed infrastructure — infrared or ultrasound receivers for room-certain accuracy, or BLE gateways and Wi-Fi access points for zone-level coverage — so that any tagged asset's location is always current on a dashboard. RTLS explained covers the underlying architectures from CenTrak, Sonitor, Zebra, and AiRISTA in detail; the short version is that every one of them requires readers or sensors installed throughout each covered space, cabling or battery-powered mounts to put them there, and a tag with its own battery on every tracked asset.
That's also where the cost structure lives. Vendors rarely publish list pricing, but the pattern holds across architectures: hardware (BLE tags and gateways run cheaper per unit than UWB or dedicated IR/ultrasound infrastructure), installation labor (ceiling access and cabling in occupied clinical space, which is the line item that most often surprises buyers), tags and batteries (every asset needs one, and every battery eventually needs replacing — CenTrak and AiRISTA publish different multi-year figures under different test conditions, so don't treat vendor battery-life numbers as directly comparable), and ongoing recalibration and maintenance for a fleet that can run into the thousands of tags. Industry guidance is to request a five-year total-cost-of-ownership model rather than a per-tag quote, because these four buckets compound differently over a system's life. See RTLS explained for the full cost breakdown by architecture.
None of that is a knock on RTLS — it's simply the honest price of continuous, infrastructure-backed location. The question is whether your use case needs to pay it.
What is attestation-based location confirmation?
Attestation-based location confirmation takes a different premise: instead of installing infrastructure to watch every asset continuously, it updates the location record every time a person verifiably interacts with the asset. A technician scans a barcode during a PM visit. A nurse checks equipment in or out at a supply closet. A rounding tech walks a floor and confirms devices are where the CMDB says they are. Each of those interactions — which already happen as part of normal clinical or facilities work — becomes a location attestation: a timestamped, provable statement of where the asset was, made by a verified person, at a verified moment.
The freshness this delivers is measured in days, not milliseconds — and for record-driven use cases like audits, PMI compliance, and CMDB accuracy, days is exactly the resolution the question actually calls for. It requires zero installed infrastructure: no ceiling-mounted readers, no gateway network, no dedicated tag battery program to run. The location record simply gets more current every time work touches the asset.
The honest limit has to be stated plainly, because it's the trade-off that makes the model work at all: an asset nobody touches doesn't self-report. If a device sits untouched in a back closet for months, attestation-based confirmation has nothing new to say about it — the last known location just ages. That gap is exactly what battery-powered BLE beacons are built to cover, either as always-on tags on your highest-risk assets or as a periodic sweep that re-attests dormant equipment without requiring a person to physically interact with it. Attestation-based confirmation and beacon coverage aren't competitors — they cover each other's honest limits.
Which alternatives do people actually evaluate?
This is also the search a lot of buyers run as "CenTrak alternatives" — not because anything is wrong with continuous RTLS, but because they're pricing out a full room-level infrastructure build for a problem that turns out to be about audit and compliance record-keeping rather than live tracking. Here's the honest field of options, each with its real trade-off.
- Periodic physical inventories. A team walks the facility on a fixed cadence — quarterly, annually — and manually reconciles what's found against the asset register. It's the lowest-tech option and requires no ongoing system at all, but the location data is only as fresh as the last count, and a large, mobile fleet can take days of dedicated labor per cycle. It works fine for low-value, low-movement assets; it strains badly for anything that moves department to department.
- RFID portal or handheld audits. Passive RFID tags on assets get bulk-read at doorway portals or via handheld readers during a walkthrough, which is much faster than manual barcode scanning for large counts. The trade-off is that portals only see what physically passes through them, and handheld audits still require someone to walk the space with the reader — it accelerates the same periodic-inventory model rather than replacing the need for a scheduled sweep.
- BLE beacon spot coverage. Rather than instrumenting an entire building, beacons go on the highest-value or highest-risk assets, or blanket the specific zones where losses or compliance findings actually occur. This gets you near-continuous visibility exactly where it's worth paying for, at a fraction of full-building RTLS cost, while leaving lower-risk areas on a lighter-touch process. The trade-off is coverage gaps by design — anything outside the beacon zones is back to whatever process covers the rest of the fleet.
- Process discipline in the CMDB. Rigorous check-in/check-out logging, mandatory location fields on every work order, and enforced data hygiene can keep a configuration management database reasonably accurate without any hardware at all. It's the cheapest option in dollars and the most expensive in organizational discipline — it only works as well as the humans following the process, and it degrades quietly the moment enforcement lapses.
None of these is a strict downgrade from RTLS — each is a different bet about where your fleet's actual risk and movement patterns are, and how much you're willing to pay in infrastructure versus process to cover them.
How should you decide?
The decision usually comes down to four questions, and the table below maps how the answers point you toward continuous RTLS versus a lighter-weight alternative.
| Question | Points toward continuous RTLS | Points toward attestation / alternatives |
|---|---|---|
| Do you need the location right now, live? | Yes — active wander management, ED throughput, duress monitoring | No — you need it as of the last audit, PM visit, or incident |
| Do you have budget for installed infrastructure? | Yes — ceiling work, gateways, and a multi-year tag/battery program are acceptable costs | No — you'd rather spend on labor already happening than on hardware |
| Is the driver an audit or compliance finding? | Rarely the primary driver | Yes — attestation-based confirmation is built for provable, timestamped records |
| How large and mobile is the fleet? | Large, high-value, high-movement fleets can justify full infrastructure | Large mobile fleets with frequent technician contact get "free" location updates from attestation |
Most organizations aren't purely one or the other — a small set of assets genuinely needs real-time coverage (duress badges, high-theft-risk equipment) while the bulk of the fleet is better served by a process that gets cheaper and more current the more your team already touches the equipment day to day.
Where Forager fits
Forager implements attestation-based location confirmation as a 10-second side effect of field work your technicians already do — a barcode scan during a service call, a check during rounds — rather than a separate task or a dedicated locating infrastructure. Every interaction updates the asset's location record with a timestamp and the person who confirmed it, which is exactly the audit-grade, provable data that audits, PMI compliance, and incident response actually need.
Forager doesn't attempt to replace continuous RTLS for the use cases that genuinely require it — if your problem is active wander management or second-by-second ED bed status, that's still a job for infrastructure-backed real-time systems. But for the much more common problem of keeping a large asset fleet's location record current and defensible without installing readers, running cable, or maintaining a tag battery on every device, Forager delivers that at $15/device/yr with no infrastructure changes. For the assets that sit untouched between service visits, pair it with Ravens beacons to close the self-reporting gap. See how Forager works.
See asset intelligence on your own floor plan
Forager confirms asset locations as a side effect of the work your techs already do — $15/device/yr, no infrastructure changes. How Forager works or talk to us.