Truck Dispatcher Service Agreements: What They Should Cover
A dispatcher-carrier service agreement should address: scope of services (and exclusions), precise fee and invoicing terms, each party's responsibilities, term and termination provisions, liability and confidentiality, and dispute resolution. This guide describes components only — it is not legal language and not legal advice. Consult an attorney for your actual agreement.
Every professional dispatcher-carrier relationship runs on a written service agreement — the document defining what the dispatcher does, what it costs, who's responsible for what, and how either side exits. It's the foundation of trust in a business where money, liability, and livelihoods intersect daily.
This guide describes the components a solid agreement should address: service scope, fee structures, invoicing terms, responsibilities, termination provisions, and dispute handling. It describes components only — this is not legal language and not legal advice. Have a qualified attorney draft or review your actual agreement. What follows is the map, not the territory.
Why Written Agreements Matter
Verbal agreements and handshake deals fail at exactly the moment they matter most: when there's a dispute. The carrier who 'understood' the fee differently, the dispatcher who 'thought' tracking was included, the termination that one side considers effective immediately and the other considers a month away — every one of these is preventable with a written agreement.
Written agreements also professionalize the relationship from day one. The onboarding process — agreement presented, terms discussed, signatures collected before the first load — signals that both sides take the business seriously. Carriers evaluating dispatchers notice the difference between a professional onboarding and a casual 'let's just start.'
And agreements protect both sides symmetrically. The dispatcher gets defined payment terms and scope boundaries; the carrier gets defined service commitments and exit rights. Good agreements don't favor one party — they create the clarity that lets the relationship focus on freight instead of friction.
Component 1: Scope of Services
The agreement should specify exactly what the dispatcher does: load searching and booking, rate negotiation, appointment scheduling, load tracking and check calls, paperwork management (rate confirmations, setup packets), and invoicing support. Vague 'dispatch services' language invites scope disputes; enumerated services prevent them.
Equally important is what the dispatcher doesn't do. The agreement should state plainly that the dispatcher is not the carrier's safety department, insurance agent, tax advisor, or legal counsel — and not the carrier itself. Dispatchers arrange freight; carriers haul it, insure it, and bear the operating liability. Clear boundaries protect both sides from dangerous misunderstandings.
Consider addressing service standards: response time commitments, communication methods, reporting frequency. These don't need to be onerous — but writing down 'dispatcher provides load status updates at agreed intervals' sets expectations that verbal understandings can't.
Component 2: Fee Structure and Invoicing
The agreement must define the fee precisely: whether it's a percentage of load revenue or a flat per-truck amount, what the percentage or amount is, and what revenue figure it applies to (linehaul only? including fuel surcharge? accessorials?). Ambiguity here is the single most common source of dispatcher-carrier disputes.
Invoicing terms need equal precision: how often invoices issue (weekly is common in the industry — JackRick Logistics, for example, invoices carriers every Friday), when payment is due, what payment methods are accepted, and what happens with late payment. The invoicing rhythm should be predictable enough that neither side thinks about it.
Address the edge cases in writing: how fees apply to cancelled loads, disputed loads, or loads where the carrier wasn't paid by the broker. These situations arise regularly, and the agreement should state the rule before the situation occurs — not after, when both sides are already entrenched.
Component 3: Responsibilities of Each Party
The carrier's responsibilities typically include: maintaining valid operating authority and insurance, providing accurate truck and driver information, communicating status honestly and promptly, executing dispatched loads professionally, and paying the dispatcher per the agreed terms. The agreement should state these plainly — they're the carrier's half of the bargain.
The dispatcher's responsibilities typically include: diligent load sourcing, professional rate negotiation, timely communication, accurate documentation, and acting in the carrier's interest within the agreed scope. Framing these as commitments (not promises of specific results — no dispatcher can promise freight that doesn't exist) keeps expectations honest.
Information-sharing duties deserve explicit mention: the carrier must inform the dispatcher of equipment issues, driver availability changes, and anything affecting capacity; the dispatcher must inform the carrier of market conditions, problem loads, and anything affecting revenue. The agreement should make mutual transparency a stated obligation, because the business runs on information.
Component 4: Term and Termination
The agreement should state its term: whether it's open-ended, fixed-period, or auto-renewing. Many dispatcher-carrier relationships run open-ended with termination rights — the flexibility suits an industry where needs change. Whatever the structure, write it down; 'we'll figure it out' isn't a term.
Termination provisions need a notice period — 30 days is a common example of one model, giving both sides time to transition. The agreement should specify how notice is delivered (written notice to a defined address or email), when it takes effect, and what happens to in-progress loads during the notice period.
Also address termination for cause: what constitutes a material breach, whether there's a cure period, and the mechanics of immediate termination when warranted. And state the financial wrap-up clearly: final invoicing, payment timing for outstanding amounts, and return or deletion of confidential information. Clean exits preserve reputations; messy ones destroy them.
Component 5: Liability, Confidentiality, and Disputes
Liability limitations are standard: the agreement should address the extent of the dispatcher's liability for load problems, consistent with the reality that the dispatcher doesn't control the truck, the road, or the shipper. This is precisely the section where attorney drafting matters most — liability language has legal consequences that general guidance can't safely specify.
Confidentiality provisions protect both sides' business information: the carrier's rates and customer data, the dispatcher's broker relationships and methods. Define what counts as confidential, how long the obligation lasts, and the exceptions (information that's public or independently developed).
Dispute resolution should specify the process before disputes arise: good-faith negotiation first, then mediation or arbitration, with the governing law and venue stated. Litigation is the expensive failure mode; a well-drafted dispute clause makes the cheaper paths the default. Again — attorney territory, not DIY.
Getting It Right: Process Recommendations
Have an attorney draft or review the agreement. This recommendation appears throughout this guide because it matters that much: the cost of professional drafting is trivial compared to the cost of a dispute under an ambiguous agreement. Find an attorney familiar with transportation — generic business lawyers miss industry-specific issues.
Review the agreement annually or when your service model changes. A solo dispatcher who adds staff, a flat-fee service that shifts to percentage pricing, a regional operation that goes national — each change can obsolete provisions. The agreement should evolve with the business.
Present the agreement professionally and walk through it with new carriers. The signing conversation — explaining each section in plain language, answering questions, confirming understanding — builds the trust that makes the written terms almost unnecessary. The strongest agreements are the ones both sides understand so well they never need to read them again.
Important: This Is Not Legal Advice
To be explicit: this guide describes the components a dispatcher-carrier service agreement should address. It does not provide legal language, does not constitute legal advice, and cannot substitute for an attorney's review of your specific situation, state law, and business model.
Transportation law varies by state, and contract law is full of jurisdiction-specific traps — what works in one state may fail in another. The components above are the map; your attorney draws the actual route. Consult a qualified transportation or business attorney before using any service agreement with real carriers and real money.
Treat legal infrastructure as a business investment, not an expense to minimize. The dispatchers who invest in proper agreements, proper entity structure, and proper insurance build businesses that survive disputes, audits, and bad luck. The ones who don't are gambling — and the house always collects eventually.
Key takeaways
- Written agreements prevent the disputes that handshake deals create — get signatures before the first load.
- Define scope precisely, including what the dispatcher does NOT do (not the carrier, not its safety department).
- Fee terms must be exact: percentage or flat, what it applies to, invoicing rhythm, edge cases.
- Termination provisions need a notice period (30 days is one common model) and clean financial wrap-up.
- Liability, confidentiality, and dispute resolution are attorney-drafted territory — not DIY.
- This guide describes components only; consult a qualified attorney for actual legal language.
Questions carriers ask
What should a dispatcher-carrier service agreement cover?
Scope of services (what's included and excluded), fee structure and invoicing terms, each party's responsibilities, term and termination provisions (including notice periods), liability limitations, confidentiality, and dispute resolution. This describes components only — consult an attorney for actual legal language.
What termination notice is typical in dispatcher agreements?
A 30-day written notice period is one common model, giving both sides time to transition in-progress loads and wrap up financially. The agreement should specify how notice is delivered, when it takes effect, and how outstanding amounts are settled.
Should the agreement say what the dispatcher doesn't do?
Yes — explicitly. The agreement should state the dispatcher is not the carrier's safety department, insurance agent, tax advisor, or the carrier itself. Clear boundaries prevent dangerous misunderstandings about liability and responsibility.
How should fees be defined in the agreement?
Precisely: percentage or flat fee, the exact figure, what revenue it applies to (linehaul, fuel surcharge, accessorials), invoicing frequency, payment due dates, and how edge cases (cancelled or disputed loads) are handled. Fee ambiguity is the most common dispute source.
Can I use a template agreement from the internet?
A template can show you the components, but have an attorney draft or review the agreement you actually use. Templates aren't written for your state, your service model, or your risk profile — and liability language has legal consequences that general guidance can't safely specify.
Is this guide legal advice?
No. This guide describes agreement components in general terms only. Consult a qualified transportation or business attorney for legal advice specific to your situation and jurisdiction.