Dispatch Best Practices

DISPATCH BEST PRACTICES Process • Communication Use: fewer issues + cleaner handoffs

Dispatch Best Practices: simple standards that prevent expensive mistakes.

This page is a practical playbook for dispatchers and carriers — focused on repeatable workflows, clear communication, and document discipline. Use it to reduce missed details, prevent preventable claims, and run cleaner loads from rate confirmation to POD.

  • Set a consistent load workflow: rate confirmation → pickup → tracking → delivery → POD.
  • Standardize updates (what to say, when to say it, and what proof to collect).
  • Catch problems early: appointment changes, dwell, OS&D, and accessorial disputes.
  • Keep a clean paper trail that supports billing, compliance, and claims defense.
Best habit
Document everything
Most preventable
Missed appt details
Big lever
Exception updates
Next best click
Dispatch = profit + service Best practice: plan the week As-of: Jan 2026

Dispatch Best Practices: The System That Keeps Trucks Moving and Margins Protected

Great dispatch isn’t “calling brokers.” It’s running a repeatable operating system: pre-plan, negotiate clean terms, protect HOS, reduce detention, document exceptions, and close the week with proof.

This briefing gives you a practical dispatch OS, a visual dispatch board layout, the KPIs that actually matter, and playbooks for the moments where fleets lose money (detention, TONU, lumper surprises, OS&D, and claim chaos).

Related: How Dispatching WorksRate Negotiation TipsLoad Planning StrategiesBroker Red FlagsHOS Rules ExplainedHOS / ELD Simulator


The Dispatch OS (inputs → decisions → outcomes)

Dispatch is a control room. You’re converting constraints (HOS, appointments, equipment, weather, customer rules) into outcomes (RPM, on-time service, low claims, low deadhead, and repeatable cashflow).

Dispatch OS map Use as a weekly checklist
Inputs (what you control)

Driver readiness, HOS projection, equipment status, lane plan, target RPM, customer rules, and your “no-go” list.

Daily: HOS + parking Weekly: lane plan
Outputs (what the week becomes)

On-time %, loaded miles %, deadhead %, detention hours, accessorial capture, and claims exposure.

Goal: repeat lanes Goal: fewer surprises
Best dispatchers don’t “fix problems.” They prevent repeats: consistent appointment discipline, consistent documentation, consistent claim response, consistent weekly close.

The 5 rules of elite dispatch

  • Plan the week, not the day. Tuesday decisions create Friday failures.
  • Protect the 14. Dock time destroys service before driving hours do.
  • Negotiate terms, not just rate. Detention, TONU, lumper, and appointment rules are profit.
  • Document exceptions instantly. If it’s not written, it didn’t happen.
  • Run a weekly close. Track repeats and coach the pattern.

A hard truth

A fleet can win rate negotiations and still lose the week on detention, late arrivals, and preventable claims. Dispatch best practices are a safety system as much as a revenue system.

Tie dispatch to compliance: CSA ScoresTruck InsuranceClearinghouse


The dispatch KPI dashboard (track what actually moves money)

KPIs shouldn’t be “more dashboards.” They should be levers: if a number moves, your behavior changes the same week.

Dispatch KPIs (practical) Targets vary by lane
Loaded miles %Higher is better
If loaded % drops, you’re bleeding profit through deadhead or poor backhaul planning.
Deadhead %Lower is better
Deadhead is a dispatch decision. Reduce it with lane discipline and “no-go” freight rules.
Detention hours / loadProfit killer
Track who causes it and bill it. Detention + late fees are a negotiation + documentation game.
On-time pickup/deliveryService
On-time is mostly planning (appointments + parking) and fewer surprises (pre-calls, checks).
Accessorial captureFree margin
If you’re not billing lumper/TONU/detention consistently, you’re paying for customer mistakes.
HOS risk indexProtect the 14
“Risk” = late-week 70-hour wall + tight 14-hour windows + no parking plan.

If you want one “north star” dispatch metric: track repeat problems. Same shipper, same lane, same driver, same issue = a process failure.


The visual dispatch board (week view)

A great board answers three questions instantly: Where is the truck? What’s next? What’s the risk? This example is a layout you can mimic in a TMS or even a spreadsheet.

