How to Track Equipment Across Job Sites
Ask a yard owner where every unit is right now and you will usually get a confident answer that turns out to be half right. The iron that left on a flatbed weeks ago is on a site somebody renamed, billed to a customer who subleased it to a sister crew, and nobody updated the board. Losing track is not a paperwork problem — it is a margin problem, a safety problem, and a renewal problem all at once. This guide lays out how to keep every unit tied to a known site and a known customer at any moment, and how to spot the gaps before they become an off-rent excavator sitting in the dirt that nobody is paying for.
Why a unit list is not a location list
Most yards can tell you what they own. Far fewer can tell you where each piece is and who has it, because those are different questions answered by different records. A unit list lives in your asset register; a location list lives in your dispatch board, your drivers' heads, and a stack of delivery tickets. When those drift apart, you get phantom units — iron the system thinks is in the yard but is actually on a pad two counties over. The fix is to treat location as a property of the unit that changes on every move, not a one-time field. Every delivery, pickup, and transfer should write a new location to the same record, so the answer to "where is it" is one lookup, not a phone tree.
Match every unit to a site, and every site to a customer
A customer is not a location. A single oilfield operator might run several pads at once, each with its own access road, its own foreman, and its own iron. If your records only say a telehandler is "out with" that customer, you cannot answer which pad it is on when the foreman calls about a flat. Structure your records so each unit points to a specific site, each site rolls up to a customer, and the customer can hold many sites at once. EquipFlow's accounts-and-sites model is built around exactly this — a parent account with its own branch sites underneath — so a renewal conversation can be had site by site instead of as one undifferentiated lump.
The handoffs where tracking actually breaks
Iron does not get lost in the yard. It gets lost at the handoffs — when a driver drops a unit and the ticket sits in the truck for days, when a customer moves equipment between their own pads without telling you, when a unit comes off one job and goes straight to the next without ever touching the yard. Each of those is a moment where the record should change and usually does not. Decide who owns each handoff and make the update part of the move, not an afterthought. A delivery is not complete until the new site is recorded. A field transfer between a customer's pads is a billing event, not a courtesy, and it needs a confirmation from someone on the ground.
Use the field to confirm what the office believes
The office record is a claim; the field is the truth. The gap between them is where money leaks. A unit marked on-rent that the customer quietly stopped using is revenue you are still owed but not collecting. A unit marked returned that is actually still on a pad is liability you are carrying for free. Close the gap with field confirmation: a quick check at delivery, at pickup, and on any move that records location and condition against the right site. When the person standing next to the iron confirms where it is, the office stops guessing. Tie that confirmation back to inventory so the same record drives both your availability picture and your billing.
Reading your fleet by site, not just by unit
Once location is reliable, the useful view flips. Instead of asking where one excavator is, you ask what every customer is holding and for how long. That site-level read surfaces the iron that has gone quiet — units sitting on a pad past the job's active phase, racking up standby risk or quietly idle while a second customer waits on that exact class of machine. It also tells you which sites are due for a check-in before a renewal lapses. A yard that can pull up a customer and see every site and every unit underneath it negotiates from knowledge. A yard working off a unit list and memory negotiates from hope.
Key takeaways
Location is a property of each unit that must change on every move — a delivery is not done until the new site is written to the record.
A customer is not a single location; tie each unit to a specific site that rolls up to the customer, so one operator with several pads is never a guessing game.
Iron gets lost at the handoffs, not in the yard — assign an owner to each delivery, pickup, and field transfer and make the record update part of the move.
Field confirmation at delivery and pickup closes the gap between what the office believes and what is actually on the pad, where most billing leaks live.
A site-level read of your fleet surfaces quiet units and lapsing renewals that a unit-only list will always hide.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“What is the fastest way to start tracking units across job sites without a full system?”
Begin with the handoffs, not the whole fleet. Pick the single move that breaks most often — usually field transfers between a customer's own pads — and require a confirmation that records where the unit went and who has it. One reliable update at the riskiest handoff beats a perfect register that nobody keeps current. Build out from the leak you can already feel rather than trying to map every piece at once.
“How do I handle a customer who moves my equipment between their sites without telling me?”
Treat a field transfer as a billing event with terms, not a favor. State in the rental agreement that the unit is rented to a named site and any move requires notice, so a relocated machine is a tracked change rather than a surprise. Then confirm location at every touchpoint you do control — pickup, inspection, fuel drops — so an undisclosed move shows up the next time someone from your yard stands next to the iron.
“Why does it matter which exact site a unit is on if I know the customer?”
Because the customer is who pays, but the site is where the iron lives, gets damaged, and either earns or sits idle. When a foreman calls about a stuck telehandler, knowing the customer does not tell your driver which access road to take. Site-level records also let you bill, renew, and check in one job at a time instead of treating a multi-pad operator as one undifferentiated account that hides quiet units.
“How do I find equipment that is on a site but no longer earning?”
Read your fleet by site rather than by unit. A site view shows every machine a customer is holding and how long it has been there, which surfaces the iron that has gone quiet — units left on a pad past the active phase of the job. Those are the pieces either owed standby or sitting free. A unit-by-unit list buries them; a customer-and-sites rollup puts them right on top where you can act.
“Who on my team should own keeping location records current?”
Whoever performs the move, confirmed by whoever stands next to the iron. Drivers own delivery and pickup updates; field staff confirm condition and site on any inspection or fuel run. The office should never be the source of a location it did not witness — its job is to flag mismatches, not invent positions. Spread the updating across the people already at the handoffs and the record stays close to the truth.
See how EquipFlow handles this on a live yard.
Bring your fleet count and a rough sense of your current workflow. Twenty minutes covers the dispatch board live, MSA billing, and an honest answer on fit.
Book a demoStay in the loop
Yard ops notes, once a week.
Operator-written. Covers dispatch, billing, maintenance, and what we ship. No fluff.