A random selection is not the compliance program. It is one documented event inside a system the employer must control from driver eligibility through final record retention. This DOT employer responsibilities guide is for fleet operators who want to run their own program without relying on spreadsheets, vague TPA updates, or paper files that cannot answer an auditor's first question: who was eligible on the day of the draw?
DOT rules allow employers to use service agents. They do not transfer the employer's responsibility to the service agent. If a driver was omitted from a pool, a notification cannot be proven, or a result record is incomplete, the employer owns the exposure.
What DOT Employers Must Own
For transportation employers, the designated employer representative is the control point. That person may not personally collect a specimen, operate the lab, or perform a medical review. But the employer must establish the process, apply it consistently, and keep records showing what happened.
Start with a current roster of safety-sensitive employees. For a CDL fleet regulated by FMCSA, that generally means drivers who must hold a commercial driver's license to perform their job, including certain part-time, seasonal, and leased drivers. A person should enter the random pool when they are performing, or are ready to perform, safety-sensitive functions. They should be removed when they are no longer eligible.
That sounds simple until operations get busy. New hires wait on onboarding paperwork. A driver moves to a non-driving role. Another goes on extended leave, returns from leave, or works intermittently. Those changes affect the eligible pool. A random draw is only defensible if the roster used for that draw reflects a defined, supportable point in time.
The employer must also maintain a written policy, provide required education and training, arrange testing through qualified providers, respond correctly to verified results, and retain records for the required periods. The details vary by DOT agency and testing event, so use the rules applicable to your operation rather than assuming every program follows the same schedule or retention rule.
DOT Employer Responsibilities Guide: The Random Program
Random testing must be scientifically valid, unpredictable, and spread reasonably throughout the calendar year. Selecting every driver at the same time each quarter may look organized, but it can undermine the element of chance that random testing requires. A compliant program also cannot allow employees to predict that they are safe from selection after a prior test.
Your annual testing rate is set by the applicable DOT agency and can change. For FMCSA employers, check the current annual random drug and alcohol testing rates before building the calendar and selection schedule. The rate is applied to the average number of covered employees, not simply the headcount on December 31.
A practical way to manage this is to review the pool each time you run a selection. Confirm additions, removals, leaves, and status changes first. Then lock the eligible-pool snapshot, run the selection using a documented random method, and preserve the selection output. Do not overwrite the roster later and expect it to prove who was eligible at the moment of selection.
A defensible random-selection record answers five basic questions:
- Which company and DOT-regulated pool was selected?
- Which employees were eligible when the draw occurred?
- What date and time was the draw run?
- What selection method or random-number process was used?
- Which employees were selected, notified, and ultimately tested?
The last question is where many self-managed programs break down. A list of selected names is not enough. You need a status trail showing notification, collection progress, result entry, cancellations where applicable, and follow-up action when something does not go as planned.
Notification Is an Operational Control
Once selected, a driver must proceed to testing promptly. The employer should have a defined notification process that works across shifts, terminals, and road assignments. Dispatch, supervisors, and backup contacts need to know who can notify a driver and what to do if the driver is unavailable.
Keep the notification record factual. Capture the date, time, notifying person, method, and driver response. If a driver is out of town, on leave, or cannot reasonably report immediately, document the circumstances and the action taken. Do not quietly substitute another driver because the first selection is inconvenient. Whether a replacement selection is appropriate depends on the reason the original test did not occur and the rules governing your situation.
This is also why email alone is not always enough. It may support the record, but it does not prove the driver received the instruction or was directed to proceed. The right workflow depends on your operation. A local day-cab fleet may use direct supervisor notification; an over-the-road fleet may need dispatch escalation and collection-site coordination.
Keep Testing Functions Separate and Qualified
Employers coordinate the program, but certain decisions belong to qualified parties. The collection site follows collection procedures. The laboratory performs analysis. A Medical Review Officer reviews and verifies drug-test results. A Substance Abuse Professional evaluates drivers after violations and prescribes the return-to-duty process.
Do not treat a lab report, a preliminary portal alert, or a supervisor's observation as a final verified drug-test result. Follow the required process and act only when the appropriate determination is made. For alcohol testing, know the required immediate actions tied to the result level. For drug and alcohol violations, remove the employee from safety-sensitive functions when required and provide the required information on SAP resources.
Employers also need a process for pre-employment testing, post-accident testing when criteria are met, reasonable-suspicion testing, return-to-duty testing, and follow-up testing. Random testing does not replace any of these obligations. Each event has its own trigger, documentation needs, and timing rules.
Records Must Hold Up When DOT Asks
An audit-ready file is not a folder full of PDFs. It is a traceable record that connects the driver, the testing reason, the date, the action taken, and the result. Records should be secure, access-controlled, and separated from ordinary personnel files where required.
For random testing, preserve the roster or locked snapshot used for the draw, the selection output, the randomization documentation, notification history, collection status, and result record. Keep an audit trail for changes. If someone corrects a driver status or enters a result, the system should show who made the change and when.
Write-once result records and timestamped status histories are not decoration. They reduce the risk that a later edit creates uncertainty about what the employer knew, when it knew it, and what action followed. That is the difference between saying a process occurred and being able to demonstrate it.
DTSMS Online is built around this employer-controlled workflow: upload the pool, run the pull, issue notifications, track status, and retain the documented chain. You run the pull. Nobody needs to sit between your roster and your compliance record.
Where Employers Create Avoidable Exposure
Manual spreadsheets can work for a very small, stable fleet, but they demand discipline that most busy operations cannot sustain indefinitely. A copied tab may not show the historical pool used for a prior selection. A formula can change. A name can be filtered out. An emailed list may not preserve the selection method or notification record.
Outsourcing can also be useful, especially for complex multi-state operations or employers that need collection-site networks and expert program support. The trade-off is control and visibility. A TPA can perform administrative work, but the fleet should still be able to retrieve its own pool history, selections, notices, results, and exception notes without waiting for a ticket response.
The same principle applies to pricing. If routine random selection is all you need, a service fee for every draw can become an unnecessary operating cost. If you need full-service coordination, that cost may be justified. Match the tool and service level to the work you actually need, not to a bundle built for someone else's fleet.
Build a Process People Can Repeat
Assign one primary program owner and one trained backup. Set a recurring roster review. Run selections on a schedule that supports unpredictability across the year. Make notification instructions available to supervisors and dispatch. Reconcile every selected driver until the event reaches a recorded outcome.
Then test your own records before an auditor does. Pick a completed random selection and ask your team to produce the eligible pool, selection method, notification proof, collection outcome, and final result history. If that takes hours, relies on one person's inbox, or produces conflicting versions, the process needs work.
Compliance becomes easier when routine tasks leave a clean trail behind them. Keep the pool current, keep the draw documented, and keep every status change tied to a date and a person. When DOT asks, your records should answer before anyone has to explain.
