← All articles

How Long to Retain Test Records for DOT?

How Long to Retain Test Records for DOT?

A DOT audit rarely begins with a question about your random rate. It begins with a request for records: show the pool, show the selection, show the notice, show the result, and show when each step happened. If you are asking how long retain test records, the answer is not one simple number. It depends on the record type, the testing outcome, and the DOT agency rules that apply to your operation.

For most CDL fleets under FMCSA rules, a practical retention system must preserve records from both the DOT drug and alcohol testing procedures in 49 CFR Part 40 and the FMCSA controlled substances and alcohol use and testing rules in 49 CFR Part 382. When the rules set different retention periods for the same type of record, keep the record for the longer period.

How Long to Retain Test Records: The FMCSA Schedule

For FMCSA-regulated employers, the retention clock is generally based on the result or documentation category, not simply the date of the random selection. The following schedule covers the records fleet operators handle most often.

| Keep for | Records to retain | | --- | --- | | Five years | Alcohol test results of 0.02 or greater; verified positive controlled-substances results; refusals to test; Substance Abuse Professional evaluations; follow-up testing and follow-up testing schedules | | Three years | Random selection process records and dates of selections; annual Management Information System reports; employee education and supervisor training records; certain testing equipment documentation | | Two years | Collection-process records and documentation of collector training | | One year | Negative and canceled controlled-substances test results; alcohol test results below 0.02 |

That table is your operating baseline, not a reason to throw away documentation the moment a retention period ends. A pending claim, investigation, enforcement action, insurance dispute, or state requirement can justify holding records longer. Your company document-retention policy may also set longer periods. The key is to avoid keeping records indefinitely by accident while also avoiding premature deletion of records you may need to defend a DOT decision.

Five-year records: violations and return-to-duty files

Five-year records receive the most attention because they involve violations, refusals, and the return-to-duty process. Keep the verified positive result, alcohol result at or above 0.02, or refusal documentation together with the employer actions that followed.

For example, a driver who refuses a random drug test does not create just one record. You may have the random-selection record, the notification, the collection-site communications, the refusal documentation, and records showing the driver was removed from safety-sensitive functions. The refusal itself belongs in the five-year category. The selection evidence is subject to its own three-year requirement.

Do not confuse an alcohol result of 0.02 with the 0.04 alcohol concentration that triggers a DOT violation. They are different operational thresholds. A result from 0.02 to 0.039 may require removal from safety-sensitive duty under applicable rules even though it is not the same as a 0.04 violation. Both categories still require five-year retention when the alcohol result is 0.02 or greater.

If a driver enters the SAP process, keep the SAP evaluations, follow-up testing plan, return-to-duty test documentation, and follow-up test records for five years. A clean return-to-duty result does not shorten the file.

Three-year records: prove the random pull was legitimate

Random testing is where a fleet's process is often tested, not just its result files. FMCSA requires employers to retain records documenting the random selection process and the dates selections were made for three years.

A spreadsheet showing a few driver names is weak evidence. It may not establish who was eligible, whether the pool was complete, when the pull occurred, or whether every eligible driver had an equal chance of selection. A defensible random-selection record should show the eligible driver pool at the time of the pull, the selection date and time, the method used to generate selections, the number selected, and the selected driver list.

Keep notifications and status history with that pull even when the result itself has only a one-year retention period. The regulations distinguish the test result from the random-selection process. Operationally, those records are far more useful when they remain connected. When an auditor asks why a driver was tested, you should be able to move from the locked pool snapshot to the random selection, notification, collection status, and recorded outcome without reconstructing the story from emails.

This is why a timestamped selection log matters. It demonstrates that the pool and selection existed at the time you say they did, rather than being rebuilt after an audit notice arrives.

Build the File Around the Event, Not the Folder

Paper folders and disconnected spreadsheets tend to create a predictable problem: records are technically retained but cannot be produced as a coherent chain. A better approach is to organize documentation by testing event and preserve the related audit trail.

For each random testing cycle, maintain the pool roster used for that selection, the locked eligibility snapshot, the documented random-number method, selection output, notification date, collection status, result status, and any exception or follow-up notes. This does not replace required custody-and-control forms, laboratory reports, alcohol testing forms, or SAP documents. It makes those documents easier to locate and explain.

The same discipline applies to driver status changes. If a driver is hired, terminated, placed out of service, returns to duty, or moves between company pools, retain the change history that explains whether the driver belonged in a particular random pool. Eligibility questions can become audit questions quickly.

A system such as DTSMS Online is designed to preserve the workflow evidence around the pull: pool snapshots, documented selection generation, timestamped notices, and write-once result history. You run the pull, but the record trail is there when DOT asks.

Retention Mistakes That Create Avoidable Exposure

The most common error is applying the one-year rule to the entire file because a driver tested negative. The negative test result may be kept for one year, but the random-selection documentation supporting that test must generally remain available for three years. Delete them on separate schedules.

Another mistake is treating a TPA or collection site as the records owner. A service provider may store documents, but the employer remains responsible for producing required records. If your agreement ends, can you export the selection history, notifications, result records, and supporting documents? If the answer is no, your retention process depends on someone else's inbox and contract terms.

A third problem is overwriting records. If a safety manager edits a roster, changes a result status, or corrects a notification date, the system should preserve who made the change, when it happened, and what changed. A clean-looking record with no history can be harder to defend than a record that shows a documented correction.

Finally, do not let annual reporting become a separate, untraceable task. Retain the annual MIS report for three years and make sure the underlying data can be reconciled to your completed tests, refusals, and violations. The report should be the output of your records, not a number assembled from memory at year-end.

A Simple Retention Workflow for Busy Fleets

Set the retention category when the record is created. A negative random drug result should be tagged for one year, while the related random-selection evidence is tagged for three years. A verified positive, refusal, or alcohol result of 0.02 or greater should trigger a five-year retention category and a separate compliance action workflow.

Review access as carefully as retention. Drug and alcohol testing records are confidential and should be available only to authorized personnel with a business need to know. Store electronic records in a controlled account, limit editing permissions, and maintain exports or backups that can be produced if your software access changes.

Once each year, audit your own file structure. Pick one completed random selection and ask whether you can produce the eligible pool, selection method, notification trail, result, and retention classification in minutes. If you cannot, fix the workflow before an auditor, accident investigation, or driver dispute exposes the gap.

The useful standard is not merely whether you still have a document. It is whether your records tell a complete, time-stamped story that holds up without a sales call, a scavenger hunt, or anybody in between.