Week board (illustrative) Scroll on mobile
Driver / Unit
Mon
Tue
Wed
Thu
Fri
Sat
Sun
D-104 • Tractor 17 Boise → SLC → Reno
HOS: clean
Lane: West
Pickup Boise 07:00
Appt
Deliver SLC 10:30
Dock risk
Pickup SLC 16:00
Pre-call
Deliver Reno 08:00
On-time
Reload Reno 13:00
Rate check
Transit West lane
Plan
Reset 34 hr
Weekly
D-112 • Tractor 22 Portland → Boise → Denver
HOS: tight 14
Risk: detention
Pickup PDX 09:00
Late risk
Dock 4+ hrs
Detention
Transit Boise
Parking
Pickup BOI 06:00
Break plan
Transit East
70 watch
Deliver DEN 07:30
Appt
Recovery next load
Backhaul

Board rules (simple)

  • One line for risk: HOS, detention, weather, or broker uncertainty.
  • One line for next: next pickup time + required pre-call.
  • One line for cash: rate con confirmed + accessorial terms noted.

If your board doesn’t show “risk” and “next,” dispatch turns into firefighting.

Pro tip: pre-call discipline

Pre-calls prevent half of dispatch chaos: confirm appointment, address quirks, check-in rules, and “last receiver” timing. Write it down before the driver arrives.

Pair with: Load Planning Strategies


Playbooks (what great dispatchers do on purpose)

These are the repeatable routines that keep margins protected. Pick one playbook, implement it for a week, then add the next.

Dispatch playbooks No scripts
Morning pre-plan (10 minutes)
  • 1) Confirm today’s appointments + check-in rules.
  • 2) Verify HOS projection + parking plan (protect the 14).
  • 3) Confirm rate con + accessorial terms are in writing.
  • 4) Identify the top risk load and get ahead of it (pre-call).
Lane discipline (the real cheat code)
  • Keep a lane list: preferred shippers, preferred receivers, preferred brokers.
  • No-go list: slow pay, appointment games, detention denial.
  • Protect repeat lanes: build backhauls before you accept the headhaul.
  • Track dwell: the shipper with the worst dwell gets fixed or dropped.

HOS planning: HOS Rules Explained • Practice: HOS / ELD Simulator

Negotiate terms (not just rate)
  • Detention: start time, free time, hourly rate, how to document.
  • TONU: what qualifies, required proof, fee amount.
  • Lumper: who pays, reimbursement process, receipt rules.
  • Appointments: FCFS vs strict, late policy, reschedule window.
Documentation mindset
  • If it isn’t written: assume you won’t get paid.
  • Time-stamps: arrival, check-in, door time, departure.
  • Proof pack: photos, messages, POD/BOL, lumper receipt.
  • Close the loop: bill accessorials within 24 hours.

Deep dive: Rate Negotiation Tips • Avoid traps: Broker Red Flags

Detention recovery (same-day)
  • 1) Confirm check-in time with receiver/shipper.
  • 2) Send a detention notice before free time expires.
  • 3) Capture proof: door time, messages, BOL notes, photos.
  • 4) Bill fast with a clean packet (no drama, just proof).
When a load goes bad
  • OS&D/claims: preserve evidence, notify broker, document temperatures/seals.
  • Late risk: pre-notify and propose a new ETA early (don’t surprise).
  • HOS squeeze: plan split sleeper or reset if needed—stay legal.
  • Re-power: know your re-power process before you need it.

Claims mindset: Truck Insurance Basics • Compliance backbone: DOT Audit Guide

Driver close (15 minutes)
  • HOS: review violations, fix the repeat pattern.
  • Service: identify late root cause (dock, traffic, planning, receiver rules).
  • Equipment: defects logged → repaired → proof filed.
  • Next week: plan parking and appointment strategy early.
Dispatcher close (15 minutes)
  • KPI review: detention, deadhead, accessorial capture, on-time.
  • Lane review: keep winners, drop repeat pain facilities/brokers.
  • Cash review: confirm invoicing completeness (no missing PODs).
  • Coaching: one skill focus for the team next week.

Compliance + risk: HOS RulesCSA ScoresClearinghouse


