Every dispute inside a small fleet has the same anatomy. A driver idles the truck all night in July, fuels his personal cooler on the company card, or takes the tractor home for a weekend without asking — and when you push back, the answer is some version of nobody ever told me. He might even be right. In a fleet with no written rules, every expectation lives in your head, every enforcement looks personal, and every firing turns into a he-said-she-said with your name on the losing side of it.
The fix is not a fifty-page handbook nobody reads. It is one page — the ten or so rules that actually cause your disputes, written plainly, signed by every driver, and enforced the same way every time. Here is how to build the one-page rulebook, what belongs on it, and how to roll it out without a mutiny.
Why One Page Beats a Handbook
Big-fleet handbooks exist to protect legal departments; your rulebook exists to prevent arguments. Those are different documents. A page that a driver actually read, understood, and signed settles disputes before they start — the conversation becomes look at line six, not a debate about what is fair. It also protects the driver, which is the part owners forget to say out loud: written rules mean no surprise standards, no rules invented mid-argument, and no favoritism between the driver you fish with and the one you hired last month. Fairness you can point to is what keeps good drivers, and as we covered in the driver scorecard system, drivers do not leave accountability — they leave arbitrariness.
What Goes on the Page: The Ten Dispute-Makers
Write rules only for the things that actually generate conflict and cost. For most small fleets that list is: fuel card use and what it never buys; idle policy with the specific hour targets your fuel budget needs; personal use of the truck and where it parks on home time; accident and breakdown protocol, including who gets called in what order; phone use in the cab; passenger and pet policy; equipment damage reporting deadlines; paperwork deadlines, meaning BOLs and receipts submitted before settlement; communication expectations, like answering dispatch within a set window during duty hours; and what triggers immediate termination — the short list you will actually enforce. Each rule is one or two sentences, and each names its consequence. A rule without a consequence is a suggestion, and drivers can smell the difference in a day.
Write Consequences You Will Actually Enforce
The fastest way to kill a rulebook is to print a consequence you will not deliver. If line four says any unreported damage is termination and your best driver dents a fairing and says nothing, you will not fire him — and the day you don’t, the whole page becomes decoration. So write graduated consequences that match reality: first instance is a documented conversation, second is a written warning, third hits the wallet or the job. Reserve immediate termination for the true non-negotiables — the safety and integrity lines you would genuinely enforce against your best driver on his best week. And when a termination does come, the signed page plus the documented steps is exactly the file that makes it clean; pair it with the clean-break protocol so the exit costs you neither the truck nor a lawsuit.
Roll It Out Without a Mutiny
Springing rules on veteran drivers feels like an accusation, so frame the rollout around what it gives them: predictability, fairness, and protection from the next guy’s mistakes becoming their problem. Walk through it in person or on a call — never by text blast — invite pushback, and actually take one or two pieces of it, because a rule a driver helped shape is a rule he polices himself. Every signature gets a copy; yours goes in each driver’s file next to their qualification paperwork. New hires sign it during onboarding before the first dispatch, which slots directly into the first-week lock-in — expectations set on day one are culture; expectations set after a violation are punishment. Then re-sign the page once a year, updated with whatever the year taught you.
Bottom Line
Unwritten rules cost you twice — once in the behavior they fail to prevent, and again in the argument about whether the rule existed. One page fixes both: the ten rules that cause your actual disputes, each with a consequence you will actually enforce, signed by every driver and applied without favorites. It is an evening of writing and a twenty-minute meeting, and it buys you something owners chronically underrate: the ability to run your fleet off a document instead of a debate.
Questions Carriers Ask
Do I really need written rules with only two drivers?
Two drivers is exactly when to write them, because whatever you tolerate now becomes the culture you scale. It is far easier to hand driver number five a page that four people already signed than to impose rules retroactively on a crew that grew up without any.
What’s the most important rule to include?
The reporting deadlines — damage, incidents, and tickets reported same-day, no penalty for the honest report, real consequences for concealment. Most fleet disasters are small problems that someone sat on. A page that makes reporting safe and hiding expensive prevents more losses than any other single line.
A veteran driver refuses to sign. Now what?
Have the direct conversation: which line is the problem? Sometimes it is a legitimate objection you should hear, and amending one rule buys buy-in from everyone. But if the objection is to being accountable at all, that is not a signature problem — the page just surfaced, in writing, the conflict you were eventually going to have anyway, on a day of his choosing instead of yours.
Innovative Logistics Group
