Fleet Safety Policy: The Complete Guide to the 7 Sections (2026)

A fleet safety policy is the document that turns an organisation’s duty of care for people on the road into rules a driver, a scheduler and a manager can each be held to — and under ISO 39001:2012 it is also the road traffic safety (RTS) policy clause 5.2 requires top management to establish, so it has to do two jobs at once. The management system job is to state commitments, provide the framework for the objectives in clause 6.4 and be communicated and available; the operational job is to say, in plain language, who may drive what, how vehicles are kept, how journeys are planned, what happens when a driver is tired, distracted or over a limit, and what the organisation does after a crash. Most fleet safety policies do the second job and forget the first, or do the first in language nobody in a cab will read. This guide sets out what ISO 39001 requires of the policy, the seven sections a working fleet safety policy contains, the rules that belong in each, how far it reaches — grey fleet, contractors and visitors included — how it is communicated and evidenced, and the five faults that make a policy fail an audit or a court.

What ISO 39001 requires of the fleet safety policy

Our guide to ISO 39001 covers the standard the policy sits in; the sections below are the operational half.

The seven sections of a fleet safety policy

How far the fleet safety policy reaches

1. Grey fleet. Staff driving their own cars for work generate the same duty of care and usually none of the controls. The policy sets licence, insurance and roadworthiness checks, journey limits and the same fitness rules, and says how mileage claims are conditional on them.
2. Contractors and subcontracted transport. ISO 39001 asks for the factors the organisation can influence through others; the policy flows the relevant rules into contracts — hours, vehicle standards, incident reporting — and monitors them.
3. Visitors and site traffic. Deliveries to and from sites, reversing, pedestrian separation and speed on site are in scope where the organisation controls the site.
4. Commuting. Usually outside scope, but in it where the organisation sets the conditions — shift end times that put tired workers on the road, or accommodation decisions on remote sites. ISO/TC 241’s work on commuting safety (ISO/AWI 39002) is the signal that the boundary is moving.

Our guide to the journey risk assessment covers section 4; our guide to driver fatigue covers the fitness rules in section 5.

Communicating and evidencing the fleet safety policy

Five fleet safety policy faults

• Two documents, no link. A board-level RTS policy for the auditor and a driver handbook nobody reconciled; objectives trace to neither.
• Grey fleet absent. The largest exposure in many organisations, outside the policy entirely.
• Rules with no owner and no consequence. A phone rule everyone knows is not enforced.
• Not communicated. Drivers cannot say what the policy requires of them; no acknowledgements on file.
• Never reviewed. Dated at implementation; the telematics, the new vehicle class and the serious crash since are absent.

Frequently asked questions

Is a fleet safety policy the same as the ISO 39001 RTS policy?
It can and should be the same document. Clause 5.2 requires top management to establish an RTS policy with commitments, a framework for objectives and communication; a fleet safety policy that carries those elements and the operational rules satisfies the clause and is the document drivers actually read.

How long should it be?
Short enough to be read: a two- to four-page policy with the commitments and the rules by section, supported by procedures — journey management, fatigue, vehicle checks, incident investigation — that carry the detail.

Does it apply to staff who drive their own cars?
Yes, wherever they drive for work. Grey-fleet drivers are in scope of the duty of care and of ISO 39001 where the organisation influences their road use; the policy sets the checks and journey rules that apply to them.

What must drivers sign?
An acknowledgement that they have read and understood the policy and the rules that apply to them, renewed when the policy changes. It is the communication evidence clause 5.2 and 7.4 expect.

How often should it be reviewed?
Annually as part of management review, and after significant change — new vehicle types, new operations, new technology — or a serious incident.

Where this leaves you

Write one fleet safety policy that does both jobs: top management’s commitments and the framework for objectives in the first section, the rules for drivers, vehicles, journeys, fitness and incidents in the middle, and roles, communication and review at the end. Reach it into grey fleet and contractors, get it signed and briefed, enforce it consistently, and review it with the data — because a policy is evidence of a managed fleet only when the people on the road can say what it requires of them.

References

• ISO 39001:2012 — Road traffic safety (RTS) management systems — Requirements with guidance for use — Clause 5.2 and the harmonized policy requirements; Amd 1:2024.
• Regulation (EC) No 561/2006 — consolidated text — The EU driving-time and rest floor the fitness section sits above.

More on ISO 39001

• Fleet safety policy — you are here
• ISO 39001 explained
• Driver fatigue management
• Journey risk assessment
• Road traffic safety objectives: clause 6.4
• ISO 39001 vs ISO 45001

The Fleet Safety (RTS) Policy with the seven sections drafted, the driver acknowledgement form, the journey management and fatigue procedures, the vehicle check and defect forms and the incident investigation form are in the ISO 39001 Road Traffic Safety Toolkit, or start with the free templates.