Programme rescue: when the RTLS or RFID pilot never became the system of record.Pilot stalled before it became the system of record?
Stalled RTLS pilot or failed RFID project recovery. We diagnose, re-scope and finish the programme, or tell you to stop spending. Independent; no hardware to protect.
Programme rescue is our flagship engagement for clients with a deployment that's stalled, over-budget, under-performing or politically toxic.
Independent diagnosis, root-cause analysis, recovery plan, and (where required) supplier renegotiation and re-delivery. Our advisers have worked on stalled deployments at every scale, before TRACIO and since.
Free 30-minute call with an adviser · written proposal with the price after · fixed-scope engagements from £3k.
Rescues fail when politics outrun a written failure analysis.
Blame-free autopsy
Separate supplier, RF, process and integration causes, or you replace hardware and keep the disease.
Stabilise then redesign
Stop the bleeding (coverage, false alarms, data lies) before a new architecture fantasy.
Re-baseline KPIs
Old success criteria may be why it failed. Reset what “good” means with the sponsor.
Read why RTLS pilots stall and what to look at first. We don't sell hardware, so our advice stays independent. Read why our advice stays independent.
When programme rescue is the right engagement
Typical signals: the pilot delivered against supplier metrics but didn't move any business KPI; production rollout has stalled or fragmented across sites; supplier and integrator are pointing fingers at each other;
capex is committed but ROI hasn't materialised; the executive sponsor is losing patience; an audit or steering committee has flagged the programme as red.
If any of these match, programme rescue is the engagement. The diagnostic covers UWB, BLE-AoA, RFID, AGV/AMR and hybrid stacks in manufacturing, healthcare, logistics, defence and retail.
The diagnostic: what we look for in week 1
We start with a structured diagnostic across six dimensions. Scope and success criteria: what was the deployment supposed to deliver, and was it ever quantified? Most stalled programmes never had measurable success criteria.
Technology fit: was the chosen radio appropriate for the environment and use case? RF site survey at production load tells us in days. Supplier and integrator performance: independent review of supplier and integrator delivery vs contract; the asymmetric-information traps.
Integration architecture: does the data flow into the systems that drive the business outcome? Most underperforming programmes have broken or absent integration.
Operational fit: do the people on the shop floor or in the ward use the system? Adoption issues are usually scope issues in disguise. Commercial position: what are the contractual options for renegotiation or termination?
Root-cause analysis: the five patterns we see
Five failure modes account for most stalled deployments. Scope misalignment: the deployment was scoped against a technology rather than a business outcome. "We want UWB" instead of "we want a 12% reduction in WIP delay".
Wrong radio: supplier sold a technology that doesn't fit the environment (UWB in dense metal without sufficient anchor density; BLE-AoA in heavy multipath; RFID at unstable read accuracy).
Integration gap: data is captured but doesn't flow to WMS/MES/EMR. Events don't drive any operational change. Supplier lock-in pricing: year-2 commercial terms make scale-out uneconomic; client is held hostage to extension capex.
Adoption failure: front-line operators don't use the system because workflow change wasn't designed; system reports look right, KPIs don't move. We diagnose which pattern (or combination) applies in week 1.
The recovery plan: built in weeks 2-3
The recovery plan is concrete and time-boxed. Scope correction: redefine success criteria as measurable business KPIs (not technology metrics), with executive sponsor sign-off.
Technical remediation: targeted changes (adding anchors, switching radio in specific zones, fixing integration, swapping tags).
Supplier and integrator action: renegotiate scope, commercials and SLAs based on root-cause findings; in rare cases, recommend replacement. Operational change: workflow design, change management, training for adoption.
Re-baseline: new milestones, new acceptance criteria, new ROI model. The plan is delivered to the executive sponsor and steering committee as a single document with a transparent assumptions log.
Supplier renegotiation: independent and credible
Programme rescue often involves renegotiating with the incumbent supplier or integrator.
We renegotiate commercial terms, scope, SLAs and milestone structures with RTLS, RFID and AGV/AMR suppliers on your behalf.
Where the relationship is unrecoverable, we recommend supplier replacement and run a structured re-procurement using RTLS RFP outline: free, independent and RTLS supplier evaluation: what to score.
Re-delivery: phase 3 of the TRACIO programme method, adapted
Once the recovery plan is signed off, re-delivery follows phase 3 of the TRACIO programme method (Production rollout) with two adaptations. Tighter gates: we add additional acceptance gates between the previous failure point and full rollout, usually three to five additional gate reviews.
Independent validation: we validate each gate independently rather than relying on supplier self-reporting. Phased expansion: rollout extends to additional sites only after the rescued site demonstrates business KPI delivery for an agreed period (typically a quarter).
How long, and how much
Diagnostic: a paid 1-week engagement. Recovery planning: 2-3 weeks. Supplier renegotiation: 4-8 weeks depending on commercial complexity. Re-delivery: 12-36 weeks depending on scope. Total: 5-13 months end-to-end for the typical mid-scale rescue.
Commercials: scoped per project for diagnosis and planning; time-and-materials or success-based for execution.
What we need from you
- A named sponsor with authority to stop, re-scope or continue the programme
- The contracts, SOWs, change requests and SLAs with the supplier and integrator
- System logs, accuracy and read-rate reports, and the original pilot criteria (if there were any)
- Read access to the location platform and the systems it feeds
- Time with the people who run it: operations, IT/OT and the project team
- Site access for a walkthrough under normal operating load
Why hire us rather than the incumbent supplier
Three reasons. Independence: we're not the supplier that built the problem, so we have no incentive to hide root causes.
We work for you, not for the technology providers. See our independence policy. Pattern recognition: the same failure modes recur across suppliers, industries and geographies, and our advisers have spent two decades seeing them.
A structured diagnostic finds in a week what can take a supplier or internal team months. Credibility on both sides: suppliers and integrators take us seriously because we're rigorous and fair. That makes renegotiation faster and fairer.
Programme rescue vs supplier TAC, SI “stabilisation” and Big-4 recovery.
When a locating pilot stalls, the incumbent supplier offers TAC and a paid health-check that rarely questions the original design. The SI offers a stabilisation change-request that extends the same scope. A Big-4 recovery workstream re-baselines governance without always re-opening the RF and integration root causes. Reseller partners propose rip-and-replace toward a different catalogue.
What programmes get wrong: asking the party who sold the original architecture to grade their own homework, or replacing hardware before diagnosing whether identity, multipath, process adoption or KPI definition was the actual failure.
TRACIO rescue is independent by construction: no hardware to protect, no licence renewal to defend. Diagnosis is paid and blunt: finish, re-scope, or stop. Most rescues keep the incumbent where the equipment can still deliver. Replacement is a managed exception, not the default pitch.
Frequently asked questions
Will you blame the supplier we already chose?
Not by default. We diagnose root causes objectively, and they often include client-side scope, integration and adoption decisions as well as supplier performance.
Where the supplier is genuinely at fault, we're direct about it, but the most common finding is a mix of issues across the engagement.
Do you take fees from the incumbent supplier for the rescue?
Never. We work for you, not for the technology providers. See our independence policy.
What if we want to replace the incumbent supplier?
We run a structured re-procurement using RTLS RFP outline: free, independent and RTLS supplier evaluation: what to score. Most rescues don't end in replacement, but when they do, we manage the transition rigorously.
Can you diagnose a stalled RTLS pilot before a full programme rescue?
Yes, many engagements start with a paid 1-week diagnostic that produces a brief root-cause report and a recommendation on whether full rescue is needed. Clients then decide whether to proceed.
How do we engage you if our incumbent supplier is in the room?
Politely and transparently. We tell the supplier up front that we're an independent advisor and that we'll be diagnosing root causes objectively. Most suppliers prefer this to ambiguity. The rare cases where suppliers won't co-operate become input to the recovery plan.
What does failed RFID project recovery typically achieve?
The aim is a programme that delivers against its original or revised ROI, or a clear decision to stop.
We're selective about which engagements we take. We don't accept rescues where the technology fundamentally can't deliver the use case (in those rare cases, we recommend abandoning, which is also a successful diagnosis).
Last updated: