First 30 days with a dispatcher: what to expect (and what to push back on)

Month one is calibration, not handoff. The operators who treat it like a handoff lose the truck to someone else’s load board.

You signed with a dispatcher. Now what. The honest answer is that the next 30 days decide whether this becomes leverage or another cost line. The dispatcher is learning your truck. You’re learning their booking instincts. Both sides are testing where the other will hold the line.

If you go quiet and “let them do their thing,” you get the lanes that are easiest for them to book. Not the lanes that pay you best. That gap shows up in week three, when your average loaded RPM is fine on paper and your bank account isn’t.

The dispatcher who earns month two is the one who sat through the week-three review. That’s the actual test. Everything before it is setup.

Most operators think month one is the dispatcher’s job. It’s yours.

The first 30 days are a feedback loop. You give the dispatcher inputs. They give you booked loads. You compare what got booked against what should have. Then you correct.

Skip that loop and you’re locked into whatever booking pattern they default to. By day 60, that pattern is the relationship. Renegotiating it then costs you a month of revenue or a switch.

Week 1 isn’t paperwork. It’s a boundary test.

A real dispatcher asks for a tight list in week one. W-9, MC and DOT certificate, certificate of insurance with the dispatcher properly listed as certificate holder, factoring company NOA, and equipment specs (length, weight rating, lift gate, reefer cycle, anything that changes what they can quote).

That’s it. That’s the week-one list.

What the dispatcher should not be asking for in week 1

• Banking access beyond the factoring routing already on file.
• A signed limited POA before the fee terms and termination clause are clear in writing.
• Authority to set up new broker packets in your name without a per-broker confirmation rule.
• Permission to reassign your factoring NOA to a different factor.

The FMCSA is direct on this: a limited POA tied to dispatch authority should be scoped, time-bound, and revocable. FMCSA guidance on motor carrier authority treats your operating authority as yours, not assignable to a third party. If a dispatcher pushes for broad POA in week one, that’s the conversation, not a signature.

Lane prefs in week 1 are not a wishlist. They’re the contract.

Before the first load gets booked, you owe the dispatcher five inputs. Lane preferences. Home-time windows. Equipment limits. Brokers you won’t touch. Brokers you trust.

If the dispatcher tries to book before that conversation happens, push back. A booked load against unstated preferences is a load you’ll fight about Friday. Better to lose two days of revenue than to start the relationship with a load you didn’t want.

Write the prefs down. Email them. That document is your reference when week three goes sideways.

Most of week 1 is calibration that won’t happen on its own → talk to a dispatcher who runs the day-30 review with you.

Week 2: the first underpriced load is a test, not an accident.

It will come. Sometimes the lane is genuinely soft and they’re keeping wheels turning. Sometimes it’s a quiet check on what you’ll accept. You can’t tell which without asking.

A real rate confirmation has the broker’s MC, the all-in rate, accessorial terms (detention rate, layover, TONU), the commodity, the appointment windows, and the lumper policy. If any of that is vague, the rate confirmation is vague. Don’t dispatch on it.

When the underpriced offer lands, ask one question. “What’s the lane average this week and where is this offer relative to it?” If the dispatcher can answer with a DAT or Truckstop number, you’re working with someone who tracks the market. If the answer is “it’s what’s available,” that’s a flag, not an answer.

If the percentage you’re paying feels high before the reload pattern is established, that’s a fee-structure conversation, not a fire-the-dispatcher conversation. Some services bill flat. Some bill per load. Some bill percentage. Each pushes the dispatcher to book differently. How dispatch fees actually work walks through where the numbers shake out by structure.

By end of week 2, reload should be booked before delivery. Most loads.

This is the metric that separates a dispatcher who’s working your truck from one who’s reacting to it. By the second week, the booking rhythm should be: load picks up, dispatcher quotes the next reload from the delivery market, reload is confirmed before you back into the dock.

If you’re sitting two days every reset waiting on a reload, that’s not a market problem. That’s a workflow problem. Bring it up. The conversation is short: “What’s the booking lead time you’re targeting on my reloads?” If there’s no answer, there’s no system.

Week 3: the P&L review most operators skip – and pay for.

End of week three, you sit with the dispatcher and walk five numbers. Gross revenue. Deadhead percentage. Average loaded rate per mile. Detention claimed (and collected). Total dispatched miles vs paid miles.

Hold those against the ATRI 2025 marginal cost benchmark of $2.27 per mile. If your loaded RPM is under that and your deadhead is over 15 percent, you’re losing money on miles the dispatcher booked. That’s the data that changes the next four weeks.

If the dispatcher won’t sit through that review, that’s a signal. Not a small one. The dispatcher who avoids weekly P&L is the dispatcher whose booking pattern won’t survive a real audit.

Week 4 is the renegotiation point, not the settling-in point.

By day 30 you have data. Real lanes booked. Real RPM. Real deadhead. Real detention numbers. That’s the leverage to recalibrate.

Use it. Adjust the rate floor based on what the lanes actually paid. Drop brokers that produced detention you didn’t get paid for. Tighten the lane preferences based on what reloaded fastest. The dispatcher who’s worth keeping welcomes that conversation. The one who isn’t will tell you “let’s give it another month.”

Self-dispatch habits sabotage month one in predictable ways: micromanaging every offer, accepting loads to “help out,” skipping the P&L review, treating the dispatcher like an assistant instead of a partner. We cover the full habit list in a separate piece. For now, watch for those four.

Red flags that show up by day 30 (and what they mean)

• Vague rate confirmations. Missing accessorials means you eat detention.
• “Trust me on this load.” Trust is the P&L review, not a phrase.
• No weekly P&L review offered. The dispatcher doesn’t want the data on the table.
• Factoring delays past 48 hours. Either the broker packet is wrong or no one’s chasing it.
• Detention not claimed. That’s revenue on the floor, every week.
• Reloads booked after delivery, not before. No system, just reaction.

Quick decision rule: when to push back in week 1

• If they ask for broad POA before fee terms are signed → push back.
• If they book before the lane-prefs conversation → push back.
• If the first rate con is missing accessorials → don’t dispatch.
• If the factoring NOA is being routed to a new factor → stop and ask why.
• If week 2 ends without a reload-lead-time answer → put it in writing.

The dispatcher who survives month one is the one who sat through the review.

Month one isn’t about being nice. It’s about building the operating rhythm you’ll run for the next year. The dispatcher who pushes back on bad loads, sits for the weekly P&L, and books reloads ahead of delivery is the one who earns month two.

The one who avoids the review and tells you to be patient is the one whose booking pattern won’t get better. That’s the gap we built Logity dispatch operations around. Calibration in week one. Reload rhythm by week two. P&L on the table by week three. Renegotiation, not drift, by day 30.