Last-known location or real-time tracking: which answer do you actually need?

"Real-time tracking" is often written into requirements before anyone defines the decision it needs to support.

It sounds reassuringly complete: a live view of every asset, everywhere. But greater precision and freshness require infrastructure, power, engineering and cost. If the operation only needs to know which zone an item last entered, a continuously updated sub-metre position may add expense without changing the decision.

The right requirement begins with the question the team must answer.

Location is a spectrum

Asset visibility is not a binary choice between "tracked" and "not tracked". Different deployments provide different levels of evidence.

Actual performance depends on the technology, environment and deployment design. The table describes the requirement, not a guarantee attached to a particular acronym.

What last-known location means

A last-known location is the recognised operational zone associated with the most recent reliable detection.

It should be accompanied by:

• The time of the detection.

• The sighting or event that supports it.

• Relevant confidence or interpretation information.

• Recent movement history.

The timestamp matters because a last-known position does not prove the asset remained there. A location seen two minutes ago and one seen two weeks ago should not be presented with the same confidence.

For many searches and investigations, this is enough to change the task. The team can go to the most likely zone, understand the route into it and judge whether the evidence is fresh enough to act on.

When last-known information is enough

Last-known tracking can be commercially appropriate when:

• Assets move through defined doorways, routes or hand-off points.

• The main need is to shorten a search.

• Teams investigate movement after an exception.

• Zone-level stock or container visibility is sufficient.

• A large population needs low-cost tags.

• Continuous position between meaningful points would not change the action.

Examples include returnable containers passing goods-out, tools moving between stores and work areas, or pallets entering staging zones.

The value comes from reliable coverage of the points that matter, not from drawing an artificial live dot between them.

When real-time precision is worth considering

A more continuously updated or precise position may be justified when:

• Safety depends on knowing whether an asset or person is within a boundary now.

• Automated equipment needs location as an input.

• The asset moves continuously within an open space where choke-point detections are insufficient.

• Search areas remain too large for zone-level evidence to be useful.

• The asset population is small and valuable enough to justify higher tag and infrastructure costs.

• The operational decision loses value if the position is even briefly stale.

The requirement should state the action, update frequency, precision and consequence of error. "Real time" on its own is not specific enough to design or evaluate a system.

Precision has an economic cost

More precise or frequently updated tracking can involve:

• More expensive powered tags.

• Battery monitoring and replacement.

• Denser gateway or anchor infrastructure.

• More detailed site calibration.

• Greater installation and maintenance effort.

• More data to process and govern.

• More demanding coverage and availability expectations.

These costs can be justified. The mistake is assuming they are automatically justified because the technical answer appears better.

Compare the incremental cost with the operational decision it improves. If room-level rather than zone-level location shortens a frequent search materially, the difference may pay for itself. If sub-metre precision does not change where anyone goes or what anyone does, it may not.

Accuracy is not the only dimension

Buyers often focus on positional accuracy and overlook:

• Coverage: Where can the system produce the intended answer?

• Freshness: How recently was the position supported by evidence?

• Population: How many assets can economically carry the required tag?

• Power: Who will maintain batteries and monitor their condition?

• Environment: How do materials, layout and interference affect performance?

• Reliability: How are missed, duplicate or low-confidence detections handled?

• Explainability: Can a team inspect the evidence behind a position?

• Integration: Can the answer reach the systems and workflows that need it?

A less precise but widely deployed and well-understood record may create more operational value than a precise system limited to a small or poorly adopted population.

One operation can need more than one approach

The choice does not have to be uniform across every site and asset.

Passive RFID may record large populations crossing defined boundaries. BLE may provide area-level presence for roaming equipment. UWB may provide higher precision for a smaller critical population.

The important architectural question is whether these detections can feed a consistent asset identity, location model, history and integration layer. Teams should not need a separate operational process for every radio technology.

Read RFID, BLE or UWB for a technology comparison grounded in range, environment, precision and economics.

Write the requirement as a decision

Replace "We need real-time tracking" with a requirement such as:

When a maintenance team requests a shared tool, it should be able to identify the most recently detected operational zone and detection time quickly enough to avoid a broad floor search.

Or:

When a mobile asset enters a defined safety area, the control system needs a sufficiently current and precise position to trigger the agreed response.

These statements can be tested. They also make it easier to select technology without confusing greater technical capability with greater commercial value.

Buy the answer the operation can use

Waytrail maintains a consistent asset record, floor-plan location model, last-known state and movement history while detections can come from RFID, BLE, UWB or other approaches. This allows the deployment to be shaped around the use case rather than a single technology assumption.

For teams trying to find assets faster, a traceable last-known position may be the right answer. For a precise safety or automation use case, it may not be. The decision should follow the consequence, environment and economics.