Updated 2 October 2026

Roll-off operations

An outside hauler can complete the physical move while the office is still left with an unfinished record. The assignment may be clear, yet the container location, service proof, extra work and customer charge can end up in separate messages. The job should remain open until those pieces agree.

TL;DR

Keep one job record as the control point for every outside-hauler delivery, swap or pickup. Confirm the hauler, container, service and site instructions before dispatch. Capture proof and reposition the individual container pin in the field. Review exceptions before approving the customer charge. Close the job only when operational and billing details reconcile.

The handoff starts before the truck moves

A subcontracted move needs more than a customer name and street address. Dispatch should make the assignment specific enough that the outside driver, office team and billing reviewer are all working from the same definition of done.

Before release, the job record should identify:

• the outside hauler responsible for the move, with a current certificate of insurance on file;
• the service type: delivery, swap or pickup;
• the individual container and its expected starting position;
• the requested service date or time window;
• site access instructions and the requested placement point;
• the disposal or return instruction when it applies;
• the proof required before the assignment can be reviewed; and
• the agreed process for reporting extra work or a failed attempt.

This creates a clean acceptance test. The field team knows what must happen, and the office knows what evidence it must receive before the job moves toward billing.

Site access instructions carry real weight on an active construction site. OSHA's construction waste-disposal rule requires scrap, waste material and rubbish to be removed from the immediate work area as the work progresses, so the placement point the job record specifies should be the spot that stays clear and reachable, not wherever debris has been allowed to collect before the truck arrives.

The certificate of insurance belongs on the release checklist, not on a shelf. A waste-hauling subcontract agreement typically keeps the primary hauler fully responsible for a subcontractor's acts on the job and requires that subcontractor to carry its own coverage, which is why the check needs to happen before the job goes out rather than after a claim. Typical benchmarks for a subcontracted hauler's certificate run close to $1 million per occurrence and $2 million aggregate in general liability, plus statutory workers' compensation and commercial auto liability, in line with the $1 million auto and $1 million general liability limits dump-truck insurance programs commonly carry. A certificate is only useful if someone checks its expiration date before the job goes out, so build that check into the release step rather than the reconciliation step. Because the dispatching company can still be held liable for an accident involving a vehicle it does not own, carrying hired and non-owned auto liability closes the gap a subcontractor's own policy leaves for the company that dispatched the job.

Site placement sometimes carries its own paperwork. A container sitting in a public street or right-of-way commonly needs a municipal permit, and a typical roll-off permit ordinance will not issue until the certificate of insurance names the municipality as an additional insured, with coverage that cannot be canceled without 30 days' written notice. Naming a party as an additional insured extends that party's protection to claims arising from the named insured's work, which is why a municipality or property owner asks for it before an outside hauler's container sits on their ground. Record the permit and its certificate in the job file instead of leaving the office to reconstruct them later.

Use the container, not just the customer site, as the reference

A customer may have several containers at the same address. A single site-level location can therefore leave dispatch unsure which container moved and where it was placed.

Give each move an explicit asset identity. Record the container number or other unique identifier, its intended action and its expected location. If a swap involves two containers, show which asset was removed and which one was left behind.

Drivers can repin a moved container at its new GPS position. Treat that repin as a required step whenever the driver changes the container's location. The updated position should belong to the individual container rather than becoming a vague pin for the whole site.

Keep field proof attached to the assignment

CRO supports a third-party hauler app, field job proof, billable additions and multiple asset pins at one customer location.

For the operator, the practical goal is to review one coherent service record. The proof package should answer four questions:

1. Who performed the work? Confirm the assigned hauler and driver.
2. What happened? Record whether the container was delivered, swapped, picked up or left in place.
3. Where is the asset now? Save the individual container's updated location when it moved.
4. What changed? Capture notes, photos and proposed extra charges for anything outside the original assignment.

Do not make the customer invoice carry operational ambiguity. If the proof does not show which container moved or what extra work occurred, return the job for clarification before billing review.

Separate an exception from a completed service

An outside-hauler job should not be forced into a simple completed-or-failed choice. A driver may reach the site and find a blocked gate, an occupied placement area, an inaccessible container or instructions that conflict with conditions on arrival.

Use a short exception workflow:

• record the observed issue;
• attach the relevant photo or note;
• state whether the requested move was completed, partly completed or not completed;
• identify any extra work proposed for billing;
• send the record to the appropriate office reviewer; and
• leave the job open until the next action is decided.

This preserves the original request without pretending that the field result matched it. It also gives the office a clear place to approve a change, reschedule the work or remove an unsupported charge.

Reconcile service and billing before closing the job

Operational completion and billing readiness are related, but they are not the same decision. A container can be in the right place while an extra charge remains unresolved. Equally, a complete photo set does not establish that every proposed charge belongs on the customer invoice.

Use a final office review with five checks:

Matching a subcontractor's invoice or paying it remains an operator check unless separately verified. Keep that accounts-payable decision distinct from proving the customer service and approving the customer charge.

This is the same discipline behind three-way matching in any subcontracted-vendor relationship: compare what was assigned, what the field proof shows actually happened, and what the invoice charges, then resolve any mismatch before payment rather than after it. The five checks above are that same match, applied to one outside-hauler job record instead of a stack of separate paperwork.

A practical closeout status model

A small set of explicit statuses can prevent premature closure:

