A driver finishes a run, dispatch reports a crash, or a new CDL hire is ready to start Monday. Each event creates the same operational question: when must drivers be tested under DOT rules? The answer is not “whenever the company thinks it is safest.” DOT testing has defined triggers, timing rules, and recordkeeping requirements. Missing one can create the same exposure as never having a program at all.
For transportation employers, the job is to identify the trigger quickly, act within the applicable time window, and document what happened. You do not need another intermediary to tell you a random selection occurred. You do need a process that proves your driver pool, selection, notification, collection status, and result records can hold up when DOT asks.
The six DOT testing situations employers must manage
For CDL drivers in safety-sensitive positions, DOT drug and alcohol testing generally falls into six categories: pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up testing. Each serves a different purpose. They cannot be substituted for one another.
A company policy may call for additional testing, such as after a company vehicle incident that does not meet the federal post-accident threshold. That is a separate policy decision. Do not label it as a DOT test unless it actually meets the DOT rule for that test type.
Pre-employment testing: before safety-sensitive work begins
A driver must receive a negative DOT drug test result before performing any DOT safety-sensitive function for your company. For most fleets, that means before the driver operates a commercial motor vehicle requiring a CDL.
The practical point is simple: a completed collection is not clearance. The driver cannot begin safety-sensitive work until the employer has received a verified negative result from the Medical Review Officer. A pending result, an unopened electronic notice, or a promise from the clinic does not satisfy the requirement.
Pre-employment alcohol testing is not required by DOT, though an employer may have a company policy requiring it. If you conduct it as a DOT alcohol test, use the proper DOT process and documentation.
There are limited exceptions when a driver moves between DOT-regulated employers without a lengthy break in safety-sensitive service, but those exceptions depend on verified prior testing history and timing. Treat exceptions carefully. For a new employer, a documented negative pre-employment drug test is usually the cleanest path.
Random testing: throughout the year, not at year-end
Random testing is the test type most likely to fail under spreadsheet administration. DOT requires selections to be scientifically valid, unpredictable, and spread reasonably throughout the calendar year. Selecting all required drivers in December because the annual quota is short is not a defensible random program.
Your eligible pool must include every covered driver who is subject to random testing, including part-time, seasonal, and leased drivers performing safety-sensitive work for your operation. A driver on extended leave or otherwise removed from safety-sensitive duty may be excluded only when the exclusion is supportable and consistently applied.
The selected driver must have an equal chance of selection each time a draw occurs. A driver selected in January can be selected again in February. Removing selected names from future draws makes the process less random, not more fair.
Federal agencies publish minimum annual random testing rates, and those rates can change. Build your schedule around the rate that applies to your operating authority and the current calendar year. Then preserve the evidence: the eligible-pool snapshot at the moment of the pull, the random selection method, the date and time, who was selected, and the notification record.
That evidence matters because an auditor is not only checking whether you tested enough people. They may ask who was eligible on the day of the selection and whether the selection process could have been manipulated after the fact.
When must drivers be tested after an accident?
Post-accident testing is where employers often over-test, under-test, or lose the deadline while deciding what happened. For FMCSA-regulated CDL operations, a DOT post-accident test is required when the accident involves a commercial motor vehicle and one of the following conditions applies:
- The accident involved a human fatality.
- A person received immediate medical treatment away from the scene and the CMV driver received a citation within eight hours.
- One or more vehicles had disabling damage requiring a tow from the scene and the CMV driver received a citation within eight hours.
A fatal accident triggers testing of the surviving driver even if the driver does not receive a citation. In injury and tow-away situations, the citation is part of the trigger. An accident report, property damage, an insurance claim, or a supervisor’s concern by itself does not automatically create a federal post-accident testing requirement.
If testing is required, conduct alcohol testing as soon as practicable and within eight hours of the accident. Conduct drug testing as soon as practicable and within 32 hours. If you cannot complete the alcohol test within two hours, document why. If it is not completed within eight hours, stop attempts and document why. For drug testing, stop attempts after 32 hours and document the reason it was not completed.
Do not delay solely because the driver is at a hospital, police are investigating, or the vehicle is being towed. Those facts may affect what is practicable, but they do not erase the need to act. A law enforcement test can sometimes satisfy the requirement if it meets applicable conditions and documentation is available. Do not assume a police-administered test counts without verifying the details.
Reasonable suspicion requires trained judgment
A supervisor may require reasonable-suspicion testing when there are specific, contemporaneous, articulable observations concerning a driver’s appearance, behavior, speech, or body odors. A vague feeling that someone “seems off” is not enough.
For alcohol testing, the observations must be made by a supervisor or company official trained in reasonable-suspicion alcohol indicators. The alcohol test must occur within eight hours of the observation, with written documentation if it cannot occur within two hours. Drug reasonable-suspicion testing also requires a trained observer and should be conducted as soon as practicable.
This is not a discipline shortcut and not a replacement for random testing. Write down the objective facts: unsteady movement, slurred speech, odor, unusual conduct, or other observed behavior. Record the date, time, location, observer, and action taken. Keep opinions out of the initial observation record.
Return-to-duty and follow-up tests are not optional
When a driver has a DOT drug or alcohol violation, the driver cannot return to safety-sensitive work based on a manager’s decision, a negative independent test, or completion of an employee assistance program alone. The driver must complete the required Substance Abuse Professional process and receive a negative return-to-duty test before resuming safety-sensitive duties.
The follow-up testing plan comes from the SAP, not the employer. It includes a minimum of six unannounced follow-up tests during the first 12 months after the driver returns to duty, and the SAP may require testing for up to 60 months. These tests are in addition to your normal random-testing program. A follow-up test does not replace a random selection, and a random selection does not satisfy a scheduled follow-up test.
Build a record trail before the test result arrives
Compliance is not just the collection event. Your records should show what triggered the test, when the decision was made, who notified the driver, when the collection was completed, and what result or status followed. For random testing, retain the locked roster and draw record. For post-accident and reasonable-suspicion cases, retain the supporting facts and any explanation for missed timing targets.
Avoid backfilling this information after the result comes in. A clean-looking spreadsheet created after a failed test is not the same as a timestamped record made during the event. Auditors can spot gaps, altered dates, and unexplained changes in the driver pool.
DTSMS Online is built around that operational reality: you run the pull, retain the eligible-pool snapshot, issue notifications, and keep a status history without paying someone else to manage routine random-selection administration.
The useful closing question is not whether your fleet has a testing policy in a binder. It is whether, when a driver is hired, selected, involved in a qualifying crash, or observed showing signs of impairment, your team can identify the trigger and produce the record before the deadline closes.
