How much time does your operation lose searching for assets?
By James Ridgway · · 6 min read
Searching is one of the most normalised forms of operational waste.
A tool is not in the store. A pallet is not in its booked location. A test device was left with another team. Someone walks to the most likely area, asks a colleague, checks the next area and eventually finds it.
The work resumes, so the incident disappears into the day.
Across a site, those searches add up. More importantly, the people searching are often not the only cost. The asset may be needed to complete an order, continue maintenance, start a production step or meet a customer commitment.
To understand the commercial value of better asset visibility, measure both the search and the work waiting behind it.
Why search time is easy to ignore
Most organisations do not record "looking for assets" as a formal activity. The time is spread across roles and absorbed into normal labour.
The search may involve:
The person who first needs the asset.
Colleagues asked whether they have seen or borrowed it.
A supervisor who widens the search.
Stores or inventory staff checking the system record.
A manager deciding whether to replace, rent or work around it.
An individual incident may last only a few minutes. Frequency is what makes the cost material.
Calculate the direct labour cost
Start with a bounded asset class or workflow. Do not ask people to estimate every search across the whole organisation.
Use:
Search incidents × average people involved × average search hours × loaded hourly cost
For example, if a team records 30 searches in a month, each involving an average of 1.5 people for 20 minutes, the labour calculation is based on 15 person-hours — not simply ten elapsed hours.
Use the organisation's real loaded labour rate. The aim is not to create an impressive hypothetical saving. It is to establish a baseline that Finance and Operations recognise.
Add the cost of waiting work
Direct labour is usually the most defensible starting point, but it may not be the largest cost.
Ask what could not happen while the asset was unavailable:
Did a production or maintenance task wait?
Was a delivery or customer commitment delayed?
Did another team have to change its sequence of work?
Was alternative equipment used less efficiently?
Did someone order, rent or expedite a replacement?
Did a supervisor spend time coordinating the response?
Avoid automatically converting every minute of delay into lost revenue. Some work can be resequenced. Some capacity can be recovered. Keep search labour, operational delay and replacement cost as separate lines so the model remains credible.
Measure the search journey, not only its duration
Search data can reveal where visibility breaks down.
For a short observation period, record:
Asset or asset class.
Where the system said it should be.
Where it was eventually found.
When it was last knowingly used.
People involved.
Time spent searching.
Work delayed.
Whether a replacement or workaround was used.
The reason, if known, that the expected record was wrong.
Patterns matter. Assets repeatedly found in the same unexpected area may indicate a process or storage problem. Searches concentrated around a particular hand-off may reveal that the record is updated too late or not at all.
Better visibility should help improve the process, not simply help people search the same broken process faster.
What information makes a search shorter?
A dot on a map is not always necessary. For many operational searches, three pieces of information change the task:
Last-known location: the recognised zone where the item was most recently detected.
Detection time: how fresh that position is.
Supporting evidence: the sighting and movement history behind the answer.
This lets the team go to the most likely place first and judge whether the answer is recent enough to trust.
Movement history can also reveal direction. If an asset was last detected leaving Stores and then entering Staging, the search begins differently from one based only on its assigned home location.
For some use cases, last-known information is not enough. A safety-critical asset, autonomous process or item that moves continuously may justify a genuinely real-time, more precise position. But many searches do not need sub-metre tracking; they need a reliable answer to "Where was it last seen?"
Read last-known location or real-time tracking before paying for precision the search process does not require.
Search should become an exception, not a workflow
The strongest outcome is not merely a faster search screen. It is fewer searches.
Visibility data can expose:
Assets repeatedly left outside their expected zones.
Routes where items disappear from the record.
Items that have gone undetected and need checking.
Storage areas that create recurring confusion.
Asset populations that are too small, too widely shared or poorly controlled.
These insights support process changes: clearer return points, different hand-offs, better asset allocation or additional read coverage at the boundary where the trail currently breaks.
Define success before deploying
A first deployment should be measured against the current search problem.
Useful measures include:
Searches per week or month.
Median search time as well as the average.
Person-hours spent searching.
Percentage of searches resolved from the last-known record without a wider floor search.
Delayed tasks or orders linked to unavailable assets.
Emergency replacement or rental spend.
Repeat exceptions by asset, area or route.
Do not rely only on user satisfaction or the number of detections collected. The deployment creates value when it changes operational effort and availability.
Start with the assets people complain about
The best first population is often already known informally. It is the class of tool, equipment, container or stock unit that appears repeatedly in shift handovers, management conversations and local workarounds.
Check that the population also has a trackable movement pattern and a cost worth addressing. Then map where it moves, where searches begin and which last-known answer would materially shorten the task.
A bounded first deployment is easier to justify when the baseline is visible and the operational question is specific.
Give teams a better starting point
Waytrail lets teams search across assets, tags and locations, then see where an item was last detected, when it was seen and the evidence behind that position. Recent movement history helps them go to the most likely location rather than repeating a broad floor search.
The commercial value comes from returning people and assets to productive work sooner — and from identifying the recurring process problems that made searching necessary.
Explore how Waytrail helps teams find assets faster.
Choose one asset population and measure the searches it creates. We'll help you understand what answer would shorten those searches and which deployment could provide it.