DOT Post-Accident Drug and Alcohol Testing Checklist
Use this checklist to decide whether DOT post-accident drug and alcohol testing is required, document the timing, and record why testing was or was not done.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Trucking And Logistics · Passenger Transportation · Construction Fleet Operations · Municipal And Utility Fleets
Overview
This checklist is for deciding whether DOT post-accident drug and alcohol testing is required after a crash involving a safety-sensitive employee, and for documenting the actions taken when it is. It walks the reviewer through incident intake, DOT coverage, accident criteria, testing timing, collection details, and final closeout so the record shows both the facts and the rationale.
Use it immediately after a qualifying incident, especially when there is a fatality, injury, tow-away damage, or a citation tied to the accident. It is designed for supervisors, safety managers, HR, and compliance staff who need a consistent way to capture the decision and avoid missed deadlines or incomplete documentation. The checklist is also useful when testing is not required, because it records why the event did not meet the trigger.
Do not use this as a general accident investigation form or for non-DOT employees. It is not meant for routine vehicle damage, customer complaints, or internal discipline decisions unless the event also implicates DOT post-accident testing rules. If your operation has mixed fleets or mixed job roles, the checklist should be paired with a clear determination of whether the employee was performing a DOT-covered safety-sensitive function at the time of the incident.
Standards & compliance context
- This template supports DOT post-accident testing documentation for safety-sensitive transportation roles and helps preserve the audit trail expected in regulated fleet operations.
- The checklist aligns with the broader documentation expectations found in DOT drug and alcohol testing programs and related employer recordkeeping practices.
- If your operation also follows FMCSA, FAA, FTA, PHMSA, or FRA rules, use the checklist alongside the applicable agency testing procedures and employer policy.
- Where state law or collective bargaining rules add notification or documentation steps, those can be added without changing the core DOT trigger analysis.
- The form is not a substitute for the employer's designated testing policy, MRO process, or collection-site procedures, which should remain in force.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Incident Intake and Initial Notification
This section captures the first facts while they are still fresh and establishes the incident record that the testing decision will rely on.
- Accident date and time recorded
- Location of accident recorded
- Human Resources or designated compliance contact notified
- Supervisor documented immediate facts and witness statements
- Accident report or incident number assigned
-
Vehicle and driver identifiers captured
Include unit number, driver name or employee ID, and any trailer or load identifier as applicable.
DOT Coverage and Accident Criteria
This section determines whether the employee and the crash fall under DOT post-accident testing rules before any collection decision is made.
- Employee was performing a DOT-covered safety-sensitive function
- Commercial motor vehicle involved
- Accident involved a human fatality
- Driver received citation for moving traffic violation arising from the accident
-
Accident meets DOT injury or tow-away testing criteria
Document whether the accident resulted in injury requiring immediate medical treatment away from the scene or disabling damage requiring tow-away, as applicable to the DOT rule in use.
Testing Decision and Time Window
This section records whether drug testing, alcohol testing, or both are required and whether the required timing was met.
- Post-accident drug test required
- Post-accident alcohol test required
-
Drug test initiated within required DOT time window
Document the collection start time and compare it to the applicable DOT deadline.
-
Alcohol test initiated within required DOT time window
Document the collection start time and compare it to the applicable DOT deadline.
Collection and Chain of Custody
This section documents where and how testing occurred so the result can be traced back to a valid collection process.
- Collection site and collector identified
- Drug test specimen collected and chain of custody completed
- Alcohol test completed by qualified tester
- Any collection delay or inability to test documented
Decision Rationale and Closeout
This section closes the loop by explaining the decision, capturing sign-off, and assigning any follow-up actions.
- Testing decision documented with rationale
-
If testing was not required, reason recorded
Include the specific criterion that was not met, such as no DOT-covered function, no CMV involvement, or accident did not meet applicable testing thresholds.
- Supervisor or compliance reviewer signed off
- Corrective actions or follow-up assigned
How to use this template
- 1. Record the accident date, time, location, vehicle identifiers, driver name or ID, and any witness statements as soon as the incident is reported.
- 2. Confirm whether the employee was performing a DOT-covered safety-sensitive function and whether the vehicle and crash facts meet the post-accident trigger criteria.
- 3. Mark whether drug testing, alcohol testing, or both are required, then document the required time window and the actual initiation time for each test.
- 4. Capture the collection site, collector, chain-of-custody details, and any delay, inability to test, or missed window with a specific reason.
- 5. Complete the rationale section, note when testing was not required, and route the checklist to the supervisor or compliance reviewer for sign-off.
- 6. Assign any follow-up actions, such as retraining, carrier notification, or incident file review, and file the completed record with the accident report.
Best practices
- Document the accident facts before opinions or assumptions so the testing decision is based on observable criteria.
- Separate the drug test decision from the alcohol test decision, because the timing and documentation requirements are not identical.
- Record the exact time the supervisor learned of the accident and the exact time testing was initiated to show whether the window was met.
- Capture the reason for any delay, including unavailable collectors, medical transport, weather, or law enforcement control of the scene.
- Use the checklist only after confirming DOT coverage, because non-covered employees should not be routed through a DOT post-accident decision path.
- Keep witness statements factual and brief, and avoid mixing disciplinary conclusions into the testing record.
- Photograph or attach supporting incident records when available so the checklist can be reconciled with the accident report later.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What accidents does this checklist apply to?
This checklist is for incidents involving DOT-covered, safety-sensitive employees after a crash or accident. It helps you determine whether the event meets post-accident testing triggers such as a fatality, a citation tied to the accident, or injury/tow-away criteria. If the driver was not performing a DOT-covered function, the checklist helps document why testing was not required.
Who should complete the checklist after an accident?
A supervisor, safety manager, HR contact, or designated compliance reviewer should complete it as soon as practical after the incident. The person completing it should capture facts, identify the driver and vehicle, and make sure the testing decision is documented before the record is closed. A second reviewer is helpful when the trigger is unclear.
How quickly does testing need to start?
The checklist is built to capture the required DOT time window for both alcohol and drug testing. Alcohol testing is especially time-sensitive, so the form should be used immediately after the accident decision is made. If a delay occurs, the checklist should record the reason, who was notified, and what prevented timely collection.
What if the driver was cited but the accident seems minor?
A citation alone does not automatically mean testing is required unless the accident also meets the DOT post-accident criteria. The checklist walks the reviewer through the covered function, vehicle involvement, injury or tow-away conditions, and citation status so the decision is based on the full rule set. That reduces inconsistent decisions across supervisors.
Can this checklist be used for both drug and alcohol testing?
Yes. The template separates the decision and timing for drug testing and alcohol testing so you can document each requirement independently. That matters because one test may be required while the other is not, depending on the facts and timing of the incident.
What are the most common mistakes this template helps prevent?
Common mistakes include failing to document the exact accident time, not confirming whether the employee was in a safety-sensitive role, and missing the reason a test was not required. Another frequent issue is starting collection too late or not recording a delay. This checklist creates a defensible record of the decision path.
How does this checklist support compliance audits?
It creates a clear audit trail showing the incident facts, the testing trigger analysis, the collection steps, and the final sign-off. That makes it easier to answer questions from internal auditors, legal counsel, or a DOT compliance review. It also helps show that decisions were made consistently rather than ad hoc.
Can we customize this for our fleet or terminal operations?
Yes. You can add company-specific roles, dispatch contacts, terminal locations, incident report numbers, and escalation steps without changing the core decision logic. Many teams also add fields for vendor collection site details, after-hours contacts, and internal notification requirements.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Compare 11 frontline hiring platforms on mobile apply, automated screening, and onboarding handoffs to find the right fit for hourly and shift-based workforces.
-
Spring '26 brings AI Course Creation, Power BI-connected AI Agents, and smarter content governance to MangoApps. See what's new across the platform.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
Ready to use this template?
Get started with MangoApps and use DOT Post-Accident Drug and Alcohol Testing Checklist with your team — pricing built for small business.
