Choosing the Right RTLS Provider: Key Questions to Ask

If you only buy one real time location system in your career, make it the one you actually need. That sounds obvious, yet many teams end up with the wrong fit because they start with a demo, not with a problem statement. The showroom tag that pops up on a glossy dashboard looks impressive, but the effort, cost, and process hidden behind that dot can surprise you later. I have seen warehouses spend twice their budget to retrofit anchors because their original plan ignored racking heights. I have seen hospitals stall for six months because badge batteries died faster than expected in metal-heavy wings. The right RTLS is not the one with the most features, it is the one that answers your use case without creating new headaches.

This guide distills the questions that separate a slick pitch from a workable deployment. It comes from the trenches - audits in busy emergency departments, walk-throughs in paint-curing plants at 60 Celsius, and rollouts across unionized logistics sites where a weekend outage is not an option.
Start with outcomes, not tags
Before asking a provider about anchors, tags, or algorithms, build a one-page view of what you are trying to achieve. Spell out the decision or action that will change because of location data. Teams that skip this step usually pay for accuracy they do not need or accept blind spots that undermine value.

A few examples sharpen the point. In a 300-bed hospital, we reduced missing-in-action infusion pumps by 70 percent with room-level accuracy and a hard rule that pumps must chirp when idle. Chasing down sub-meter accuracy would have added complexity without moving the needle. In a returnable packaging pool, however, we needed dock-door granularity - which pallet left through which bay - or the charge-back model would collapse. Two different outcomes, two different requirements.

Here is a fast filter I give executives when they have twenty minutes to shortlist an RTLS provider.
What decision will be made differently because of this data, and how exactly will that work in your current software? What is the smallest zone that still delivers value - building, floor, room, bed, shelf, or work cell? How quickly must the location update for the workflow to work - seconds, minutes, or on event? How long must tags last before maintenance - months, a year, multiple years, or rechargeable? Who will be accountable for rtls management after go-live, and what is their weekly time budget?
If a vendor cannot engage you at this level, you are not buying a system, you are buying a gamble.
Accuracy, update rate, and physics still matter
Every real time location services pitch eventually lands on accuracy. The nuance lies in how accuracy behaves in your environment. Sub-meter accuracy in a lab with perfect line of sight is not the same as sub-meter accuracy in a machining bay with heavy steel, reflective surfaces, and forklifts. You want proof that the claimed performance holds under your constraints, not just in a whiteboard diagram.

Be specific about update rates too. A room-level inventory check that runs every five minutes does not need the same cadence as a worker safety alert when a person enters a no-go zone. Higher update rates drive battery consumption, channel utilization, and back-end load. Align the update profile with your event model: steady heartbeats for presence, bursts for movement or state changes, and silence when an asset sleeps.

Ask the provider to describe how their location engine deals with multipath, line-of-sight loss, and anchor geometry. The answer should be in plain language: how many anchors per square meter for your ceiling heights, what happens if one anchor fails, what signal processing is used, how calibration survives a layout change. A good rtls provider will tell you where their approach struggles. If they say it works everywhere, they have not deployed enough.
The infrastructure you already have has a vote
You can build an rtls network on top of Bluetooth Low Energy, UWB, Wi-Fi, Chirp Spread Spectrum, passive and active RFID, or hybrid stacks that fuse inertial sensors with radio. Your physical site and existing IT policies narrow the field more than most marketing copy admits.

The first fork is power and mounting. If your ceilings are 12 meters and you cannot run permanent power on the floor due to safety rules, your anchor plan will drive you toward technologies that can get by with fewer, higher-mounted beacons. If you have drop ceilings with easy access and PoE everywhere, your options open up. A union rule against drilling into beams can change your bill of materials more than a discount on tags.

The second fork is spectrum and coexistence. An already crowded 2.4 GHz environment with dozens of handheld scanners and guest Wi-Fi behaves differently from a quiet private band. UWB often shines in metal-rich, cluttered spaces, but you still need a site survey to confirm channel plans and attenuation. Bluetooth-based systems can take advantage of commodity silicon and cheaper tags, but careful channel planning and filtering keep them from becoming noisy neighbors in dense deployments.

