← All articles

How to Set Up a DOT Testing Roster That Holds Up

How to Set Up a DOT Testing Roster That Holds Up

A random selection is only as defensible as the pool it came from. If an auditor asks who was eligible on the day of a pull, a spreadsheet with overwritten rows and no history puts the burden back on you. When you set up a DOT testing roster, the job is not simply loading driver names. You are establishing the controlled eligible pool that supports every random drug and alcohol selection that follows.

For a small fleet, this may be 12 drivers. For a multi-terminal operation, it may be hundreds of safety-sensitive employees with different work statuses and testing requirements. The principle stays the same: include everyone who belongs, exclude only those who do not, and retain proof of what the pool looked like when you ran each selection.

Start With the Right DOT Testing Roster

Your roster should represent employees who perform DOT-covered, safety-sensitive functions under the regulations that apply to your operation. For many motor carriers, that means CDL drivers subject to FMCSA drug and alcohol testing rules. Passenger carriers, construction fleets, and companies with drivers who rotate between active and inactive assignments need to look closely at actual duties, not just job titles.

Do not build the pool from payroll labels alone. A person called a dispatcher may occasionally operate a covered commercial vehicle. A driver listed as part-time is still eligible if they perform a safety-sensitive function. Conversely, an office employee with a CDL who never performs covered driving duties generally does not belong in the DOT random pool merely because they hold a license.

Start with a written eligibility decision for each worker. Then make that decision visible in the roster fields you maintain.

| Roster field | Why it matters | | --- | --- | | Full legal name or unique employee ID | Prevents confusion between similarly named employees and supports matching to test records. | | DOT agency or program | Keeps employees in the right testing pool when more than one DOT agency applies. | | Safety-sensitive job status | Shows why the employee is eligible for random testing. | | Active, inactive, or removed status | Stops former or temporarily ineligible workers from being selected without deleting history. | | Effective date of each change | Establishes when a driver entered or left eligibility. | | Work location or company division | Helps manage legitimate sub-pools and notification workflows. |

A roster does not need unnecessary personal data to be useful. Avoid turning it into a general HR file. Keep only the identifiers and status information needed to administer the testing program, document eligibility, and connect the selection to the correct employee.

Decide Whether You Need One Pool or Separate Pools

One of the easiest ways to create audit exposure is to split drivers into convenient groups without a compliance reason. A separate pool may be appropriate when different DOT agency rules apply or when a legitimate, consistently administered testing program requires it. But creating a “day shift” pool and a “night shift” pool just because it makes notifications easier can distort the selection process if it is not handled correctly.

The practical question is whether every covered employee who should compete in the same random-selection process is being treated consistently. If your company has one FMCSA-regulated driver group, a single active pool is often the cleanest choice. If separate entities, DOT agencies, or testing programs are involved, document why pools are separate and keep their records separate.

For owner-operators, leased drivers, and workers shared between affiliated companies, responsibility can depend on the operating arrangement and who is acting as the employer for DOT testing purposes. Do not guess. Determine which employer carries the testing obligation before adding someone to a pool or assuming another company has done it.

Use Effective Dates Instead of Deleting People

Drivers are hired, placed on leave, return to duty, transfer, and separate from employment. Your roster has to reflect those changes without erasing the record that explains earlier selections.

When a driver becomes safety-sensitive, add the person promptly with an effective date. When a driver leaves the covered role, change the status to inactive or removed and record the date and reason. Do not delete the row just because the driver will not be in the next pull. That deleted row may be the only evidence that the person was properly included in a prior selection.

This distinction matters when reviewing an old test. If a driver was selected in March and terminated in April, an auditor should be able to see that the driver was active and eligible in the March pool. A current-only roster cannot prove that.

Temporary inactivity requires judgment. A driver on vacation, a short leave, or a temporary dispatch assignment may still be part of the random pool depending on the applicable rules and company circumstances. The key is to apply a documented rule consistently. Never remove a driver simply because selecting that person would be inconvenient.

Lock the Pool Before You Run the Pull

A defensible random program preserves a snapshot of the eligible roster at the moment of selection. This is where manual spreadsheets usually fail. Someone sorts a column, pastes in a new hire, removes a terminated driver, and the prior version disappears. Later, no one can reconstruct the pool population or show that the selected names were generated from the correct group.

Before running a pull, review the active count, recent hires, separations, and status changes. Then lock the eligible-pool snapshot. The record should show the selection date, the pool size, the identities or IDs of eligible employees, the required testing category, and the method used to generate selections.

Computer-generated random selection is not just a convenience feature. It removes the appearance that a manager chose names based on availability, performance, route assignment, or a prior testing history. Your records should identify the randomization method and retain the output. If the system assigns a run number or timestamp, keep it with the selection record.

DTSMS Online is built around this control point: the eligible pool is locked for each run, the selection method is documented, and later roster changes do not rewrite the historical pull. You run the pull. The record remains available when DOT asks how it was done.

Calculate Selections From the Correct Population

The annual random testing rate is set by the relevant DOT agency and can change. Your program must follow the rate in effect for your covered employees and test category. Drug and alcohol rates may differ, so do not assume a single percentage applies to both.

The operational mistake is treating the annual rate as a one-time annual draw. Random testing must be reasonably spread through the year, and each draw should be based on the applicable active population. A driver selected in one period can be selected again in the next. That is not a system error. Random does not mean everyone is selected once before anyone is selected twice.

Keep the math with the selection record: pool size, required annual rate, testing category, period covered, number selected, and any carryover logic your program uses. If the result is rounded, use a consistent documented approach. A safety director should be able to explain the count without reopening a calculator and reconstructing assumptions months later.

Notify, Track, and Close Each Selection

The random roster is only the beginning. A selection that never reaches collection, or a result that sits in an email inbox, leaves a broken compliance trail.

After a pull, record when the designated employer representative or supervisor was notified, when the employee was notified, and what happened next. The record should progress through clear statuses such as selected, notified, sent for collection, collected, pending result, and result entered. If a collection is delayed, cancelled, or refused, document the event and follow the applicable company and DOT procedures rather than quietly replacing the selected employee.

Protect confidentiality while doing this. Supervisors may need enough information to arrange immediate notification and remove a driver from duty when required, but broad access to testing details is unnecessary. Limit access by role, especially for result information and medical-review-related records.

A timestamped status history is more useful than a stack of emails because it answers the questions an auditor will ask: When was the employee selected? Who was notified? Was the collection completed? What record supports the final status? It also gives your team a current operational view instead of requiring dispatch, HR, and safety to compare separate files.

Review the Roster Before Every Cycle

A monthly or quarterly selection schedule only works if roster maintenance happens between pulls. Assign one accountable owner, usually the designated employer representative or safety manager, to receive hiring, transfer, leave, and termination updates. Dispatch and HR can supply the changes, but one person should verify the roster status before it affects a selection.

Use a short pre-pull check: confirm active driver count, review additions and removals since the last run, verify the correct pool and testing category, and make sure prior selections have reached a documented disposition. This is faster than repairing records after an audit notice arrives.

Control does not mean doing more paperwork. It means making the right record once, at the moment the work happens. Set up your DOT testing roster as a living eligibility record, preserve each selection snapshot, and let every status change leave a trail that holds up.