Roll-off dispatch software
Build a dispatch plan the whole team can follow.
A roll-off day connects customer commitments, available cans, trucks, drivers and disposal stops. For qualified large-scale operators, TossDock Pro brings those workflows into one operating workspace. Use this guide and the working demo to assess how your dispatcher would plan the day and handle changes.
Start with the service commitment
Review what the customer needs before assigning the work: delivery, pickup, exchange or another agreed service. Confirm the service address, container size, requested window and site instructions. An incomplete job should have a clear next action so the dispatcher can resolve it before a driver starts the trip.
- Separate a requested date from a confirmed service commitment.
- Identify access questions, material restrictions and instructions that require a person to review.
Match the job to available capacity
Look at the truck, driver and container together. A free truck lane does not establish that the required can is ready or that the driver can complete the work within the shift. In the demo, inspect the assignment controls and truck lanes; in deployment, verify the limits and records your team relies on.
- Check current assignments, expected returns and disposal time.
- Confirm who can assign, move and remove work from the daily plan.
Make changes visible to the office and field
An urgent pickup or a truck going out of service can change several commitments. Review the affected work before moving it, identify who needs an update and confirm the saved plan. Acceptance should include a failed-save exercise so a dispatcher can distinguish a proposed edit from the last confirmed assignment.
Close the handoff with service evidence
Decide which driver updates and supporting records the office needs for completion, exceptions and billing review. A route proposal still requires dispatcher review; it does not establish road access, site suitability or permission to enter. Agree how the team handles an unsuccessful service attempt and who contacts the customer.
Prepare the conversation
Bring these details to a dispatch assessment
Start with representative operating information. Detailed customer records can wait until the migration scope and access arrangements are agreed.
- Your normal job types, dispatch hours and busiest periods.
- Truck and driver counts, shift constraints and container types.
- How work reaches the dispatcher today and where changes are recorded.
- Common exceptions, escalation owners and required driver evidence.
Use this in an evaluation
Review exercise: a truck becomes unavailable
Use demonstration jobs to take one truck out of the plan after assignments have been made. Walk through the response with a dispatcher and someone who works in the field. The useful result is an agreed process for affected work, not a claim about miles or hours saved.
- Find every affected job and its customer commitment.
- Review another truck and driver before reassigning the work.
- Confirm the saved plan and decide who owns each customer update.
Common questions
Does TossDock dispatch trucks autonomously?
Dispatch remains an operator decision. Suggested plans are proposals for review. Your team confirms assignments, restrictions and customer commitments before relying on a route.
What can we evaluate in the public demo?
You can explore the interface and example assignment workflow. It uses demonstration records. Shared live records, permissions, driver updates and failure recovery must be accepted for your deployment.
How should we compare dispatch systems?
Use the same representative day in each assessment, including a difficult change. Ask the dispatcher to explain the next action, the evidence needed and how another team member learns about it. Confirm required integrations in writing.