The third fork is your backhaul and security posture. Some sites ban outbound connections from IoT gateways. Others require certificate pinning, private APNs, or traffic through a corporate proxy. I have watched projects stall over a TLS library mismatch on a gateway. You want a provider who can map their rtls network stack to your rules without heroics.
A quick tour of location technologies, with trade-offs
If you have to choose among options, keep the comparison to what you can defend later in a budgeting meeting rather than what sounds cool on stage.
UWB, typically best-in-class for sub-meter accuracy, handles multipath well, but needs more anchors and slightly higher tag cost. Good for high-value assets, worker safety zones, and dense manufacturing cells. BLE angle-of-arrival or fingerprinting, affordable tags and flexible, but accuracy depends on antenna arrays, calibration, and environmental stability. Works well for room and zone presence, patient flow, and inventory visibility at a lower infrastructure cost. Passive RFID, cheapest tag by far, but not continuous real time location. Superb for chokepoints, kiosks, and inventory audits. A complement to, not a replacement for, continuous tracking. Wi-Fi based RTLS, leverages existing access points if the design supports it, but accuracy and battery life vary widely. Good for coarse presence and cases where running a parallel network is a non-starter.
A hybrid stack often wins - chokepoint reads at doors plus room-level presence for general assets, and UWB only where the workflow justifies the premium. The art is in not over-engineering every corner to the highest spec.
Software is the product you live in
After the pilot, your team spends time inside dashboards, reports, and integrations, not inside anchors. Ask to see how exceptions are highlighted and how users acknowledge and resolve them. Watch the clicks and count them. In a trauma center rollout, the turning point was a single screen that showed “likely hoarded devices” by room with a one-click page to the charge nurse. That delivered more value than prettier heat maps.

Check how the platform models your world. Does it support nested zones, dynamic geofences, and temporary work cells? Can you assign business rules to a zone - for example, “forklifts enter, operators must slow below 5 km/h, else alert operations”? The best real time location system software ties location to intent and action, not just coordinates.

Integration decides whether your RTLS becomes a pane of glass no one opens or a live part of your workflow. Confirm how it connects to your CMMS, ERP, WMS, nurse call, or MES. REST APIs are table stakes. Event webhooks, robust authentication, and versioned schemas separate grown-up platforms from science projects. Ask the vendor to show a live integration with a named system like SAP, Oracle, Infor, Epic, or Meditech, complete with data mapping. The smoothest projects happen when the provider has pre-built connectors and references ready.
Battery life, tag form factors, and human behavior
If you cannot fit the tag onto what you track, you do not have an RTLS. A pallet tag that looks small on a slide may snag shrink wrap in practice. A medical device tag with a great clip may still disappear if patients and staff find it aesthetically ugly or uncomfortable. Bring sample tags to the floor and let the people who will use them hold, mount, and push them. Observe, do not just ask.

Battery life is a system property, not just a tag spec. Update rates, signal strength, and environmental temperature swing consumption dramatically. A BLE tag that lasts two years reporting every 10 seconds in a lab may last six months in a freezer at minus 20 Celsius. UWB burst modes can drain faster in reflective rooms that force retries. Demand a battery budget model tied to your actual cadence, zone sizes, and ambient conditions, then pressure-test it during the pilot.

On maintenance, reality beats optimism. Who replaces batteries, when, and with what spares? Can you monitor “days remaining” for each tag and auto-generate a work order in your CMMS? Do you have a plan for tag abuse - forklift impacts, chemical exposure, autoclaves? Ruggedized tags often pay for themselves on the first avoided replacement cycle. I have seen a plant reduce lost-tag rates by 60 percent simply by switching from adhesive backs to riveted brackets and adding a tamper-evident strap.
Security, privacy, and data retention
Location is sensitive. In healthcare and high-security manufacturing, it can be regulated. Ask your rtls provider which data leaves the site, how it is encrypted in transit and at rest, and where it lives geographically. Role-based access, audit trails, and SSO through SAML or OIDC are basic requirements in most enterprises. If the platform supports worker location, align with HR and legal on visibility boundaries and retention windows. I have worked on deployments where historical breadcrumb trails were aggregated after 30 days for analytics but the raw trails were purged to mitigate privacy risk. Document these rules before your pilot, not after your first complaint.

