How to Build an Auto Transport Dispatch Board That Shows the Real Work

A dispatch board is useful only when it shows the operation as it really is.

If every load sits in “available” until someone remembers to drag it, the board is decoration. If a load can reach “dispatched” without an approved carrier, agreed price, or pickup plan, the status is fiction. If every exception becomes a red note, managers cannot see which problem needs attention first.

Build the board as a shared operating model: a small set of shipment states, clear movement rules, and visible ownership.

Define the unit of work

Decide what one card represents. For most broker workflows, it should be one shipment or order with its vehicles, route, customer, commercial terms, assigned carrier, documents, and communication attached.

Avoid creating separate cards for the quote, dispatch task, pickup, and billing record unless they remain linked automatically. Split records invite conflicting dates, prices, and contacts.

The same load should move from the sales-to-dispatch handoff through assignment and delivery.

Use stages that describe real state

A practical board might include:

Stage	Meaning	Exit condition
Dispatch ready	Required booking data and approvals are complete	Dispatcher accepts ownership
Sourcing	The team is actively seeking a carrier	A serious offer or assignment path exists
Offer in progress	A specific carrier and rate are being evaluated	Offer declines, expires, or becomes an approved assignment
Assigned	Carrier, price, compliance, and terms are approved	Pickup plan is confirmed
Pickup scheduled	Contacts and window are communicated	Pickup is confirmed or an exception is raised
In transit	Vehicle is picked up	Delivery is confirmed
Delivered	Delivery event is recorded	Required documents and balance move to completion

Add a blocked or exception view, but do not use it to erase the real stage. A pickup-scheduled load with a carrier fall-off is still a pickup-stage emergency, not an anonymous blocked card.

Write entry and exit rules

Every column needs a definition the team can test.

For example, “assigned” may require:

• Carrier identity and authority checked
• Insurance and equipment fit reviewed
• Agreed carrier pay recorded
• Rate confirmation or dispatch agreement complete
• Driver and dispatch contacts present
• Customer-facing assignment approved for release
• Pickup and delivery constraints acknowledged

The carrier should complete onboarding and assignment checks before the card moves. If an approved exception exists, display its owner and reason.

Keep tasks inside the stage

The board answers “where is the load?” Tasks answer “what happens next?”

Every active card should show:

• Named owner
• Next action
• Due time
• Last meaningful activity
• Important constraint
• Current exception, if any

Do not create columns called “call customer,” “send rate confirmation,” or “waiting on COI.” Those are work items within a shipment state. Too many columns turn the board into a maze and make aging meaningless.

Make readiness visible at a glance

The card should surface only the information dispatch needs to choose its next move:

• Route and approximate mileage
• Vehicle and operability
• First available date and timing constraints
• Open or enclosed requirement
• Customer price, carrier target, and current margin
• Source or posting status
• Offer count and best current offer
• Required documents or missing fields
• Owner and next action

Everything else can live in the detail view. A board crowded with full addresses, entire notes, and message transcripts hides the signal.

Model offers without losing the history

Carrier offers and counter-offers should remain attached to the load. Record:

• Carrier
• Offered amount
• Who made the offer
• Date and time
• Expiration or response deadline
• Equipment and timing proposed
• Counter-offer history
• Final result and reason

Do not overwrite $900 with $975 and lose the negotiation. The sequence explains margin changes and helps evaluate future lane pricing.

Treat exceptions as structured work

Use exception types such as:

• Price or margin approval needed
• No carrier response
• Carrier fall-off
• Compliance or insurance review
• Missing customer information
• Vehicle or equipment mismatch
• Pickup contact unavailable
• Weather or route disruption
• Missing BOL or delivery confirmation
• Payment hold

Each exception needs severity, owner, next action, and due time. Managers should be able to filter critical pickup risks separately from routine paperwork follow-up.

For carrier reliability failures, use the prevention and recovery steps in the no-show and fall-off playbook.

Automate events, not judgment

Useful board automation includes:

• Creating a follow-up when a load enters sourcing
• Flagging a card with no activity for a defined period
• Requiring fields before a move to assigned
• Logging who moved the card and when
• Sending approved customer updates after selected events
• Alerting when a pickup window is at risk
• Requesting delivery paperwork after delivery confirmation

Avoid automatic assignment or customer promises based on incomplete data. Automation should make missing work visible and execute approved routines.

Establish the daily rhythm

The board becomes trustworthy through use.

Morning review

• Pickups due today and tomorrow
• Loads with no carrier or unconfirmed assignment
• Active exceptions
• Missing documents or contacts
• In-transit loads without a current update

Midday control

• New dispatch-ready loads
• Offers awaiting a response
• Aging sourcing cards
• Price approvals
• Slipping pickup windows

End-of-day handoff

• Overnight or next-morning pickups
• Customer promises made
• Unresolved exceptions and next actions
• Carrier contact status
• Ownership for anything that cannot wait

Do the review from the board. If the real meeting happens from a spreadsheet, the board will drift.

Measure flow, not card movement

Useful metrics include:

• Time from dispatch ready to active sourcing
• Time to approved assignment
• Age in each stage
• Offers per assigned load
• Offer acceptance and carrier fall-off rates
• Pickup-window misses
• Loads without an owner or next action
• Carrier-pay increases during dispatch
• Delivery-to-BOL completion time
• Manual status corrections

Pair the board with the broader auto transport broker KPIs. Fast movement is not healthy if it creates low margins or missing paperwork.

Audit the board with one load

Choose a shipment that had a problem and replay it:

1. When did it become dispatch ready?
2. Who accepted it?
3. Which offers were made?
4. What carrier checks occurred?
5. When did the assignment become customer-visible?
6. What exception appeared first?
7. Who owned the next action?
8. What changed in price, timing, or terms?
9. Were pickup, delivery, and paperwork confirmed?

If the card cannot answer those questions, fix the data and movement rules before adding another view.

CarShipOS connects a Kanban dispatch board with carrier checks, offers, documents, customer communication, and payment on one load. See the dispatch workflow, or book a demo using a recent shipment.