Skip to main content
Equipment Scheduling

Moving Equipment Between Job Sites Without Losing Track of It

Rovaryn DigitalNovember 3, 20269 min read
Moving Equipment Between Job Sites Without Losing Track of It

The Excavator That Was Booked Everywhere and Parked Nowhere

It is 6:40 on a Monday morning. The superintendent at the second site has a mid-size excavator on his schedule starting at seven. The schedule says it left the yard on Friday, so he expects it to be there. It is not. The yard foreman says it went out on a lowboy Friday afternoon, but two sites had asked for it and the dispatcher changed the plan by text, so he cannot say which one it went to. The driver is off until noon. Meanwhile the schedule shows the machine as "assigned" to the second site, so nobody thinks to look for it, and the project manager has just promised it to a third job for Wednesday.

Nothing about that morning is a scheduling failure in the narrow sense. Every booking was valid on paper. What broke was the stretch of time when the machine was neither at the yard nor on a site, a stretch that most calendars and whiteboards do not represent at all.

This guide covers how to handle an equipment transfer between job sites so that the schedule matches where machines actually are: what to record, who has to sign off, and when a machine counts as available at the next job.

Why a Machine in Transit Falls Through the Schedule

Most scheduling tools, and nearly all spreadsheets, model a machine as being in one of two places: assigned to a site or sitting at the yard. A move turns that into a three-state problem. At the start of the day the machine is at Site A. At the end of the day it is at Site B. In between, it is on a trailer, with a driver, on a road, in a state that no row on the sheet describes.

That gap causes three predictable failures.

Phantom availability. The booking at Site A ends on Thursday, so the machine looks free on Friday. Anyone planning from the calendar assumes it can be reassigned on Friday morning, when in fact it is still being loaded or is unavailable until the haul is done.

Phantom presence. The booking at Site B starts Friday, so the calendar treats the machine as on site Friday. If the haul slips to Saturday, the schedule is wrong for a day or more, and nobody changes it because nobody is told.

Orphaned machines. When a move is arranged verbally, the record exists only in the driver's and dispatcher's heads, and a changed plan leaves the schedule silently wrong.

The cost of getting this wrong is the cost of an idle or unavailable machine, and the published figures on that are large. Whip Around reports that up to roughly 30% of equipment time on jobsites is idle (Whip Around, 2025), and manufacturer telematics data across roughly 75,000 North American machines found average idle time near 38% (FleetRabbit, 2025). Whip Around also estimates heavy-equipment downtime at $450-$760 per hour depending on asset class (Whip Around, 2025). Transit gaps are only one contributor to idle time, but they are one you can see and record.

What a Complete Move Record Contains

A log of every equipment transfer between job sites does not need to be elaborate. It needs to answer five questions for every machine every time it moves, and it needs to be filled in at the moment of the move, not reconstructed on Friday afternoon.

  1. Which machine? Use the asset ID from your register, not "the 320" or "the yellow one." If you lack consistent IDs, fix that first.
  2. From where, to where? Name the origin and destination exactly. "Yard to Site B" is fine. "Out to the job" is not.
  3. Who authorized it? A named person approved this move, not "dispatch." This matters later when two sites argue over the same machine.
  4. When did it depart, and when did it arrive? Two separate timestamps. The first closes the machine's availability at the origin. The second opens it at the destination.
  5. What state is it in right now? At minimum: at origin, in transit, or arrived and accepted.

The fifth item is the one most informal systems skip, and it is the one that fixes phantom availability and phantom presence. If a machine is flagged "in transit" from the moment it leaves until someone at the receiving end confirms it, there is always an answer to "where is it?" even when the answer is "on a trailer, due this afternoon." For a deeper look at how status labels support this, see our guide to equipment asset status tracking.

Authorization: Who Approves an Equipment Transfer Between Job Sites

Informal moves are the main source of orphaned machines. A foreman who needs a skid steer calls the yard, the yard sends one, and the machine the project manager had earmarked for another site is gone.

