Table of Content
- “Hit gross of $X by month three” is the wrong starting line
- Four behaviors to name in week one
- What the dispatcher should be naming back to you in week one
- “They’ll figure it out from the contract” assumes the contract covers operational rhythm. It doesn’t.
- The week-three check-in that catches drift before it’s drift
- Where the desk hits the standard and the relationship still doesn’t fit
Most operators set expectations on results. Real ones set expectations on behavior. Results follow.
Week one with a new dispatcher is full of soft language. Partnership. Trust. Open communication. None of it survives a Tuesday afternoon when a load drops and the reload window collapses.
The expectations that carry through month three are behavioral. They name what the desk does, when, and what the operator does in response. Written down on day two, not implied by the contract.
“Hit gross of $X by month three” is the wrong starting line
Gross targets miss the point. A desk can hit a gross number with bad bookings, or miss it with the right bookings on a soft week. Setting expectations on gross signals you’ll judge the desk on output you can’t fully control.
| Week-one behavior | Standard |
|---|---|
| Daily check-in | Once per day, set time |
| Reload booking | Before delivery, not after |
| Doc forwarding | Within 24 hours |
| Weekly P&L call | Friday, brief, structured |
The expectations that carry are the ones the desk can be measured on directly. When they call. In what format. How they handle a load that goes sideways. Whether they file detention every Friday or skip two weeks and lose the window.
That’s the standard: behavioral, observable, weekly. Gross becomes a downstream metric, not the operating goal.
Four behaviors to name in week one
Write these down on day two, send them as a one-page document, and ask for acknowledgement in writing.
- Reload booked before delivery. Not after. Cold reload booking past the dock is the gap your week is paying for. Standard: every load gets a reload conversation before the truck rolls into the receiver, except Friday afternoons into a regional shutdown.
- Detention claimed on every eligible event. Two-hour free time exhausted, the clock starts. Submitted with a check call timestamp, signed BOL, and a written explanation, batched Friday. Standard: if it happened, it gets billed. Don’t decide for the broker whether they’ll pay.
- Loaded RPM floor named in writing. Pick a number you’ll hold against ATRI’s $2.27 marginal cost baseline. Most one-truck operators land between $2.10 and $2.45 by lane and trailer type. The number isn’t aspirational: it’s the line below which the desk doesn’t book without calling first.
- Friday P&L review, fifteen minutes, weekly. Same five lines from your settlement: gross, deadhead percentage, loaded RPM, detention claimed and collected, dispatched-vs-paid mile gap. Same time every week. The dispatcher names the calls they made and what changed.
These four are not negotiable. They are the operational fingerprint of the relationship.
What the dispatcher should be naming back to you in week one
Expectations work both ways. A working desk names what it needs from you in week one. A flipper absorbs yours and disappears into them. A working truck dispatching service names its own back to you.
Things they should be naming: pickup-window discipline (at the dock when you said, every time), check-call cadence (text on the hour, no skipping), document turnaround (BOL and rate-con back inside 24 hours), and honesty about home time (not claiming Saturday and then not answering Friday).
If the dispatcher doesn’t push back with their own expectations, they’re too polite or too desperate. Neither is a working dynamic. The desks that produce on month three set expectations both ways from week one.
Before week one closes, write down the two or three numbers you’ll hold the desk to and put them in front of them. The expectations nobody wrote down are the ones that get missed.
“They’ll figure it out from the contract” assumes the contract covers operational rhythm. It doesn’t.
Most dispatch contracts are about money, exit, and authority, not operational rhythm. They say fee structure, cancellation notice, broker-book ownership. They do not say “reload is booked before delivery” or “Friday is the P&L call.”
That’s the gap. The contract is a legal document; the expectations doc is the operating one. and it usually does more for the relationship.
Operators who skip the doc end up in month three having a relationship-temperature conversation. They feel the desk isn’t running; the desk feels the operator is moving goalposts. Both are right, because nobody wrote down what running looked like in week one.
The week-three check-in that catches drift before it’s drift
By week three, behaviors either became habits or didn’t. Schedule a fifteen-minute call on that Monday with one question: have any of the four slipped, and why.
The honest answer from a working desk is usually one slip with a structural reason: detention claims fell behind on a billing software issue, or the RPM floor got missed once while the operator was out of pocket. Both are recoverable.
The non-recoverable answer is “everything’s fine” when the settlement says it isn’t. The behaviors are the early signal, the settlement the trailing one. Catching drift in week three is cheaper than renegotiating in month two.
Where the desk hits the standard and the relationship still doesn’t fit
Sometimes the four behaviors land cleanly and the relationship still doesn’t reach month four. Reload before delivery, detention claimed every week, RPM floor held, Friday P&L call, and the operator still leaves. The reason is usually personality fit, not workflow: the desk runs the rhythm, but it has no warmth, or too much warmth and no operational edge, or fits a different operator than you turn out to be.
That’s allowed. Week one’s expectations are the operational floor, not a guarantee of fit. Hitting them earns the desk month two, not an automatic month four.
The standard from week one is a one-page expectations doc, signed by both, with reload timing, detention discipline, RPM floor, and a Friday P&L call written into it. That is what makes month three feel earned, not negotiated. The settlement votes on whether the rhythm held. If it didn’t, the renegotiation has a document to walk against. If it did, the fee structure can settle into something both sides live with.
