Key Takeaways
- A fatigue policy should tell drivers when to stop, who to call, and how dispatch will respond when a driver says they are not safe to continue.
- Hours-of-service compliance is not the same as fatigue management. A driver can be legal on paper and still unsafe to keep driving.
- Document fatigue reports, dispatch decisions, schedule changes, and follow-up coaching without punishing honest safety reporting.
Related documentation steps
Fleet safety records work best when policies, coaching, meeting notes, and accident reviews use the same filing and follow-up habits.
fleet safety documentation checklist · driver coaching policy · accident review board basics · FMCSA CSA score basics
What the policy should establish
A driver fatigue policy sets expectations for reporting fatigue, stopping safely, contacting dispatch, rescheduling deliveries, and documenting the decision. The policy should make clear that a driver who is unsafe to continue has a duty to stop.
The policy should also explain what dispatch does next. A driver who reports fatigue should not have to negotiate with several people while parked on a shoulder or at a truck stop.
HOS compliance is only the floor
Hours-of-service rules create a legal framework for duty time and rest, but they do not measure alertness. A driver can be within hours and still affected by poor sleep, illness, medication, heat, stress, or a difficult schedule.
A fatigue policy should treat HOS records as one input. Dispatch timing, route conditions, rest quality, and driver self-report all matter when deciding whether to continue a trip.
Fields to include in the template
Include fields for driver name, unit number, location, time of fatigue report, remaining hours, delivery appointment, dispatcher contacted, decision made, revised plan, and follow-up owner.
Add a place for the driver to describe the issue in plain language. A note such as 'unsafe to continue due to lack of sleep after shipper delay' is more useful than a checkbox alone.
| Field | Why it matters | Who completes it |
|---|---|---|
| Driver fatigue report time | Shows when the issue was raised | Driver or dispatcher |
| Location and safe parking status | Shows whether the driver stopped safely | Driver |
| Available HOS | Documents duty-time context | Dispatcher |
| Dispatch decision | Shows whether load plan changed | Dispatcher |
| Customer or broker notice | Records schedule impact communication | Operations |
| Follow-up review | Identifies patterns or planning issues | Safety contact |
A fatigue report should not be treated as discipline by default. Repeated patterns may require scheduling review, coaching, or medical referral through the appropriate process.
Dispatch response rules
The policy should tell dispatch what to do when a driver reports fatigue: identify safe parking, notify the customer or broker if needed, revise the delivery plan, and document the decision.
Avoid language that turns every fatigue report into discipline. Drivers are less likely to report honestly if they believe the report will be treated as a violation before the facts are reviewed.
How to handle repeated reports
Repeated fatigue reports on the same lane may point to detention, appointment timing, parking availability, or dispatch planning rather than a driver issue. Review patterns before assuming the cause.
Repeated reports from the same driver may require a private safety conversation, schedule adjustment, medical guidance, or a review of off-duty rest quality. Document the follow-up, but keep medical or personal details out of ordinary operations notes.
Records to keep with the policy
Keep fatigue reports with dispatch notes, HOS records, appointment changes, and any customer communication related to the delay. The file should show the safety decision and the operational impact together.
If the report leads to coaching, schedule adjustment, or medical referral, store that follow-up in the appropriate driver or safety file. Do not place private medical details in ordinary dispatch notes.
Step-by-step checklist
- Name the policy owner and review schedule.
- Describe the driver action expected in plain language.
- List records to keep after incidents or coaching sessions.
- Set an escalation path for urgent safety concerns.
- Review the policy with drivers before it is enforced.
Safety Boundary
General information only. This is not safety consulting, regulatory compliance advice, or a substitute for current official requirements and company policy.
Source Notes
- Motor Carrier Safety PlannerFMCSA · official · last checked 2026-06-08Supports: safety-management, driver-policy, documentation
General carrier safety management and recordkeeping reference.
- 49 CFR 395.8: Driver's Record of Duty StatuseCFR · official · last checked 2026-06-08Supports: eld-data, hours-of-service-records, incident-documentation
Supports general ELD and duty-status record context.
- 49 CFR 395.22: Motor Carrier Responsibilities for ELDseCFR · official · last checked 2026-06-08Supports: eld-data, motor-carrier-responsibilities, documentation
Used for general ELD responsibility context. It is not interpreted as compliance advice.
- Roadway SafetyNational Safety Council · industry · last checked 2026-06-08Supports: driver-safety, coaching, incident-prevention
Industry safety reference for driver coaching and incident prevention language.
For source notes and related resources, visit https://www.crashprooftruck.com