Goldberg Consulting

Breakdown · A regional trucking company

Dispatch, out of one head

A regional carrier running 40 to 80 trucks had steady revenue and a full board. Leadership thought the limit was drivers. The real limit was that dispatch lived in one senior dispatcher's head. Here is how it was rebuilt, from the first order to the paid invoice.

The carrier's dispatch system, built one piece per sectionFive order channels wind round one dispatcher. Piece by piece, a complete dispatch record, four separate modes, written rules, a lane map where empty legs are paired, dwell by account, milestones along each load, a status view for customer service, proof of delivery, truck state and a clean invoice join into one line where every load flows from order to cash.EmailPhoneTextEDISpreadsheetOne dispatcherDispatch recordComplete, or it waitsIntakePlanningExecutionExceptionDispatch rulesHours, certs, border, trailerYou can overrideDwell by accountCustomer serviceSees statusPODTruck downNever dispatchedInvoiceClean invoice, faster cash
  1. Everything in one person's head

    Trucks were booked, revenue was steady and leadership believed it needed more drivers.

    Orders came in by email, phone, text, EDI and spreadsheet. One senior dispatcher held it all together. She knew which drivers crossed the border, which trailers fit which docks, who had hours left, which customers kept drivers waiting and where every trailer was.

    None of it was written down. The company ran on her memory.

    Where it startedFive order channels wind round one dispatcher. Everything depends on her.EmailPhoneTextEDISpreadsheetOne dispatcherDispatch recordComplete, or it waitsIntakePlanningExecutionExceptionDispatch rulesHours, certs, border, trailerYou can overrideDwell by accountCustomer serviceSees statusPODTruck downNever dispatchedInvoiceDispatch in one head
  2. No complete record, no planning

    Orders often arrived without the weight, dimensions, dock hours, commodity, hazmat status, appointment, equipment type, references or billing terms.

    Now every order has to become a complete dispatch record first. If something is missing, the order waits at intake. Dispatchers stop chasing customers for details an hour before pickup.

  3. One job at a time

    The dispatcher used to take orders, plan trucks, watch moves and fight delays all at once. Every few minutes she rebuilt the state of the fleet from new messages.

    Now the work has four modes. Intake completes the record. Planning matches driver, truck and route. Execution watches the moves. Exception handles delays. Each one gets full attention.

  4. Her rules, written down

    What she knew became rules. Driver location, hours left, certifications and border status. Trailer type and maintenance dates. What each load needs.

    The board now hides combinations that break a rule or waste a truck, so dispatchers choose from assignments that already work. They can still override any of them.

  5. Seeing the empty miles

    Each trip used to be planned on its own. Sometimes two trucks drove empty between the same two cities.

    Now the board shows where every truck is, where it is going and when it will be free. Empty legs are flagged and paired. Dispatch moves from moving loads to running a network: revenue per kilometre, revenue per driver hour and how well the equipment is used.

  6. Waiting time, priced by account

    The data showed that some customer docks kept drivers waiting more than two hours to load or unload.

    Now waiting time sits on each account. Leadership can charge detention, change appointment rules, adjust service windows or reprice an account that does not pay its way.

    HalfwayA complete record, four modes, written rules, empty legs paired and dwell tied to each account.EmailPhoneTextEDISpreadsheetOne dispatcherDispatch recordComplete, or it waitsIntakePlanningExecutionExceptionDispatch rulesHours, certs, border, trailerYou can overrideDwell by accountCustomer serviceSees statusPODTruck downNever dispatchedInvoiceDwell priced by account
  7. Milestones, not phone calls

    Drivers used to get instructions in calls and scattered texts.

    Now each load carries its own instructions: pickup details, reference numbers, dock rules and delivery contacts. Drivers update it in set steps: en route, arrived at pickup, loaded, departed, arrived at delivery, delivered, or exception.

  8. Status without calling dispatch

    Customer service used to call dispatch every time a customer asked where a load was. Each call pulled a dispatcher off the board.

    Now customer service sees every active load and its last milestone. Routine status questions are answered without touching dispatch.

  9. Proof at the dock

    Paperwork used to follow the truck back days later.

    Now a load is not delivered until proof of delivery is captured on the spot, with damage checked and the signature taken.

  10. Down trucks stay parked

    Dispatch and the shop used to keep separate lists, so a truck that was down could still be booked.

    Now every truck has one state that both sides see: available, assigned, loaded, down, maintenance due or restricted. A truck that is down is never offered for a load.

  11. A clean invoice, sooner

    With the proof captured at delivery, the invoice goes out clean, without days of paperwork in between.

    Cash comes in faster and accounting did not have to grow to do it.

    From the first order to the paid invoice, every load moves through one system, not one person.

    The finished systemEvery piece is in place. Loads run on milestones, proof is captured at the dock and the invoice goes out clean.EmailPhoneTextEDISpreadsheetOne dispatcherDispatch recordComplete, or it waitsIntakePlanningExecutionExceptionDispatch rulesHours, certs, border, trailerYou can overrideDwell by accountCustomer serviceSees statusPODTruck downNever dispatchedInvoiceClean invoice, faster cash

What changes

Manual status reporting drops 25–50% and customers get answers 25–50% faster. Avoidable logistics cost falls 10–30% with 50–90% fewer operational errors, and the work from order to invoice moves 50–90%

The typical range for this kind of system. Median outcomes across 55 projects since 2021. Ranges are medians, not guarantees. How we report numbers

No AI. Better process.

None of this needed AI or a new transport platform. A complete record, written rules, set milestones and one state for every truck did the work.

That matters if you run a fleet: you can start with the tools you already have.

What comes next

Once every load, truck and driver lives in one record, automation can sit on top: suggesting the best match, flagging empty legs before they happen and drafting the invoice the moment proof lands. Dispatchers still make the calls.

Curious what empty miles cost you? Work it out in a minute.

Dispatch that runs without one hero.

Want the same for your fleet? Book a call and we will look at your dispatch process with you.

Book a callScore your business

Systems built to SOC 2, ISO 27001 and PIPEDA/PHIPA controls.