Driver Fatigue Self-Assessment Form

Use it for any driver who may operate a vehicle after a shift start, especially commercial, delivery, shuttle, or field-service drivers. It is designed for the person actually reporting for duty to complete before driving begins. A supervisor or dispatcher can review the result, but the driver should be the one answering the fatigue questions. If your operation has a separate medical clearance process, this form should support it rather than replace it.

Complete it before each shift or each driving assignment where fatigue risk matters. It is most useful as a pre-trip or pre-dispatch check, not as an annual policy document. If a driver changes routes, has a long break, or returns after an interruption that could affect alertness, a new submission is a good practice. The goal is to capture the driver's condition at the moment they are about to operate.

The form should capture the reason, the explanation, and whether dispatch was notified so the next step is clear. In practice, that usually means the driver is removed from the assignment, a supervisor reviews the situation, and an alternate plan is made. The form should not force the driver to over-explain medical details. Keep the follow-up focused on operational safety and fit-for-duty decisions.

It can, so the template should be configured with data minimization in mind. Only ask for the sleep, alertness, medication, and impairment details needed to make a fit-for-duty decision. If your organization stores the responses, make sure access is limited and the submission includes a clear consent or disclosure line. Avoid collecting unrelated medical history or diagnosis details.

The biggest mistake is making every field required, which can block honest reporting and create bad data. Another common issue is using free-text fields where a date picker, numeric input, or multi-select would be more accurate. Teams also forget the go/no-go follow-up step, so a no-go response sits unanswered. Finally, if medication questions are included, the form should explain why the information is being collected.

Yes, and it should be. Use route_or_assignment to tailor the context, and add conditional logic if certain routes, vehicle classes, or shift lengths need extra screening. For example, long-haul, overnight, or passenger-carrying assignments may need more detailed fatigue prompts than local daytime routes. Keep the form short for low-risk assignments and expand only when the risk justifies it.

An ad-hoc check-in is easy to miss, hard to audit, and often inconsistent from one dispatcher to another. This template standardizes the same questions every time, creates a clear record of the decision, and makes follow-up easier when a driver is not fit for duty. It also supports accessibility and clearer validation than a freeform message. If you need a defensible process, a structured form is much stronger than a casual conversation.

Common integrations include dispatch systems, HR records, incident logs, and audit trail storage. A no-go submission can trigger a notification to dispatch or a supervisor, while a go submission can be logged as part of the shift record. If your workflow supports conditional logic, you can route only higher-risk responses for review. Keep the integration limited to what you actually use so you do not spread PII unnecessarily.