A dumpster dispatch checklist for a day that keeps moving

1. Reconcile the work before assigning drivers

Start with yesterday’s unfinished work. A failed pickup, a delayed return, or a unit still awaiting inspection changes today’s available inventory. Do not copy an old route forward and assume its equipment is back in the yard.

Review each due delivery, pickup, and exchange. Confirm the customer, site, job type, equipment requirement, and the person responsible for the next action. A customer can have several active locations, so the customer name alone is not a safe way to identify a stop.

• Requested time: what the customer asked for, including any event or site restriction.
• Confirmed window: what your office has actually committed to and communicated.
• Equipment status: the specific unit if assigned, or the compatible pool from which it will be selected.
• Open exception: anything that could stop the job, its owner, and the next review time.
• Commercial approval: whether the quote, account terms, or required payment step is complete under your policy.

Keep uncertain appointments visibly uncertain. A requested 8 a.m. delivery should not quietly become a confirmed 8 a.m. appointment when it appears on a board. Resolve the promise before assigning a route that cannot meet it.

2. Match equipment to the site and the truck

Identify containers by unit number when the assignment becomes definite. A description such as “the blue 20-yard” is not dependable if you have several similar units. The office and driver should use the same identifier through delivery, pickup, and return.

Confirm compatibility against your own equipment records. A roll-off container and a towable dumpster may both serve a customer’s cleanup, but their transport and placement requirements differ. The planner needs the actual truck, equipment, and site constraints. Do not infer compatibility from size alone.

The site record should include the entrance to use, an onsite contact, access hours, and the intended placement location. Useful notes are specific: “Use the south entrance; call the site contact before arrival.” A long thread of old instructions should not override the latest confirmed directions.

Include the relevant handling or access restrictions from your operating procedures and the customer’s approved placement plan. If a driver finds that conditions differ from those records, they need a clear way to stop and contact the office. A dispatch checklist should expose uncertainty, not encourage a driver to improvise around it.

Finally, distinguish “returned” from “available.” A returned unit may still need an inspection, cleaning, or repair. Marking it ready early can make the next reservation appear covered even when the equipment cannot leave the yard.

3. Sequence the day around dependencies

Order the stops after identifying which jobs depend on another task finishing. A pickup may supply the container for a later delivery, but only after travel, disposal where applicable, inspection, and any required preparation. Those steps need time and a workable fallback.

Consider this fictional two-truck plan. Truck A has a compatible empty container available at the yard. Truck B is assigned an exchange and must carry its replacement unit. The afternoon delivery depends on a morning return that is not yet available.

Account for disposal facility opening hours, expected unloading time, shift limits, and travel conditions using the information your office actually has. A route is not feasible just because every destination appears on a map. If a required detail is missing, leave the plan for review.

Keep discretionary work identifiable so the dispatcher knows what can move if an earlier job runs late. Replanning should preserve confirmed commitments and communicate changes to the affected driver. Avoid forcing the driver to reconcile an old text message with a newly sequenced job list.

4. Give drivers a complete, current handoff

A driver’s job card should answer five questions quickly: where am I going, what am I doing, which equipment am I handling, who can help onsite, and what counts as completion? These details should be accessible before the driver leaves for the stop.

For a delivery, record the actual unit placed and the placement location. Capture the timestamp, relevant notes, and supporting photos under your company’s procedures. For a pickup, identify the unit actually collected. For an exchange, preserve both the outgoing and incoming equipment identities.

In Gravel, a recorded dropped event starts the rental clock. Moving a card on the schedule or assigning a driver does not prove delivery. This separation helps keep promised work distinct from completed work, especially when an appointment changes during the day.

Ask drivers to record exceptions where the work lives rather than leaving the office to reconstruct a call later. A short structured outcome plus a useful note is usually easier to act on than a generic “problem” status. The office should be able to identify the next action without guessing what the driver meant.

If connectivity is poor, follow the capture-and-sync procedure supported by your system. Keep unsubmitted records visibly pending. On reconnection, check that notes, photos, and events reached the correct job once. A screen that appears saved is not enough if the office has never received the record.

5. Keep exceptions open until someone resolves them

A blocked gate is an attempted visit, not a completed delivery. A customer’s request to move a container is not an automatic approval for an extra charge. Separate the field outcome from the office decision about rescheduling, equipment, and any agreed fees.

Use a small exception log linked to the job. Record the reason, observed time, affected equipment, owner, next action, and due time for a follow-up. Review it during the day so an unresolved issue does not disappear underneath newer bookings.

• No access: record the obstacle and contact attempt, then have the office confirm the next appointment.
• Wrong or missing equipment: reconcile the unit identifier and assignment before declaring the stop complete.
• Customer change: save the request, confirm the revised scope, and communicate the new plan.
• Damage or unexpected conditions: record evidence and route the decision to the appropriate office role.
• Sync failure: keep the pending field record visible until its receipt is confirmed.

If a mistake is corrected, retain the original record and add the correction. An understandable sequence is more useful than silently replacing the timestamp or unit number. Billing and customer service may need to explain exactly why the record changed.

6. Close the day before closing the job

Reconcile completed stops with container locations. Review what is on rent, in transit, returned for preparation, ready to rent, and out for repair. Make sure tomorrow’s reservations use that updated picture rather than this morning’s planned inventory.

Check the billing handoff separately. A completed pickup may still need a weight record or office review before the final charge can be explained. Gather the accepted price terms, relevant actual events, approved additions, and supporting documents. Avoid treating “job complete” as permission to invent missing amounts.

Review exceptions one more time and assign every remaining action. A useful end-of-day handoff says who is contacting the customer, which job is being rescheduled, and what inventory is affected. Carry those unresolved actions into tomorrow’s opening check.

During the first week using this checklist, count missing handoff fields and unresolved exceptions. That gives your team a baseline without making up a productivity target. After correcting the most common omissions, compare similar days and see whether fewer jobs need office clarification.

If dispatch software is your next step, bring this checklist to a software evaluation. For companies adding sanitation work, use a separate recurring service schedule: a cleaning visit and a container exchange need different completion records even when they share an office.