Network-level security matters too. Gateways should support certificate rotation, signed firmware updates, and secure boot. Ask how the provider handles vulnerability disclosure and patch SLAs. If they stumble on these questions, assume you will carry that risk.
Total cost of ownership beats sticker price
TCO for real time location services bundles hardware, software, installation, commissioning, IT time, physical adjustments, training, and ongoing operations. A low-cost tag with a one-year battery and a manual replacement program can outspend a pricier tag with three-year life and remote diagnostics. Anchor density, cable runs, conduit, lifts, and permits add up faster than tags in many facilities.

Run a five-year model. Include spare pools at 5 to 10 percent, replacement cycles, support contracts, and planned expansions. If your business varies seasonally, bake in peak load costs for the back end. For example, a distribution center with holiday surges may need higher message throughput for two months. Some platforms price by message volume, others by asset count or zone count. Make sure your contract fits your pattern.

Service level agreements deserve line-by-line reading. What is the uptime commitment for the cloud back end? How are credits calculated and capped? What is the response target for P1 incidents? Ask for anonymized incident metrics from the last four quarters. An honest vendor will share average time to resolution and the top root causes they have eliminated.
Deployment logistics and change management
Even the best RTLS falls flat if the rollout collides with operations. In a hospital, quiet hours limit ceiling work. In a food plant, sanitation windows rule. In a warehouse, peak season freezes changes. Set a deployment calendar that respects these rhythms, and demand a detailed method of procedure that lists site entry, safety practices, testing steps, and rollback plans.

Training belongs in the plan, not as a footnote. Nurses, technicians, pickers, and supervisors need context, not just clicks. Explain why the system helps them, show a real-life scenario, and reinforce how to report issues. In one factory, we made a laminated, two-page guide that showed the four things operators should check when a tag appeared missing: physical check at the last known zone, tag LED state, battery estimate on the handheld app, and the “snooze” function if the asset was in maintenance. That simple tool cut support tickets by half.

Governance keeps the system healthy. Decide who owns data quality, who approves zone changes, and who signs off on firmware updates. Monthly health checks, including anchor heartbeat, tag battery distributions, and outlier asset movement patterns, catch issues before they bite.
Proof of concept without the rose tint
A pilot should mirror production enough to teach you something painful. Run it in the hardest zone first, not the easiest. If your worst area is a radiology wing with lead-lined walls, start there. Define success criteria in measurable terms - percentage of assets found within two minutes, percentage of false alerts per shift, average time between battery replacements - and publish them before the pilot begins.

Give the provider enough rope to show their process. Watch how they survey, place anchors, calibrate, and iterate. Solid teams reveal a playbook, not improvisation. Capture data on deployment time per anchor, failure rates, and rework. These become multipliers in your rollout plan. If a provider insists on a black-box proof and declines to discuss details, that is a signal.
Vendor viability and roadmap fit
The rtls provider you choose will ship updates, patch vulnerabilities, and add capabilities over years. You are buying a relationship as much as a system. Ask about their installed base in your vertical, typical deal sizes, and churn. Request two references that match your environment in scale and complexity. Ask those references what went wrong, not just what went right. Every project has surprises. You want a team that handles surprises well.

Roadmap alignment matters too. If you expect to add staff safety, forklift geo-fencing, or environmental sensing later, ask how those features integrate with the current platform. Look for a track record of on-time releases and backward compatibility. Providers who break APIs frequently create hidden costs in downstream systems and user retraining.
Data ownership, portability, and analytics
Clarify early who owns the data and in what format you can export it. A mature platform lets you pull raw events and enriched analytics via APIs and bulk export. If you ever need to switch vendors or add a data lake, you do not want your history trapped.

Analytics can turn location into insight. Cycle time variance across work cells, asset utilization heat maps, dwell-time anomalies by room, and arrival rate prediction are not pipe dreams if the data model is sound. But resist the lure of a fancy analytics demo if the basics - accurate zones, timely updates, and clean asset master data - are shaky. I prefer a phased path: stabilize presence and search, then add utilization and predictive layers once the ground truth holds for a quarter.
Edge cases worth surfacing
Real projects surface details that glossy brochures skip. Elevators can break track continuity if you do not plan for vertical handoff. Freezers can kill batteries and de-tune antennas. Autoclaves can brick tags unless they are rated and vented correctly. Forklifts can shadow anchors if you place them near mast paths. Magnetic badges on staff coats can rotate and hide an antenna pattern that your lab test never saw.