A workable transfer authorization rule is short:

  • Any site can request a machine.
  • One named role approves the request, usually the equipment manager or a designated project manager.
  • The approval is recorded with the move, so the log shows the request, the approver and the date.
  • A machine already booked at its current site cannot be pulled without the approver resolving that booking first.

This is the same request-and-approve pattern that EquipmentScheduler uses in the app, where site users request equipment and an approver confirms it. On paper or in a spreadsheet, you can reproduce the pattern with two columns, "requested by" and "approved by," and a rule that a move without both is not a move. If a single mobilization sends several machines to the same site, handle the group as one authorized batch with one line per machine; our piece on bulk equipment assignment to a job site covers that case.

Counting Transit Time Honestly: A Worked Example

The following is an illustration with round numbers, not a statistic.

Suppose a compact excavator finishes at Site A on Thursday at 4:00 pm. Site B's booking starts Monday at 7:00 am. The machine is loaded Friday at 10:00 am and, because of a trucking delay, arrives at Site B on Friday at 3:00 pm. Whoever is receiving it signs for it Friday at 3:30 pm.

On a calendar that only tracks bookings, the machine shows as free from Thursday evening and committed again on Monday morning. That leaves a Friday-to-Sunday window in which someone could reasonably book it for something else, even though it is on a trailer or unloading for most of Friday.

On a log that tracks the move, the same machine reads: available at Site A until Thursday 4:00 pm; in transit from Friday 10:00 am; arrived and accepted at Site B Friday 3:30 pm. The calendar can then treat the machine as unavailable from Friday morning, and the Monday booking at Site B is clearly safe.

The log did not change the physical haul. It turned a vague "somewhere between" into a window with edges.

A useful habit is to schedule travel as its own block: if a haul takes most of a working day, book the machine as unavailable for that day rather than hoping the arrival lands before the next job begins. The broader logic of keeping a machine's availability honest across sites is covered in our guide to how to schedule equipment across multiple job sites and in equipment availability tracking.

Where the Calendar Fits and Where It Does Not

Move logging and booking are two different jobs, and the boundary matters for every equipment transfer between job sites.

A move log records physical events: a machine left, a machine arrived, a person authorized it. It is a record of what happened, and someone has to enter it by hand.

A booking calendar records intent: this machine is committed to this site for these dates. EquipmentScheduler is a booking calendar with a conflict check. Before a booking is saved, it runs a date-range overlap check on the equipment and on the operator, so a machine cannot be committed to two sites for overlapping dates. It also has an equipment registry, status badges, request-and-approve workflow and utilization reports.

What it does not do is track a machine on the road. There is no GPS or in-transit tracking in the app, and it does not connect to telematics. If you want to know where a trailer is right now, that is a separate question with a separate answer; our article on whether you need GPS and telematics for scheduling walks through when that investment makes sense and when a disciplined manual log is enough for a fleet of this size.

The practical division for a 5-30 machine fleet looks like this:

  • Use the booking calendar to prevent double-booking and to see which machines are committed where.
  • Use a move log, kept by hand, to record departures, arrivals and authorizations.
  • When a move is logged as departed, update the calendar so the machine does not look available at the origin or present at the destination until the arrival is confirmed.

The calendar prevents the conflict. The log keeps the calendar honest.

Setting Up the Log Without Starting From Scratch

You can build a move log for each equipment transfer between job sites in a spreadsheet in an afternoon: one row per move, with the five fields above, a status column and a filter that shows everything currently in transit. The two disciplines that make it work are filling it in on the day and giving one person responsibility for checking the "in transit" filter at the start of each day. Anything still flagged from yesterday gets a phone call.

If you would rather start with a finished structure, the Equipment Move & Transfer Log with In-Transit Tracking is a template built for this: every machine move logged, with depart, arrive and who authorized it, and an in-transit flag so nothing is lost between yards and jobs. It is a manual workbook, not a tracking system, so it works only as well as the people who fill it in, but it gives you the fields and the filter without designing them yourself.

Whichever route you take, start with a single week. Log every move, flag anything that arrives later than planned, and look at how many machines were, at some point in that week, somewhere your schedule could not have told you.

Get practical fleet scheduling guides in your inbox

Related articles