Where Is It Right Now? How to Track Assets Across Multiple Sites

Someone needs a torque wrench, a diagnostic scanner or a service van and asks a simple question: where is it right now? In a single-site business the answer is a short walk. In a company with a dozen locations, it is usually a round of phone calls, a spreadsheet nobody fully trusts, and a guess.

Asset tracking across multiple locations is rarely a technology shortage. Most companies already own an asset register, an ERP, a maintenance system and a helpdesk. The trouble is that each holds a different version of the truth, and none is updated at the moment equipment actually moves.

This article covers why records drift, what that costs, how to diagnose the gap in your own operation, and how to keep one live record of location, custodian, condition and status for the equipment, tools and vehicles that travel between sites. The practical steps come first. The closing sections explain how The Ninjaz Group approaches the problem.

Why the record goes stale between sites

Assets rarely lose their location through carelessness. They lose it because the process asks people to do paperwork after the move, when the next job is already waiting.

Three patterns show up again and again. First, moves happen informally. A technician borrows a generator from the neighbouring site on Friday, planning to return it on Monday. Nobody records the loan, because the official route is a transfer form needing two approvals. Second, ownership of the data is split. Finance holds the fixed asset register, with cost centres and depreciation. Operations keeps a spreadsheet. Maintenance holds service history in its own system. IT tracks laptops through the helpdesk. Each system gives the same item a different identifier. Third, status lives in conversation. "It's broken, someone's looking at it" is true for a week and recorded nowhere.

Consider a group with twelve locations that shares a pool of specialist equipment: diagnostic scanners, pressure testers, two trailers and four service vehicles. The ERP lists each item against the site that bought it, and Finance depreciates it there. The maintenance system tracks servicing by serial number, but the serial number is not stored in the ERP. The helpdesk receives a ticket reading "the scanner at site seven is faulty", which names a room, not an asset. When site four asks for a scanner, three systems give three answers: site seven, site two, and "disposed". The real scanner is in a van, waiting for a repair nobody scheduled.

No single system is wrong by its own logic. The failure sits in the gaps between them, where no shared identifier links the asset register, the maintenance history, the open ticket and the person holding the item.

What it costs when nobody knows

The cost of lost visibility is spread thin, which is why it often goes unmeasured. It shows up in several places.

Time. Site managers, dispatchers and technicians spend hours chasing equipment by phone and message. Each search is small. Across twelve sites and a working year, it becomes a standing tax on skilled people.

Inventory and capital. When nobody can find the second pressure tester, someone buys a third. Idle equipment sits in one site's storeroom while another site rents the same thing. The balance sheet carries items that may no longer exist.

Mistakes and risk. Calibrations lapse and inspections get missed because the item was never where the schedule assumed. A vehicle due for service keeps working because its record says it is at a different site. In regulated or safety-critical work, that is more than an inconvenience.

Lost work and frustrated customers. A technician arrives at a customer's premises without the right tool and must book a second visit. A job is delayed because the one suitable machine is somewhere in transit. The customer sees a company that cannot keep its own promises.

Burnout. The people who "know where everything is" become a single point of failure. They get the calls on weekends, and when they leave, the knowledge goes with them.

Finally, there is the quarterly reckoning. Finance and operations compare lists, find discrepancies, and write items off or hunt for them, and the same drift begins again.

How to diagnose your own situation

Before buying anything, measure the gap. A one-week test will tell you more than a software demo.

1. Pick thirty items across categories: high-value tools, shared equipment, vehicles, and a few low-cost items that are easy to lose.
2. Ask every system that claims to hold them (asset register, ERP, maintenance system, helpdesk, team spreadsheets) where each item is, who has it, and what state it is in. Record each answer.
3. Verify the physical reality with site leads over a day or two. Photograph the items if you can.
4. Compare the answers on four fields: location, custodian, condition and status.
5. Sort every mismatch into one of four groups: moved without a record, record is wrong, duplicate or missing identifier, or genuinely unknown.
6. Trace each mismatch to the handoff that failed. Was it a loan between sites, a repair, a vehicle swap, a disposal?

Read the pattern. If mismatches cluster around transfers between sites, you have a process problem at the moment of movement. If systems disagree with each other but each is internally consistent, you have an integration problem. If many items are simply unknown, you have an identification problem: tags, serial numbers or naming conventions are missing. Most companies find a mix of all three, but one usually dominates, and that tells you where to start.

What one live record should hold

The aim is not a better spreadsheet. It is a single record per asset that every team and system reads from and writes to. At minimum, it should hold:

