Managing Equipment Pickups and Swaps
A pickup or a swap looks simple on the schedule: send a truck, bring a unit back, maybe drop a replacement. On the ground it is where yards quietly lose money and lose track of their iron. A scissor lift goes down mid-job, a driver leaves the replacement and forgets to flag the dead one, and a week later you are still billing a serial number that has not lifted a thing. This guide is about keeping the chain of custody intact during swaps and recoveries — knowing what is on which site, who has it, and what state it is in — so the truck roll, the billing, and the physical iron all agree.
A swap is two transactions, not one
The single biggest mistake yards make is treating a swap as one event. It is two: a delivery of the replacement and a recovery of the unit coming off rent. When a scissor lift fails on a contractor's deck and the crew needs another up there by morning, the replacement rolls before the dead one comes home. For a window, both units are physically on that job. If your dispatch record only shows one line, the other unit falls into a blind spot — still marked on rent, still billing, sitting in a corner of the site. Write the swap as a paired move from the start: one unit ending its rental, one unit beginning. The truck may carry both, but the books should never collapse them into a single entry.
Chain of custody is the whole game
Every time iron changes hands or changes location, custody should change with it on paper. The driver who drops a telehandler is the last person who can confirm where it actually sits and who signed for it. If that hand-off is a verbal nod in a gravel lot, you have nothing when the unit goes missing or the customer disputes the return date. Capture the transfer at the moment it happens: who released it, who received it, the on-site location, and the meter reading. A swap doubles the exposure because two units move in one trip. Make the driver close out the recovered unit before the replacement is considered delivered, so one cannot be quietly skipped in the rush.
On-site repositioning is not a return
Contractors move your equipment around their site constantly. A scissor lift that was on the east elevation Monday is on the north stairwell by Wednesday, hauled there by the crew without telling anyone. This is normal and fine — until your driver shows up to recover it and cannot find it, then burns an hour and a wasted truck roll. The fix is to stop assuming the drop location is the pickup location. On longer contractor jobs, confirm the current position before dispatching the recovery, ideally with the site contact you already have on file. Treat a unit that has wandered across a jobsite as still on rent and accounted for, not as a phantom return. Repositioning is a logistics note, never a billing event.
Recoveries fail when nobody declares 'done'
A recovery should be triggered by a clear signal that the rental is over — not by a guess. The two failure modes are mirror images. You pick up too early, the crew still needed the telehandler, and now you have an angry contractor and an emergency redelivery. Or you pick up too late, the unit sat idle for days while you kept billing, and the customer fights the invoice when they notice. Both come from a fuzzy end-of-rental signal. Decide who gets to declare a job done, get it in a form you can point to, and tie the recovery dispatch to that declaration. A unit waiting on pickup is still your liability on someone else's ground, so do not let 'we'll grab it eventually' stretch into open-ended exposure.
Reconcile what the system says against what the yard knows
Records drift. After enough swaps and repositions, your dispatch board and the physical reality of where your iron sits start to disagree, and the gap is invisible until you go looking. Build a habit of reconciling: walk the open rentals and confirm each unit is where the record claims, on the job the record names, billing on the terms the record holds. The units most likely to be wrong are the ones involved in a recent swap, because that is where custody changed hands fast. When the system and the yard disagree, the yard is usually right and the paperwork is stale — so fix the record, then ask why it drifted. A swap that was never closed out is the classic culprit.
Build swaps into how you quote and dispatch
If swaps are an emergency every time, your process is the problem, not the customer. Heavy use, rough sites, and high-hour iron mean breakdowns are a cost of doing business, so plan for the replacement before you need it. Keep enough float in the fleet for the equipment classes that fail most, and know which standby units can roll on short notice. When you write the rental, note whether the job is the kind that will need hot swaps — multi-phase contractor builds usually are — so dispatch is not caught flat. The smoother the swap, the less the customer feels the breakdown, and a fast, accounted-for replacement is one of the few moments where downtime can actually build trust instead of burning it.
Key takeaways
Treat every swap as two linked transactions — one unit ending its rental and one beginning — so the unit coming off rent never falls into a billing blind spot.
Capture chain of custody at the moment iron changes hands: who released it, who received it, where it sits, and the meter reading.
On-site repositioning by the crew is a logistics note, not a return — confirm the current location before sending a recovery truck.
Tie recovery dispatch to a clear end-of-rental declaration from a named person, so you neither pick up too early nor keep billing idle iron.
Reconcile the dispatch record against the physical yard regularly, and look hardest at units involved in a recent swap, where custody changed fast.
Plan for swaps as a normal cost of heavy use — keep fleet float and standby units ready rather than treating every breakdown as an emergency.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“How do I keep billing straight when a replacement goes out before the broken unit comes back?”
Bill them as two separate rental lines tied to the same job. The replacement starts billing when it is delivered and accepted; the original stops when the driver confirms recovery, not when it physically reaches the yard. The danger is the overlap window where both sit on site. If you collapse them into one record, one keeps billing in the background. Keep the lines distinct and close the old one the moment custody transfers.
“What is the cleanest way to track where a unit actually is on a large jobsite?”
Lean on the site contact you captured at delivery. On big contractor jobs the crew will reposition a scissor lift or telehandler without telling you, so the drop spot is rarely the pickup spot. Before you send a recovery truck, have dispatch confirm the current location with that contact. Logging the on-site position at each touch keeps your record close to reality and saves the wasted roll of a driver hunting for a unit that walked.
“Who should be allowed to declare a rental finished and trigger a pickup?”
Name one decision-maker per job and put it in writing at the start. A pickup triggered by an offhand comment from whoever answered the phone is how you recover iron a crew still needs the next morning. The person who can say 'we are done' should be the same person you confirm the recovery with. Tie the dispatch to that declaration so you are never guessing whether the job is actually over.
“How often should I reconcile my records against the iron that is actually out?”
Often enough that drift never gets big, and always after a busy swap stretch. Walk your open rentals and confirm each unit is on the job it should be, in the state the record claims, billing on the right terms. Pay closest attention to anything that went through a recent swap, because fast hand-offs are where the record and reality split. When they disagree, trust the yard, fix the record, then find out why it drifted.
“Should a customer pay while a unit waits on site for me to pick it up?”
That depends on what the contract says and why it is waiting. If the job ended and you simply have not collected yet, billing the idle days will sour the relationship fast. If the customer keeps the unit on site for their own convenience past the declared end, that is a different conversation. Settle the rule before the rental starts so the recovery window is not a fight, and recover promptly once a job is declared done.
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.