Templates (copy/paste ready)

These are quick templates to protect revenue: pre-call script, detention notice, accessorial packet checklist, and a weekly close sheet.

Dispatch templates No scripts
Pre-call script (shipper/receiver) Copy/paste
PRE-CALL SCRIPT (DISPATCH) Hi, this is ______ with ______. Our driver is scheduled for: - PU/DEL: ______ on ______ at ______ - Load/Ref #: ______ - Trailer/Unit: ______ Quick confirms: 1) Appointment is confirmed? (yes/no) If no, what is the correct time? 2) Check-in procedure? (gate, phone #, door assignment, paperwork) 3) Any special rules? (FCFS, lumper, PPE, seal policy, staging) 4) Expected dwell today? (estimate) 5) After-hours or last receiver time? (if applicable) Notes: - Contact name / time: ______ - Any issues discovered: ______

Pre-calls prevent “surprise failures” and protect on-time service.

Detention notice (send before free time expires) Email/text
SUBJECT: Detention notice — Load ______ / Ref ______ Hi ______, Driver arrived and checked in at: ______ (local time) Free time ends at: ______ We are now tracking detention per the rate confirmation / agreed terms. Proof (available): - Arrival/check-in time-stamp - Messages / gate notes - Photos (if needed) - BOL/POD notes Please confirm detention billing process and required documentation. Thank you, Name / Phone / Company

The earlier you notify, the cleaner the billing outcome.

Accessorial packet (detention / TONU / lumper) Checklist
ACCESSORIAL PACKET CHECKLIST Detention: [ ] Arrival time + check-in proof [ ] Door time / start time proof [ ] Release/departure time [ ] Messages with facility/broker [ ] Rate con terms (free time + hourly) TONU: [ ] Rate con terms for TONU [ ] Cancellation message/time [ ] Driver location proof / attempt proof [ ] Any facility refusal notes Lumper: [ ] Lumper receipt (photo) [ ] Proof of payment (if paid) [ ] Rate con terms for reimbursement [ ] POD/BOL notes if required Billing: [ ] Invoice includes load/ref, dates, and supporting attachments [ ] Sent within 24 hours of completion
Weekly close sheet (dispatch) Print this
WEEKLY DISPATCH CLOSE (ONE-PAGE) 1) KPI snapshot: - Loaded miles %: ____ Deadhead %: ____ - Detention hours: ____ Accessorial capture: ____ - On-time %: ____ Claims/incidents: ____ 2) Repeat problems (circle): - Same facility detention - Same broker issues - Same lane deadhead - Same driver HOS squeeze - Same paperwork missing 3) Fix for next week (one): ___________________________________________ 4) Owner: ___________________________________________ 5) Proof to collect: ___________________________________________

One fix per week beats ten “ideas” that never get implemented.

Want the “dispatch fundamentals” sequence? Start with How Dispatching Works, then stack: NegotiationPlanningRisk.


FAQ

What is the #1 dispatch best practice?
Plan the week, not the day. The best dispatchers protect the 14-hour window, pre-call appointments, and maintain a “next load” plan before committing to the current one.
Why do good rates still produce bad weeks?
Because the week gets lost on detention, missed appointments, deadhead, and unbilled accessorials. Rate is only one part of dispatch profitability.
What KPIs should a small fleet track?
Loaded miles %, deadhead %, detention hours, on-time %, accessorial capture, and HOS risk projection. These change behavior fast.
How do I reduce detention?
Pre-call, document arrival/check-in/door times, send detention notice early, and stop taking repeat-problem facilities without pricing the risk.
How does dispatch affect CSA and insurance?
Dispatch decisions drive HOS compliance, fatigue risk, appointment pressure, and claims exposure. That’s why dispatch is a safety system, not just a sales function.

Quick next steps

If you want immediate dispatch improvement (this week):

  • 1) Implement pre-calls for every appointment (use the template).
  • 2) Track detention hours and bill it consistently (proof pack).
  • 3) Add “risk” and “next” to your dispatch board (no more guessing).
  • 4) Run a weekly close: pick one repeat problem and kill it.

Related: HOS RulesCSA ScoresInsuranceClearinghouse
Back to top