Why policy documents fail
The typical fleet policy is eleven pages, written years ago, signed by nobody, and referenced by no one. It fails for a reason that has nothing to do with intent: it was written to satisfy an insurer, not to guide a decision at six in the morning.
General Orders is a format borrowed from organizations that cannot afford ambiguity. Short numbered orders, one subject each, issued to everyone, acknowledged in writing, and revised on a fixed schedule.
- One subject per order, one page or less.
- Numbered and dated, so a revision is visible rather than silent.
- Written in the imperative: what a person does, not what the company believes.
- Acknowledged by every person it binds, with a date.
What belongs in the first five orders
Almost every fleet-heavy service company needs the same five subjects before anything else: vehicle use and assignment, pre-trip inspection, load and equipment security, hours and fitness for duty, and incident reporting in the first hour.
Note that four of the five are behavioral. They tell a person what to do at a specific moment. They are not statements of value, and that is why they can be enforced.
Re-issue on a schedule, not on an incident
A standard revised only after an incident reads, in hindsight, as a company that knew and did not act until it was forced. Re-issue on a calendar: annually at minimum, and whenever the work, the equipment or the customer base changes.
Each re-issue produces a new dated version and a fresh acknowledgment. That trail is the single most persuasive artifact a company can hand an underwriter, because it shows a standard that is alive rather than archived.
The test
Hand the order to a crew member and ask them to restate it. If they cannot, the order failed and the field is not at fault. Rewrite it until a person who has never read it can repeat the requirement back to you in one sentence.
This article describes a mechanism, not a legal position. Nothing in it is legal advice.
