The same desk produces different results for different drivers, and the difference is rarely favoritism. Dispatch is a working relationship with inputs, and the operators who feed it well get measurably better freight — not because they are liked, but because they are plannable.
What a planner is actually solving for
A planner is building a sequence, several moves deep, against constraints that move all day: which trucks are where, which will be empty when, what the shipper's window is, what the receiver will actually accept, and how many hours each driver has left under Part 395. The load in front of them is one link in that sequence, and the value of the link depends on what it makes possible next.
Understanding that reframes the whole relationship. You are not asking for favors from a person with a list of loads. You are one variable in a scheduling problem, and the quality of the plan depends on the quality of the information attached to your variable. Drivers who supply good information are cheap to plan for, and cheap-to-plan-for trucks get planned into the good chains.
Give real constraints, not polite ones
A plan built on flexibility you do not have is fragile, and the fragility surfaces as your empty miles. If you will not run the Northeast, will not sit more than a few hours, need to be home on the twentieth, or will not take a tarp load without the tarp pay agreed on the confirmation — say it plainly, once, and in a form the desk can keep.
Say it in the forms a planner uses: a geographic radius, a dollar figure or a rate floor, a day of the week, an hour count. 'Somewhere closer' is not a constraint; 'not more than a hundred empty miles unless the rate clears my floor' is one. Real constraints stated early beat surprise refusals stated late, every time, because the late refusal costs the desk a rebuild and costs you the load that was going to follow.
Then hold them. Constraints that change weekly are indistinguishable from no constraints at all, and a planner will rationally start assuming the safe version — which is the cheap version.
Close the loop after the load
The desk sees the rate confirmation. It does not see the three-hour dock, the shipper who loads at will-call only, the receiver with nowhere to park overnight, the yard that needs a trailer you cannot back into. A thirty-second debrief — 'good rate, brutal facility, four hours on the dock' — turns your experience into information the desk keeps.
Do it on the good loads too. A planner who knows which facilities load fast and which lanes reload cleanly can aim at them deliberately, and the operator who supplied that knowledge is the one it gets aimed at. Drivers who report back are, in effect, training their own load filter, and it is the highest-return five minutes in the job.
Keep the debrief factual and short. Times, conditions, whether you would take it again. Nobody builds a plan out of an adjective.
How should you escalate when something is off?
With numbers, in writing, early. Empty miles trending up for three weeks, a deduction you cannot trace to a lease clause, a lane that used to work and stopped: raise each one specifically — the measurement, the period, and the question 'what is the plan?' Numbers travel through an organization in a way frustration does not, and a written record protects both sides of a relationship that is worth keeping.
Bring your own measurements rather than impressions. Your deadhead percentage by week, your gross per loaded mile, your total deductions as a share of gross: the four numbers off your settlements are the vocabulary this conversation runs on. An operator who arrives with a series is having an operations discussion. An operator who arrives with a mood is having an argument.
And separate the two kinds of problem, because they go to different places. A planning problem — lanes, markets, empty miles, home time — is a conversation with the desk. A money problem — a chargeback with no clause behind it, a settlement line you cannot verify — is a documents question governed by your lease and 49 CFR 376.12(h), which entitles you to the paperwork that proves each charge. Mixing them makes both harder to solve.
Treat the desk like a business partner, because it is one
Answer the phone. Update your ETA the moment it moves rather than when you arrive. Flag a breakdown immediately, even when it is embarrassing, because the desk can re-plan a truck that is down and can do nothing at all about a truck that has gone quiet. Send your documents in the form and the timeframe the lease asks for — under Part 376 the settlement clock starts when your paperwork is in, so slow paperwork is a cash-flow decision you are making about yourself.
Reliability is the whole currency here. A planner spends the best freight on the trucks whose word holds, because those are the trucks a four-load chain can be built on. None of this is about being liked. It is about being the variable in the scheduling problem that never blows up the plan, and that is a reputation you build in ordinary weeks rather than in dramatic ones.
How this shows up at Arrow
The desk here is staffed 24/7, and dispatch builds plans around your home base, your preferred states and your home time — the three constraints this article says to state clearly, which is not a coincidence. Both divisions run on one authority, so hotshot and CDL-A planning sit in the same place rather than in two organizations that have to phone each other.
Two things to put in writing at the start rather than discovering later: your standing constraints, in the planner's own units, and how tarping or oversize and permit work gets quoted and who orders what, since those are agreed per lane. Then keep your four settlement numbers weekly and bring them to the desk monthly. That is the entire method, and it works better here than any recruiting pitch does.