• Assigned: the outside hauler has the job and its instructions.
• In progress: the move has started but field proof is not complete.
• Exception review: the requested result and field outcome differ.
• Billing review: service proof is present and charges need approval.
• Closed: the service, asset location, exceptions and customer charge agree.

The labels matter less than the gates between them. A driver completing a field step should not automatically settle an exception or approve a customer charge. Those decisions need their own owners.

Questions to test in a workflow demonstration

Ask for a demonstration using one real outside-hauler scenario rather than a generic dispatch tour. Use a delivery, swap or pickup with a moved container and one billing exception.

• Can the dispatcher assign the work to the outside hauler without creating a disconnected record?
• Can the driver identify the exact container involved?
• Can the driver update that container's position at the customer location?
• Can photos, notes and extra work remain attached to the same assignment?
• Can the office hold an exception without losing the completed field proof?
• Can the billing reviewer see what was requested, what happened and what was approved?

If the demonstration cannot keep those answers together, the operator is likely to rebuild the handoff through calls, texts and manual reconciliation.

Where CRO fits in the decision

This is where CRO's outside-hauler tools genuinely fit the problem above. The assignment, the container's mapped location and repin, the driver's proof of service and any billable additions all attach to one job in CRO, so dispatch, the outside driver and the office reviewer read the same record instead of piecing one together from texts and separate photo threads. CRO's third-party hauler app assigns and tracks a subcontracted job the same way it tracks an in-house truck, rather than treating the outside fleet as a workaround outside the system. When a container moves, the driver repins it in CRO instead of the office relying on a stale note. None of this replaces the office's own judgment on whether a proposed subcontractor charge belongs on the customer invoice; CRO keeps the evidence attached to the assignment so that reviewer can decide quickly, not automatically.

This level of process is not the right answer for every outside-hauler relationship. An operator who calls in a subcontractor once or twice a season, for a single overflow job with no repeat container swaps, does not need a formal status gate: a phone confirmation, one photo attached to the invoice and a quick sign-off from whoever approves billing will cover it. The job-record approach in this checklist earns its cost once outside-hauler volume is routine enough that a missed handoff step turns into a repeated billing dispute rather than a rare one.

The reconciliation time adds up faster than it looks once volume is routine. Assume an office spends 25 minutes tracking down the hauler, confirming the container's final position and matching field notes to a proposed charge before approving one outside-hauler invoice with no shared job record, and 8 minutes once the assignment, the repinned container location and the proof already sit in one place, a reduction of 17 minutes per job. At the median hourly wage for dispatchers, $22.53 (U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2023), that is roughly $6.38 saved per reconciled job. An operator handling 15 outside-hauler jobs a week saves about $96 in reconciliation time that week, or roughly $5,000 across a year, before counting a single avoided billing dispute or duplicate payment. The job count, minutes per job and time saved are assumptions for this example; substitute your own outside-hauler volume and office wage to size the effect for your operation.

Keep the record open until the handoff is complete

The best outside-hauler workflow is not the one that marks work complete fastest. It is the one that leaves dispatch, the asset record and billing with the same account of what happened. Build the process around one container, one assignment and explicit review gates, then close the record only when the operational and commercial details reconcile.

See the workflow in a CRO demonstration

Frequently asked questions

What should be recorded before an outside hauler receives a roll-off job?

Record the hauler, service type, individual container, requested date, site and access instructions, proof requirements and the process for reporting an exception or extra work.

Is a customer-site GPS pin enough?

Use an individual container location when several assets may sit at the same customer site. The closeout should identify which container moved and where it was left.

When is an outside-hauler job ready to close?

Close it after the assignment, asset identity, final location, service proof, exceptions and approved customer charge agree. A completed drive or field step alone should not bypass those checks.

How should extra work be handled?

Record the extra work against the original assignment, attach supporting notes or photos and route it for office approval before adding it to the customer charge.

Does every outside-hauler job need this full process?

No. A single occasional subcontracted job can be confirmed by phone with one photo attached to the invoice. Use the full job-record workflow once outside-hauler jobs are frequent enough that a missed step becomes a recurring billing dispute rather than a rare one.

Sources

1. RapidWorks, CRO product page, reviewed 30 September 2026.
2. RapidWorks, Schedule a Demo, reviewed 30 September 2026.
3. Sourgum, Waste Hauling Master Service Agreement, subcontracted hauler terms, reviewed 30 September 2026.
4. SubDoc, A Comprehensive Guide to Construction Vendor Insurance Requirements, reviewed 30 September 2026.
5. Procore, Certificate of Insurance (COI), reviewed 30 September 2026.
6. Insureon, Hired and Non-Owned Auto Insurance, reviewed 30 September 2026.
7. Kojo, Why Every Contractor Should Do 3-Way Matching, reviewed 30 September 2026.
8. Amwins, Dump Trucks Insurance Program, reviewed 30 September 2026.
9. Amwins, Four Key Additional Insured Endorsements for Contractors, reviewed 30 September 2026.
10. Hanover Township, Dumpster/Roll-Off Container Permit Application and Ordinance, reviewed 30 September 2026.
11. OSHA, 29 CFR 1926.252, Disposal of waste materials, reviewed 30 September 2026.
12. U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, Dispatchers, Except Police, Fire, and Ambulance (SOC 43-5032), May 2023, reviewed 30 September 2026.