A DOT audit rarely fails because a fleet cannot explain its program. It fails because the proof is scattered, incomplete, or gone. If you are asking how long retain DOT records, start with this: there is no single retention period for every DOT document. The clock depends on the record type, the regulation behind it, and sometimes the test result.
For a small or mid-sized fleet, the practical goal is straightforward: keep a record schedule that tells your team what to preserve, where it lives, and when it can be destroyed. That removes guesswork when an investigator asks for a random-selection history, a driver qualification file, or six months of logs.
DOT record retention depends on the record
DOT is an umbrella term. FMCSA drug and alcohol testing records follow one set of timelines. Hours-of-service records follow another. Driver qualification, vehicle maintenance, crash, and Clearinghouse records each have their own rules.
The table below is a working retention schedule for common FMCSA-regulated fleet records. It is a compliance operations tool, not a substitute for reviewing the exact rule that applies to your operation, state requirements, contracts, litigation holds, or insurer requirements.
| Record category | Common retention period | Operational point | | --- | --- | --- | | Positive drug tests, alcohol results of 0.02 or greater, refusals, SAP records, follow-up tests, annual MIS reports | 5 years | Separate these from routine negative-result files. | | Calibration documentation for alcohol testing devices | 5 years | Keep it with the testing program evidence, not in a loose vendor email folder. | | Random selection process and collection-related records | Generally 2 years | Preserve the eligible pool, selection method, dated pull, notifications, and status history. | | Supervisor training and employee training records | 2 years | Retain proof of who completed training and when. | | Negative and canceled drug tests; alcohol results below 0.02 | 1 year | Do not accidentally apply the five-year rule to every negative test. | | Driver vehicle inspection reports, ELD data, records of duty status, and supporting documents | 6 months | The six-month clock is short, but missing documents are a frequent exposure. | | Driver qualification file materials | Often 3 years after employment ends, with some items kept while employed | Review each file component instead of using one blanket deletion date. | | Clearinghouse query records | 3 years | Document both the required pre-employment full query and annual limited queries. | | Accident register | 3 years after the accident | Maintain the register even when the crash file is handled by an insurer. | | Vehicle maintenance files | 1 year while the vehicle is in use and 6 months after it leaves your control | Keep inspection, repair, and maintenance history tied to the unit number. |
Retention rules can change by circumstance. For example, a driver qualification file stays active during employment, while particular supporting documents may have a different post-employment retention period. If a claim, dispute, investigation, or legal hold exists, do not destroy records simply because the minimum DOT period has ended. Put normal deletion on hold and get appropriate legal guidance.
Drug and alcohol testing records: sort by outcome
For most fleet compliance teams, drug and alcohol program files create the most confusion because a single testing event produces multiple documents. There may be a selection record, a notification, a custody-and-control form, a laboratory result, a medical review officer verification, and collection-status notes.
Under 49 CFR Part 382, five-year records include verified positive controlled substances test results, alcohol test results showing a concentration of 0.02 or greater, refusals to test, substance abuse professional evaluations and referrals, follow-up testing records, calibration documentation, and annual MIS reports. These are not routine records. They document a violation, a return-to-duty process, or the integrity of alcohol testing equipment.
Negative and canceled drug test results, plus alcohol test results below 0.02, are generally retained for one year. Collection-process and employee training records are generally retained for two years.
The retention period is only half the job. A result file that cannot be connected to the driver, reason for test, date, and final disposition is weak evidence. Keep records in a structure that makes the sequence clear: why the test occurred, whether the driver completed it, what happened next, and who updated the record.
Random selection evidence needs its own file trail
A random test result does not prove that your random-selection process was compliant. An auditor may want to see the eligible pool, the selection date, the method used, the rate applied, the selected driver list, and evidence that selected drivers were notified and tested.
That is where spreadsheet-based programs become risky. A spreadsheet may show a name, but it often cannot show whether the driver was eligible at the moment of selection, whether someone changed the roster after the pull, or whether the selection was genuinely random.
Keep the source evidence for the selection process for the applicable two-year period, along with the test results for their required duration. A defensible file has a locked eligible-pool snapshot, documented random-number generation, a timestamped selection report, notification history, and status changes through collection and result entry. You need to be able to show the process, not just announce that a pull happened.
DTSMS Online is built around that distinction. You run the pull, while the system preserves the pool snapshot, selection history, notifications, and write-once result trail that can hold up when DOT asks.
Hours-of-service records: six months goes fast
Hours-of-service records are often easier to retrieve than testing records because ELD systems collect much of the data automatically. That does not make retention optional. Motor carriers generally must retain records of duty status and supporting documents for six months. ELD records and required backup data also need to remain available for the required period.
The risk is usually not the ELD file itself. It is the missing supporting document, the unresolved unidentified driving event, or the inability to produce the requested period after changing ELD providers.
Before a vendor switch, export your historical data and verify that someone in your operation can retrieve it without opening a support ticket. Retention is not satisfied when the information exists somewhere in a former vendor's platform. It needs to be accessible to the motor carrier when requested.
Build a retention system that works under pressure
Do not manage DOT retention from memory, email inboxes, and a shared drive named “Compliance.” Assign an owner for each category, establish a standard file location, and use a retention calendar that identifies the record type and destruction date.
Your testing folder structure should separate random, pre-employment, post-accident, reasonable-suspicion, return-to-duty, and follow-up testing. That makes it easier to verify testing rates and produces a cleaner audit response. Within each test reason, retain the full event trail rather than storing notifications in one system and results in another.
For driver files, track employment status and termination date. For vehicles, track the date each unit leaves your control. For logs, schedule a monthly check that confirms the prior six months are complete and retrievable. These are small operational controls, but they prevent last-minute record hunts.
Electronic storage is acceptable when it protects legibility, access, and integrity. A scanned record that cannot be read is not useful. A digital file that anyone can overwrite is also a problem. Use permissions, timestamps, backups, and an audit trail for high-risk records. Keep personally identifiable information and test results restricted to people with a legitimate compliance role.
Do not confuse a minimum with a safe deletion policy
Minimum retention periods tell you the earliest point at which a record may be eligible for disposal. They do not require you to purge a record immediately. Some fleets keep certain non-sensitive compliance records longer because of insurer expectations, contract requirements, recurring audit patterns, or internal trend analysis.
There is a trade-off. Keeping everything forever creates clutter, increases privacy exposure, and makes an audit response slower. Deleting too aggressively can leave the fleet unable to prove compliance. The answer is a written schedule: retain each record for the required period, preserve it longer when a valid business or legal reason exists, and securely destroy it when it no longer needs to be kept.
When DOT asks for records, confidence comes from retrieval, not recollection. Set the schedule now, keep the evidence connected to the event, and make every file easy to produce before the request arrives.
