Driver Fatigue Risk Management Log

This template documents driver fatigue assessments, the controls applied, and any fatigue-related events in a single log. It is designed for fleets and operations that need a repeatable record of fit-for-duty checks and corrective follow-up. The output supports day-to-day supervision as well as annual program review.

A supervisor, dispatcher, safety manager, or other designated competent person should complete or verify the log. In some operations, the driver may self-report fatigue indicators and the supervisor records the decision and controls. The key is that the person signing off can make or escalate a fit-for-duty determination.

Use it at the start of shift, after extended driving, before a return trip, and any time fatigue is reported or observed. It also fits post-incident reviews and periodic audits of fatigue management practices. The cadence should match your routes, hours-of-service exposure, and operational risk.

No. This log complements hours-of-service tracking by capturing the human and operational signs of fatigue that time logs alone do not show. It helps document why a driver was held, reassigned, rested, or coached even when legal driving limits were not obviously exceeded. Many teams use it alongside dispatch records and telematics.

It supports fatigue management expectations under OSHA-style safety programs, transportation safety policies, and internal fit-for-duty procedures. It can also help demonstrate due diligence in audits that review supervision, hazard recognition, and corrective action tracking. If your organization follows a formal safety management system, this log provides evidence of routine control and follow-up.

The biggest mistake is treating fatigue as a checkbox instead of recording observable indicators and the actual control used. Another common issue is failing to document who was notified, what changed in the schedule, and whether follow-up was completed. Logs that omit the final fit-for-duty decision are much less useful in an audit or incident review.

Yes. You can add fields for long-haul, local delivery, night shift, seasonal peak periods, or specific fatigue triggers such as split shifts and weather delays. Many teams also add vehicle type, route length, or telematics references so the record matches their dispatch process. Keep the core assessment and corrective-action fields intact.

An ad hoc note usually captures only the immediate concern, while this template creates a consistent record of assessment, mitigation, reporting, and follow-up. That consistency makes it easier to spot repeat fatigue patterns and prove that the issue was addressed. It also reduces the chance that a critical event is handled verbally and then forgotten.

Assign a corrective action, name an owner, set a due date, and verify completion. Depending on the event, that may include schedule changes, coaching, route redesign, or a review of rest-break practices. The follow-up section is important because it closes the loop between the event and the prevention plan.