Roll-off operations
Updated November 14, 2026
At 3 p.m., Nina's north yard sends a 20-yard dumpster south for tomorrow's delivery, while both dispatch desks still expect to use it. Dispatch should promise that transferred dumpster only after the receiving yard confirms the correct unit is physically there and ready, and a named dispatcher checks its next commitment.
TLDR: Keep the next booking pending until a receiving person confirms the dumpster's ID, condition and readiness. CRO gives drivers assigned job details and captures job photos and notes to support the handoff. Physical receipt and the decision to promise the unit still belong to your people.
What does departure confirm?
Leaving the north yard establishes where the transfer began; receiving it at the south yard establishes whether dispatch has the right dumpster to assign. Nina's transfer record names unit 204, a 20-yard needed for a customer tomorrow. The north desk knows it left. The south desk expects it. Neither fact tells Rosa, the receiving yard lead, what has actually arrived. Crossed wires are easy when everyone is working toward the same delivery from a different desk.
Keep the dumpster's identity through the move. GS1's returnable-asset guidance distinguishes equipment that returns for reuse from a single shipment. Its traceability framework records shipping and receiving as separate events. For Nina, departure starts a movement record; it cannot stand in for Rosa's receipt at the other end.
We suggest agreeing on the handoff before the truck leaves. Nina records unit 204, its size, the sending and receiving yards, departure time, driver and Rosa's name as the receiving contact. The driver takes responsibility for reporting the movement while it travels; Nina owns the office follow-up until Rosa confirms receipt. Record an expected arrival and a time for the next update, so an overdue transfer has someone to call. Keep the future booking pending, and tell both desks that the unit is committed to this transfer.
Who owns the handoff at each desk?
Both yards need the same account of who has the dumpster and what happens next. A shared transfer note can do that without turning a simple move into a second dispatch operation. The labels below describe a suggested office practice. Agree who updates the note and where both desks will read it.
| Transfer point | What the team records | Named owner | Next action before another promise |
|---|---|---|---|
| Departure | Unit 204, size, yards, driver and departure time | Nina, sending dispatcher | Tell both desks the unit is moving and keep its next booking pending. |
| In transit | Last confirmed movement, expected arrival and next update time | Transfer driver reports; Nina follows up | Check with the driver if the agreed update is missed. |
| Received | Physical ID, receiving location, time, condition and readiness | Rosa, receiving yard lead | Send receipt confirmation to Nina; dispatch checks the next job. |
| Mismatch or no arrival | Expected unit, actual finding and unresolved question | Nina owns resolution with the driver and Rosa | Keep the affected unit off the available list until its receipt and readiness are confirmed. |
The note gives each person a clear part of the job. O*NET's dispatcher profile includes coordinating equipment and keeping work requests; here, Nina keeps that office responsibility while Rosa reports the physical finding. Rosa confirms what she can physically check at the receiving yard. The driver reports what moved. Nina reconciles their accounts and makes sure both desks have the result.
If a shift changes before the transfer closes, we suggest handing that open item to a named replacement with the last confirmed fact and the next call time. We suggest a verbal handover with the shared note, then an incoming cross-check, following the approach in HSE's handover guidance. An expected arrival should never quietly become a received unit because someone went home.
What if the arriving dumpster has a different ID?
An arrival mismatch stays open until the team identifies the dumpster that actually moved. At the south yard, Rosa reads 240 on the arriving unit; Nina's departure note says 204. Both are 20-yards, so size alone would miss the discrepancy. GS1's explanation of serialisation separates an individual asset's lifetime identity from its type. The receipt needs the particular dumpster, not just another unit of the same size.
Rosa reports the actual ID and receiving location, and Nina keeps 204's next assignment pending while the driver checks the departure record against the unit moved. A photo can help settle a transposed number, but the team still needs to establish which physical dumpster it identifies. Comparing an arrival with its documents and reporting discrepancies is a receiving task described by O*NET's receiving-clerk profile; Rosa's expected-ID and actual-ID note makes that comparison usable by both desks.
Rosa's receipt check also covers readiness for the next job: whether the dumpster is empty, whether anything needs cleaning or attention, and where it is parked for loading. We suggest recording any concern and referring it to the person your company authorizes to decide fitness for service. A condition photo documents what someone saw; it does not approve the equipment. If a different unit arrived, confirm that unit separately and locate the expected one. If nothing arrived, Nina follows up with the driver and gives the south desk a new update time.
Make the physical check from a safe position under your company's yard procedure. NIOSH's refuse-truck safety guidance warns about people being struck around moving and reversing vehicles. Rosa should not chase a truck or step behind it to finish a photograph. An unreadable or inaccessible number remains unresolved until the team can check it safely.

