Choosing an independent RTLS consultant: what to checkYour RTLS consultant may be tied to a supplier.

What an RTLS consultant does

A good RTLS consultant owns the hard parts of a location programme: validating the use case and the accuracy you genuinely need, choosing the right radio for the physics,

designing an architecture that scales, integrating it cleanly into your WMS, ERP, EMR or MES, and governing the rollout so it ships.

The job is as much about saying “you don’t need that” as recommending what you do, stopping you over-specifying precision or buying infrastructure you’ll never use.

Why independence matters

Most “advice” in this market comes from companies that also sell the hardware or the platform. That is not advice. It is sales.

We don't sell hardware, so our advice stays independent. The recommendation is driven only by your use case, budget and risk.

When to bring one in

• Before an RFP, to write requirements that get comparable, accurate supplier bids
• When a pilot stalled or missed its accuracy target and you need a diagnosis
• Before a multi-site rollout, so a single-site success actually scales
• When the board wants a defensible business case and payback, not a supplier deck

What you get from a TRACIO engagement

• A clear recommendation: the right technology, architecture and integration plan
• A gate-governed delivery plan so spend stays tied to evidence
• Independent selection: we work for you, not for the technology providers
• Plain-English deliverables your whole buying group can act on

Independent RTLS consulting: architecture before anchors

An RTLS consultant exists to stop locating programmes from starting with a preferred radio and reverse-engineering a use case.

What a serious engagement covers. Use-case and KPI framing; technology shortlist (UWB, BLE AoA, Passive RFID, hybrid, occasionally Wi-Fi or GNSS outdoors); RF survey oversight; anchor/locator density challenge; integration patterns to MES/WMS/EMR/CMMS; cybersecurity and OT segmentation notes; pilot success criteria; TCO and rollout phasing. Deliverables should be readable by operations, finance and IT, not only by RF engineers.

Why independence changes the outcome. Resellers optimise for attach rate of their anchors and software seats. Independent advisors optimise for the sparsest stack that still hits the locating KPI. That often means hybrid designs, lower density, or even deciding RTLS is the wrong buy this year compared with Passive RFID portals or process redesign.

When to bring a consultant in. Before RFP; when two suppliers disagree on density; when a pilot stalled; when IT/OT cannot agree on data ownership; or when the board asks for a risk-adjusted business case. Waiting until after contracts are signed turns consulting into remediation.

Engagement models and red flags when hiring RTLS advice

Red flags: accuracy claims without percentiles in writing; density recommendations without a survey; one radio for every zone; integration marked “phase 2”; any fee tied to hardware volume. Green flags: a clear “do not deploy” list, hybrid architectures, and comfort facilitating disagreement between operations, IT and finance.

Ask for anonymised examples of density reductions, pilot gates, and recoveries. You are buying judgment under uncertainty. Evidence of that judgment is fair diligence.

Independence test in one question

Ask any RTLS advisor: “Where on our site would you refuse UWB and specify BLE or Passive RFID instead?” Competent independent consultants answer with zone maps and KPI thresholds. If every zone somehow needs their densest radio, keep looking.

Field note

Bring the consultant in before the RFP freezes the architecture. After award, they can only remediate.

Frequently asked questions

• How we work & fees
• Pricing by service
• Find your technology
• Compare technologies
• Supplier comparisons
• Case studies