• Identity: one primary ID, linked to the serial number, the finance asset number and the maintenance reference, so no system has to guess which item another one means.
• Location: the site, the place within the site where that matters, or an explicit "in transit" state with origin and destination.
• Custodian: a named person or team who has accepted responsibility, not just the site that owns the item on paper.
• Condition: the last inspection, known defects, calibration or service due dates, and any open fault tickets.
• Status: available, reserved, in use, in repair, in transit, or retired, with a small, agreed list of values.
• History: every change, with who made it and when, so questions about the item can be answered without detective work.

Two design points matter. Location and custodian should change together, as one event. A transfer needs a handover and an acceptance, and until the receiver accepts, the item is in transit and the sender still answers for it. And condition should come from the systems that already know it. A fault ticket raised in the helpdesk should flip the status to "in repair" without anyone retyping it.

Matching the tracking method to the asset

Barcode, RFID and GPS each solve a different part of the problem. Few companies need all three, but most need more than one.

Barcode and QR labels are inexpensive and work well for tools and portable equipment that pass through a handover point. They depend on someone scanning, so they suit workflows where scanning is part of getting the item: a tool crib, a site store, a vehicle checklist. Adding a quick scan to every check-out and return is the simplest way to start.

RFID reads tags without line of sight, so it suits places where many tagged items pass a fixed point, such as a yard gate, a warehouse door or a storeroom. It reduces reliance on individual discipline, but tags and readers cost more, and reader placement needs thought. It earns its place where volume or value is high.

GPS suits vehicles, trailers and powered equipment that move on their own or are transported far from any scanning point. It gives continuous position, but it does not tell you who is responsible for the item or what condition it is in. A dot on a map is a location, not a custody record.

Whatever the method, the signal has to land in the shared record. Field tools matter here: a mobile app that lets a technician scan at handover, confirm condition with a photo, and work offline at a remote site will be used. A form that requires an office desktop will not. Connect the helpdesk so faults are raised against an asset, not a room. And connect Finance so transfers between cost centres or entities, and disposals, follow the same record that operations sees, rather than being reconciled later.

Rules that keep the record true

Technology captures events, but a few simple rules decide whether the record stays accurate.

Start with the category that hurts most, usually shared, high-value or compliance-relevant equipment, not everything at once. Give every asset one ID and retire the parallel naming schemes. Make the scan or the system entry part of the physical handover: no scan, no release. Name a custodian for every item, and make "unassigned" a state that triggers a question. Define the status list once and resist adding values.

Then add exception alerts, because the record's value is in what it flags. Useful ones include an item not seen for a set period, a loan past its return date, a service or calibration coming due, and an asset marked available at a site that has no record of receiving it. Review these weekly at the site level and monthly across the group. The goal is for the discrepancy to surface in days, not at the annual count.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner for multi-location enterprises, and asset visibility is the kind of problem that sits between systems, which is where its work is focused.

Engagements usually start with a Blueprint. We map how the operation actually works, and find where work is done twice, where data goes stale and where money leaks. For assets, that means tracing the real path of equipment between sites and finding which handoffs break the record. The client keeps the map, whatever happens next.

The Build & Link stage then connects what you already run. There is no rip-and-replace, and software you have already paid for stays. Through Managed Link, the integration layer Ninjaz builds, owns and maintains, the ERP, inventory or warehouse system, maintenance system, helpdesk and finance systems are connected through the Ninjaz Operating Platform. Its unified data layer holds one record per asset, so the asset register, the maintenance history and the open ticket describe the same item. Inventory and asset views show equipment across sites, and the Command Center surfaces live KPIs and alerts across locations, such as overdue returns or assets not seen. Workflow automations can route a transfer for acceptance or update status when a fault is logged. Team chat boards tied to records keep the conversation about an item attached to the item itself. Roles and an audit trail show who changed what.

After go-live, Managed Business Operations covers the day-to-day running and managed IT, so the integrations and workflows keep working as sites, systems and teams change.

A realistic note on limits: a platform cannot make people scan a tool. The tracking method, labels, and handover rules still need to fit how your sites work. How scan, location and condition events from your chosen tracking approach reach the shared record is something we scope in the Blueprint, based on the systems and hardware you have and what the operation needs. The platform's job is to keep the record in one place and keep it consistent, so the discipline on site is worth the effort.

Start with where it is right now

If you cannot answer "where is it right now?" in under a minute for your most important equipment, the cause is almost certainly in the handoffs and the gaps between your systems, not in any single tool. Run the thirty-item test and see which of the three problems dominates.

If you would like help mapping where your asset records break down, book a consultation and we will walk through your sites, systems and equipment flows. If you would rather see what a unified asset record and cross-site view look like in practice, take a look at the platform demo.