Locating programmes the board can sponsor without buying a science project.

Three numbers and one owner: payback or risk metric, worst-case exit cost, and the executive who owns the KPI after go-live. Everything else is decoration.

See CFO and Programme Method for the gate model.

Reseller-led programmes optimise for close. An independent advisor holds the SOW and the success criteria — and can recommend walking away at gate 1.

Detailed client references are available under NDA.

Dashboard vanity, unpaid integration, and safety claims that do not survive an audit. We design against those failure modes first.

• What is the single KPI this programme is accountable for in year one?
• What is the exit cost if gate 2 fails — hardware stranded, licences, integration?
• Who owns the KPI after go-live: operations, EHS, clinical, or IT/OT?
• Which named references can we speak to under NDA?

Bring those answers (or the gaps) and we leave with a scoped next gate — not a slide deck.

Boards do not need another technology narrative. They need a thesis: which KPI moves, by when, at what worst-case exit cost, and who owns it after go-live. We write that page before the RF survey — then refuse to scale hardware until gate evidence exists.

Typical gates: (1) use-case and success criteria locked, (2) live-floor pilot against a baseline, (3) integration and security signed, (4) scale with a kill switch. See Programme Method and CFO for the numbers pack.

Independent architecture options (not a single-vendor stack), a risk register that includes RF and change-management failure modes, and named references under NDA. Homepage logos are real clients; case studies remain composite patterns unless labelled otherwise.

If the thesis does not survive contact with the plant, we say so at gate 1. That is the point of independence — no reseller margin on walking away.

Vendor decks sell precision. Boards buy risk-adjusted outcomes. A locating programme (RTLS, RFID, or hybrid) survives capital review when four criteria are explicit before any radio is chosen:

• Outcome lock — one primary KPI (search labour, downtime, utilisation, safety response, or compliance evidence) with a baseline measured on your floor, not a vendor benchmark.
• Exit economics — worst-case cost if the pilot fails: stranded anchors, licences, SI change orders, and internal labour. If that number is blank, the business case is incomplete.
• Ownership after go-live — named ops, EHS, clinical or plant owner for the KPI, plus IT/OT for the estate. Orphan programmes die in year two.
• Architecture neutrality — at least two viable technology paths documented so the board is not hostage to a single SKU or AMR add-on.

Consultancies often pitch transformation programmes; hardware vendors pitch platform breadth; SIs pitch delivery capacity. Boards should insist the first artefact is a one-page thesis with gates — not a bill of materials.

Independent reviews of stalled RTLS and RFID programmes keep returning the same patterns. Design against them before scale:

• Dashboard vanity — live maps that never change a shift decision or a board KPI.
• Unpaid integration — location events that never reach MES, WMS, EMR or EHS systems of record.
• Lab accuracy, plant fiction — centimetre claims that collapse under metal, multipath and full production load.
• Lock-in recovery — year-1 discount recovered through tag refresh, change orders and multi-site premiums.
• Safety theatre — mustering or lone-worker claims without drill evidence or audit-grade retention.

Industrial RTLS vendors themselves increasingly stress starting from measurable operational friction and full five-year TCO — not brochure ROI. The board's job is to force that discipline even when the seller is persuasive.

• What single year-one KPI will you put your fee or margin against — and what is our measured baseline?
• Show production-load accuracy in an environment like ours (metal, racking, RF noise), not a lab brochure.
• What is five-year TCO including tags, batteries, integration, support and change orders for two additional sites?
• Who owns MES/WMS/EMR/EHS integration in writing, and what happens if events do not land in those systems?
• Can we exit at a named gate without buying the next hardware tranche?
• Do you earn margin on hardware, AMR fleets or perpetual licences — and how does that affect the recommendation?

TRACIO is an independent locating advisor. We do not sell RTLS hardware, RFID labels, AMR fleets or a platform SKU. We write the thesis, run gate-driven pilots, score vendors and SIs against your criteria, and can recommend walking away at gate 1 with no reseller conflict. The board gets architecture options, a risk register that includes RF and adoption failure modes, and NDA references — not a channel close.

Boards do not need another technology narrative. They need a thesis: which KPI moves, by when, at what worst-case exit cost, and who owns it after go-live. We write that page before the RF survey — then refuse to scale hardware until gate evidence exists.

Typical gates: (1) use-case and success criteria locked, (2) live-floor pilot against a baseline, (3) integration and security signed, (4) scale with a kill switch. See Programme Method and CFO for the numbers pack.

Independent architecture options (not a single-vendor stack), a risk register that includes RF and change-management failure modes, and named references under NDA. Homepage logos are real clients; case studies remain composite patterns unless labelled otherwise.

If the thesis does not survive contact with the plant, we say so at gate 1. That is the point of independence — no reseller margin on walking away.

Vendor decks sell precision. Boards buy risk-adjusted outcomes. A locating programme (RTLS, RFID, or hybrid) survives capital review when four criteria are explicit before any radio is chosen:

• Outcome lock — one primary KPI (search labour, downtime, utilisation, safety response, or compliance evidence) with a baseline measured on your floor, not a vendor benchmark.
• Exit economics — worst-case cost if the pilot fails: stranded anchors, licences, SI change orders, and internal labour. If that number is blank, the business case is incomplete.
• Ownership after go-live — named ops, EHS, clinical or plant owner for the KPI, plus IT/OT for the estate. Orphan programmes die in year two.
• Architecture neutrality — at least two viable technology paths documented so the board is not hostage to a single SKU or AMR add-on.

Consultancies often pitch transformation programmes; hardware vendors pitch platform breadth; SIs pitch delivery capacity. Boards should insist the first artefact is a one-page thesis with gates — not a bill of materials.

Independent reviews of stalled RTLS and RFID programmes keep returning the same patterns. Design against them before scale:

• Dashboard vanity — live maps that never change a shift decision or a board KPI.
• Unpaid integration — location events that never reach MES, WMS, EMR or EHS systems of record.
• Lab accuracy, plant fiction — centimetre claims that collapse under metal, multipath and full production load.
• Lock-in recovery — year-1 discount recovered through tag refresh, change orders and multi-site premiums.
• Safety theatre — mustering or lone-worker claims without drill evidence or audit-grade retention.

Industrial RTLS vendors themselves increasingly stress starting from measurable operational friction and full five-year TCO — not brochure ROI. The board's job is to force that discipline even when the seller is persuasive.

• What single year-one KPI will you put your fee or margin against — and what is our measured baseline?
• Show production-load accuracy in an environment like ours (metal, racking, RF noise), not a lab brochure.
• What is five-year TCO including tags, batteries, integration, support and change orders for two additional sites?
• Who owns MES/WMS/EMR/EHS integration in writing, and what happens if events do not land in those systems?
• Can we exit at a named gate without buying the next hardware tranche?
• Do you earn margin on hardware, AMR fleets or perpetual licences — and how does that affect the recommendation?

TRACIO is an independent locating advisor. We do not sell RTLS hardware, RFID labels, AMR fleets or a platform SKU. We write the thesis, run gate-driven pilots, score vendors and SIs against your criteria, and can recommend walking away at gate 1 with no reseller conflict. The board gets architecture options, a risk register that includes RF and adoption failure modes, and NDA references — not a channel close.