How to Choose a Trucking Business Consultant: The Job, the Proof, the Paper

How to verify operating experience

“Industry experience” on a website costs nothing to write. Operating experience shows up in specifics, and a short conversation exposes the difference. A consultant who says they ran a fleet should be able to name the company and the authority it ran under — carrier registration information is public, and FMCSA publishes carrier contact details under the government’s open-data policy.

Then ask questions only an operator answers easily. Walk through a real owner-operator settlement statement, line by line — fuel, chargebacks, escrow. Under the federal truth-in-leasing rule, 49 CFR 376.12, a lease must clearly state the compensation, must let the owner-operator examine the documents from which rates and charges are computed, and must specify every charge-back item together with how its amount is computed; someone who has paid settlements every week knows where those lines come from and where disputes start. Ask how they would find detention earned at the dock that never reached an invoice, or how they judge a lane once deadhead is counted. Ask what records a broker has to keep: 49 CFR 371.3 requires a broker to keep a record of each brokered transaction for three years and gives each party to the transaction the right to review it.

Good answers are specific and a little impatient. Weak answers move quickly to frameworks, dashboards and “best practices” without touching a single document the fleet actually produces.

Eight questions to ask a trucking consultant before signing

These are the questions we would want any fleet owner to put to any consultant — including us. They are not trick questions; a serious consultant should be glad to answer them.

• “What will you read first?” A good answer names records: the TMS or dispatch board, ELD data, settlement and factoring statements, the accounting file, the recruiting log. A weak answer is a round of interviews and a workshop.
• “Show me a sample of what I receive.” One page, in the real format, with the record each finding came from.
• “Who does the work after the signature?” A name, not “the right team.”
• “What do I own when we stop?” Everything — usable with the fleet’s own team or another firm.
• “How is the scope fixed, and what happens when you find something outside it?” It gets noted in the report, not billed midstream.
• “What happens if you find nothing worth fixing?” A written readout that says so, and the fee does not change.
• “What will you refuse to do?” Boundaries such as no promised safety score, no reselling software, no driver recruiting from the client.
• “Who is this not for?” A specific answer, given quickly, from someone who has turned work away before.

Confidentiality and drivers: the clause that matters most

A trucking consultant sees the most sensitive things a fleet has: driver names and pay, owner-operator lease terms, customer rates, lanes, broker relationships. A consultant who also runs a fleet, or a recruiting operation, has an obvious conflict — the same people the fleet works hard to keep are the people the consultant’s own trucks need. That conflict is manageable, but only on paper.

Before anyone opens a record, the fleet should hold a signed NDA, a written promise not to recruit or solicit its drivers and owner-operators, and a written promise that its data will not be used for anything except the engagement. If the consultant has its own carrier, add one more line: client data never touches the consultant’s fleet. And the customer list and rates stay out of any “benchmark” the consultant sells to the next client.

We run our own trucking company, so these lines apply to us first. We never recruit a client’s drivers or owner-operators, a client’s data never touches our own fleet, and everything runs under an NDA signed before anyone opens a record.

Read-only access, and what a consultant never needs

A consultant who is reading the business does not need to be able to change it. Read-only logins or exports are enough for a TMS, an ELD portal, a factoring portal or an accounting file, and nobody outside the fleet needs access to a bank account or the ability to book, cancel or pay anything.

Some records should stay out of reach entirely. A diagnosis can work from aggregates and de-identified exports — counts, dates, statuses — rather than the contents of driver qualification files or motor vehicle records. Drug and alcohol testing records are the clearest case: under 49 CFR 382.405 an employer releases them only as that rule allows, which for an outside party means the driver’s specific written consent naming the recipient. A consultant asking for them to “get the full picture” is asking for something the question does not need.

• Read-only accounts or exports, named system by system
• Driver data as aggregates or de-identified exports
• No qualification-file contents, motor vehicle records or testing records
• Where the data is stored, who sees it, and the date it is deleted
• Every login removed on the last day of the engagement

Written scope: the page that settles disputes before they start

An argument about talent is hard to settle. An argument about what was supposed to be delivered is easy to prevent: a one-page scope, signed before work starts, makes it impossible to have.

Illustrative example: a fleet hires a consultant to “look at dispatch.” Six weeks later the fleet expected a load-profitability tool and the consultant delivered a slide deck of observations. Both sides acted in good faith; neither wrote down what “look at” meant. A scope naming what would be delivered, the acceptance test and the price would have turned a disagreement into a checklist.

• The task, the scope, and what is explicitly out
• Every document or tool delivered, by name, and how it will be accepted
• The timeline and the full price, with the payment schedule
• Anything paid to third parties — ad budgets, software licenses — shown apart from the consultant’s fee
• What stopping early costs, and what the fleet keeps if it does

When not to hire one — and where we fit

Hire no one if the problem fits in one sentence and has an obvious owner: a POD that waits for days because “delivered → invoiced” belongs to nobody needs a name and a fixed time of day, not a study. Hire a dispatch service if the job is booking loads, a factor if the job is cash on delivered invoices, and a compliance service if the job is keeping files current. A consultant earns a fee only when the question is where the company loses money and what to change first.

Our first engagement is The Revenue Review: two weeks of read-only access to the fleet’s own records, and a written report the fleet keeps — where drivers, loads and money stall, with a monthly dollar figure wherever the records support one, and a 90-day plan. It files nothing with FMCSA, dispatches no loads and buys no invoices. The team behind it has run its own trucking company for seven years on an owner-operator model, with Amazon Relay as the main freight for five of them; we have no published trucking client yet. It is not built for owner-operators or fleets under about 20 power units, and the free 20-minute call says so when the arithmetic does not fit. The free Revenue Self-Audit on this page takes two taps and comes first.