Use CRO to check the recorded work
CRO supports the office-to-driver record behind a dumpster transfer. For a dumpster moving between yards, compare its driver-entered placement pin and assigned movement with the receiving person's physical finding before treating it as available. This gives dispatch a recorded dumpster location to check; a placement pin is not continuous GPS hardware telemetry. Dispatchers can assign trucks and drivers, and drivers can view assigned routes and full job details. Photos, notes and customer signatures captured on site attach to the job record. Drivers can also pin exact unit placement on a map, including multiple pins at one location. Those are useful records for checking the planned movement against reported field work, with fewer scraps of paper to piece together. See our CRO job and driver capabilities.
That connected record gives dispatch a reliable starting point for the conversation with the receiving yard. Keep the receipt confirmation explicit: who saw the unit, which ID they read, where it sits and whether it is ready. A driver-set pin records placement; it does not establish that Rosa received the unit or approved its condition. Use the assigned work and field evidence to investigate Nina's discrepancy, then have the people at each end confirm the result before dispatch changes its plan.
When can dispatch promise the next delivery?
Receipt makes the dumpster a candidate for its next assignment; dispatch still checks whether the customer commitment works. The driver confirms that 240 was loaded while 204 stayed at the north yard. Nina records the confirmed location of each unit, arranges 204's transfer and keeps tomorrow's booking pending. When Rosa receives 204, Nina still checks the agreed customer terms, delivery window, truck and driver availability, and preparation work. Keep the customer updated if the plan remains uncertain, and agree a changed window or substitute before sending a different instruction.
Receipt also leaves the next road movement to check. For US operations covered by federal motor-carrier rules, the driver's cargo and securement checks are separate from Rosa's receiving note. Roll-off and hook-lift securement requirements depend on the equipment, with specific provisions for vehicles without an integral securement system. The driver must also be satisfied that the vehicle is safe to operate. A signed receipt or condition photo does not replace those checks or make an unresolved equipment concern fit the customer's window.
Use assumed times to test that last decision. Suppose the next delivery window ends at 9 a.m., preparation takes 15 minutes, travel takes 40 minutes, and Nina allows a 20-minute buffer. These are planning assumptions, not CRO estimates or typical operating times. The calculation gives her a latest preparation start:
- Preparation, travel and buffer total 15 + 40 + 20 = 75 minutes.
- Counting back 75 minutes from 9 a.m. gives 7:45 a.m.
- If Rosa can confirm receipt and readiness at 7:30 a.m., Nina has 15 minutes before that start time. A confirmation at 8 a.m. misses it by 15 minutes, so she needs a revised plan before promising the window.
Nina closes the transfer when both desks have the confirmed unit, Rosa's receipt and the next assignment decision. Unit 204 can then move into tomorrow's plan with a person behind each confirmation. For the wider fleet check, use our daily container count. Our cross-yard visibility guide covers shared records, while the container inventory and itemization guide covers asset identity and job activity.
Bring one transfer and a mismatched arrival to a CRO demo. We can walk through assigned job details and recorded field evidence while you decide who confirms physical receipt and releases the dumpster for its next job.
Frequently asked questions
When can dispatch promise a dumpster moving between yards?
After the receiving yard physically confirms the correct unit and its readiness, and the named dispatcher checks the next customer commitment. Keep the booking pending during transit and while any receipt discrepancy remains unresolved.
Who confirms receipt at the destination yard?
A named person at the receiving yard checks the arriving dumpster's ID, condition, readiness and location, then confirms those findings to dispatch. The dispatcher owns the next assignment decision and keeps both yards informed.
What if the arriving dumpster has a different unit number?
Record the expected and actual numbers, name the dispatcher who will resolve the discrepancy, and check with the driver and sending yard. Confirm the arriving unit separately and locate the expected unit before treating either one's transfer as resolved. Keep the next booking pending until a named person at the receiving yard confirms the arriving unit's ID and readiness.
Does a map pin prove the receiving yard accepted the dumpster?
No. A driver-set placement pin records a location. Physical receipt requires a person at the receiving yard to identify the unit and report its readiness. Dispatch still checks the next assignment before promising it.
What CRO records help with an interyard handoff?
CRO gives drivers assigned routes and job details, captures photos, notes and customer signatures on job records, and lets drivers pin unit placement on a map. Use those records alongside the receiving person's physical confirmation and the dispatcher's release decision.
Sources
- CRO job, driver and asset capabilities.
- Daily container count.
- Cross-yard container visibility.
- Container inventory and itemization.
- GS1: Main use of GRAI
- GS1: Serialisation and unique identification
- GS1: Global Traceability Standard
- O*NET: Shipping, Receiving, and Inventory Clerks
- O*NET: Dispatchers, Except Police, Fire, and Ambulance
- HSE: Shift handover
- NIOSH 2024-123: Preventing Struck-by Injuries and Deaths When Working with Refuse Trucks
- eCFR: 49 CFR 393.134, roll-on/roll-off and hook lift securement
- eCFR: 49 CFR 392.9, cargo inspection
- eCFR: 49 CFR 396.13, driver inspection