Plan for temporary layouts. A pop-up staging area during peak season can confuse a location engine trained on fixed zones. Can you add and retire zones quickly, with audit logs, and without a site visit? Can you create quarantine zones that re-route alerts and hide patient names from general views? The more dynamic your environment, the more you need flexible rtls management.
Cutting through marketing with a few direct questions
You can learn a lot by asking for specifics that map to lived experience. The most useful vendor conversations I have had hinged on simple, pointed questions.
Show me a deployment where you replaced or coexisted with another real time location system. What did you learn, and what would you do differently? Walk me through your most recent P1 incident affecting multiple customers. Root cause, timeline, and the change you made to prevent recurrence. How do you calculate battery life, and what field data backs it? Show a histogram from a live site with at least six months of data. What parts of your stack are your own IP versus licensed or open source, and how does that affect support and updates? If I add 30 percent more tracked assets during peak season, what changes in cost, performance, and support?
The way a provider answers will tell you as much as the answers themselves. Crisp, transparent responses suggest a mature operation. Evasion suggests trouble.
A brief buyer’s vignette
A regional health network asked us to evaluate three RTLS candidates for asset tracking and staff safety across five hospitals and twelve clinics. Budget pressure was real, and IT had strict rules about devices on the corporate network. One vendor offered a BLE solution with room-level presence, one offered UWB with sub-meter accuracy, and one offered a hybrid that used BLE for general assets and UWB only for ED and psych units where duress accuracy mattered.

We built a five-year TCO model. The pure UWB option had higher anchor counts and install cost but great accuracy. The pure BLE option had lower cost but struggled with room boundaries in old buildings with thick walls. The hybrid fit the outcomes: general equipment needed room presence and findability, while staff duress needed tighter resolution and faster updates.

The deciding factor was battery behavior. We asked for field distributions, not marketing claims. The hybrid provider produced data from two similar hospitals showing median badge battery life of 18 to 22 months at the planned update rates, with 90th percentile above a year. The BLE-only provider showed medians closer to 10 months in noisy environments. Multiplied by 4,000 badges and the labor to replace them, the difference offset the UWB anchor premium where we needed it. We chose the hybrid. Two years later, the sites report fewer false duress alerts, faster equipment search times, and an operations team that spends less than four hours a week on rtls management, mostly on planned maintenance.
Negotiation points that reduce risk
The last mile is your contract. Push for a pilot that transitions to production https://jsbin.com/cicudusapu https://jsbin.com/cicudusapu credits if success criteria are met. Lock in anchor and tag SKUs for a period to avoid mid-project substitutions. Include a clause that the provider supplies data export tools at no additional charge if you choose to exit. Tie a portion of payment to uptime and incident response targets during the first year.

On support, insist on named contacts during rollout and the first quarter after go-live. Record a joint escalation tree with roles and on-call windows. Agree on a change window policy for software updates, with pre-notification and rollback commitments.
What “good” looks like after go-live
When the dust settles, you should see a few signs that you chose well. Operations staff rely on the system without grumbling. Battery replacement becomes routine, not crisis-driven. Your integration feeds action - preventive maintenance triggers based on real usage, automatic updates to the asset register when something moves departments, nurse call alerts that include room and staff presence. Quarterly business reviews focus on metrics you care about - utilization, search time reduction, incident response - not just uptime and feature releases.

Most important, the provider behaves like a partner. They bring you ideas grounded in your data. They notice anomalies before you do and suggest why. They have a clear roadmap and invite you to influence it. When something breaks, they own it fast and fix it faster.

Choosing an RTLS is not about being dazzled by dots on a screen. It is about matching the physics, software, and human factors to the way your operation really runs. Ask the questions that reveal that match. The rest, the slides and the sizzle, can wait.

TrueSpot<br/>
5601 Executive Dr suite 280, Irving, TX 75038<br/>
(866) 756-6656