FMCSA Record Retention: How Long to Keep Every DOT Record

There is no single FMCSA retention period. There are at least nine, they range from three months to five years, two of them are measured from something other than the record's own date, and three of them specify where the record has to be kept as well as how long. A fleet that keeps everything for three years is over-retaining some records and under-retaining others.

This is the full set a fleet operation owns, with the governing section beside each one and the period as the regulation states it. Nothing here is a recommendation or a best practice; it is the published requirement, read from the eCFR text current to 1 November 2026.

Every FMCSA retention period in one table

Three patterns are worth noticing in that table. Two periods run from an event rather than from the record's date — maintenance records from when the vehicle leaves your control, driver qualification files and training records from when the person stops. Three periods specify a location, and two of those locations are physical: "where the vehicle is housed or maintained." And one period, the annual inspection report's 14 months, is deliberately longer than the interval it documents.

Maintenance records: 49 CFR 396.3

Section 396.3(a) is the duty itself, and it is worth quoting because it does not say what people often think it says: "Every motor carrier and intermodal equipment provider must systematically inspect, repair, and maintain, or cause to be systematically inspected, repaired, and maintained, all motor vehicles and intermodal equipment subject to its control."

There is no mileage interval in that sentence and none anywhere else in the section. FMCSA requires a system, not a schedule it specifies. That is why two fleets can both comply with wildly different PM intervals, and why "we follow the OEM schedule" is an answer to a different question than the one an auditor is asking. The question is whether your intervals are documented, applied and recorded.

Paragraph (b) is where the records are specified, and it is scoped: it applies to "each motor vehicle they control for 30 consecutive days." A rental taken for a fortnight is outside it. The required contents are four items:

• An identification of the vehicle including company number if so marked, make, serial number and year — plus, if the vehicle is not owned by the carrier, the name of the person furnishing it
• A means to indicate the nature and due date of the various inspection and maintenance operations to be performed
• A record of inspection, repairs and maintenance indicating their date and nature
• A record of tests conducted on pushout windows, emergency doors and emergency door marking lights on buses

The second item is the one software exists to satisfy, and it is a forward-looking requirement: a means to indicate what is due and when. A pile of completed work orders satisfies the third item and not the second. If an auditor asks what maintenance is due on a unit next month and the answer requires someone to work it out, that item is not met.

Paragraph (c) sets both the period and the place: the records "shall be retained where the vehicle is either housed or maintained for a period of 1 year and for 6 months after the motor vehicle leaves the motor carrier's control." Two things follow. A multi-yard fleet cannot satisfy this with one central archive unless the records are also available at the yard. And selling a truck does not end the obligation — it starts a six-month clock.

One interval does sit inside this section rather than in its own: 396.3(a)(2) requires that "pushout windows, emergency doors, and emergency door marking lights in buses shall be inspected at least every 90 days." If you run buses, that is four inspections a year with a record each, and it is easy to miss because nothing in the section heading suggests it.

DVIRs: three months, and only when there is a defect

Section 396.11(a)(1) requires every driver to prepare a written report at the completion of each day's work on each vehicle operated, covering at least eleven named items: service brakes including trailer brake connections, parking brake, steering mechanism, lighting devices and reflectors, tyres, horn, windshield wipers, rear vision mirrors, coupling devices, wheels and rims, and emergency equipment.

But 396.11(a)(2)(i) then says plainly: "Drivers are not required to prepare a report if no defect or deficiency is discovered by or reported to the driver." A no-defect DVIR is not a federal requirement. Many fleets require one anyway as a management control, which is a legitimate choice, but it should be understood as a company policy rather than a compliance obligation — and it means the volume of DVIRs a system has to store is a policy decision, not a given.

Where a defect is reported, 396.11(a)(3) requires the carrier or its agent to repair any defect "which would be likely to affect the safety of operation of the vehicle" before requiring or permitting a driver to operate it, and to certify on the report that the defect has been repaired or that repair is unnecessary. Paragraph (a)(4) then sets the retention: the carrier "shall maintain the driver vehicle inspection report, the certification of repairs, and the certification of the driver's review for three months from the date the written report was prepared."

Three records, one period. Fleets that store the DVIR and lose the repair certification have kept a third of what the section asks for. Paragraph (a)(6) permits all of it in electronic format in accordance with 49 CFR 390.32, so this is a records-architecture problem rather than a paper one.

There are exceptions in 396.11(a)(5): the section does not apply to a private motor carrier of passengers (nonbusiness), a driveaway-towaway operation, or "any motor carrier operating only one commercial motor vehicle." That last one is the single-truck owner-operator carve-out, and it is narrower than it sounds: it is one vehicle, not one driver. More on what else changes at that scale in our walkthrough of the FMCSA new entrant safety audit. The term itself is defined in our glossary entry for DVIR.

Records of duty status: six months from receipt

Section 395.8(k)(1) sets the carrier's period: "A motor carrier shall retain records of duty status and supporting documents required under this part for each of its drivers for a period of not less than 6 months from the date of receipt."

Two details in that sentence do real work. It is six months from receipt, not from the date the driving happened, so a log that reaches the office late extends its own retention window. And it covers supporting documents as well as the logs themselves, which in practice means fuel receipts, dispatch records, toll records and bills of lading share the retention period of the log they support.

Paragraph (k)(2) is a driver obligation rather than a carrier one: the driver "shall retain a copy of each record of duty status for the previous 7 consecutive days which shall be in his/her possession and available for inspection while on duty." Seven days in the cab, six months in the office.

The limits those records evidence are in 395.3: 10 consecutive hours off duty before driving, no driving after the 14th consecutive hour following coming on duty, a maximum of 11 hours' driving in that window, a required 30-minute interruption after 8 cumulative hours of driving time, and the 60-hour-in-7-days or 70-hour-in-8-days ceilings, each resettable by 34 or more consecutive hours off duty. Our glossary covers hours of service and the ELD that now records most of it.

Driver qualification files: employment plus three years

Section 391.51(c) sets the headline period: each driver's qualification file "shall be retained for as long as a driver is employed by that motor carrier and for three years thereafter." That is the longest routine retention obligation most fleets carry, and the one most likely to be broken by a payroll system that purges leavers.

Paragraph (d) then permits five specific items to be removed three years after the date of execution, which is a thinning rule rather than a shorter retention period:

• The motor vehicle record from the annual driver record inquiry required by 391.25(a)
• The note relating to the annual review of the driver's driving record required by 391.25(c)(2)
• The medical examiner's certificate required by 391.43(g), a legible copy, or for CDL drivers the CDLIS MVR obtained under 391.51(b)(6)(ii)
• Any medical variance issued by FMCSA, including a Skill Performance Evaluation Certificate under 391.49, or a Medical Exemption letter issued under Part 381
• The note verifying the medical examiner's listing on the National Registry of Certified Medical Examiners required by 391.23(m)

Two deadlines govern what goes in rather than how long it stays. Under 391.23(b), the motor vehicle record from each driver's licensing authority "must be placed in the driver qualification file within 30 days of the date the driver's employment begins," and where no record is received the carrier must document a good faith effort to obtain it. Under 391.23(c)(1), replies to the safety performance history investigation, or documentation of good faith efforts, must be placed in the driver investigation history file within 30 days of the employment start date — and the section is explicit that any time taken up by the driver exercising review and rebuttal rights sits outside that 30-day clock.

Accident register: three years, and six specified fields

Section 390.15(b) requires carriers to "maintain an accident register for 3 years after the date of each accident," and specifies what each entry contains: the date of the accident; the city or town, or nearest, and the State where it occurred; the driver's name; the number of injuries; the number of fatalities; and whether hazardous materials other than fuel spilled from the fuel tanks of a vehicle involved were released. The register must also hold copies of all accident reports required by State or other governmental entities or insurers.

Note that the period runs from each accident, so the register is not purged as a whole. And note the sixth field: the hazardous-materials question has a carve-out for fuel spilled from the fuel tanks of vehicles involved in the accident, which is a distinction that register templates frequently get wrong.

Drug and alcohol programme records: four different periods

Section 382.401 is the only one of these sections that specifies storage conditions as well as a period: records "shall be maintained in a secure location with controlled access." It then splits the retention into four bands, and the bands do not follow the shape of the rest of Part 382.

Five years covers the serious outcomes: driver alcohol test results indicating a concentration of 0.02 or greater, verified positive controlled substances results, documentation of refusals, driver evaluations and referrals, calibration documentation, records related to the administration of the programme including all driver violations, and a copy of each annual calendar year summary required by 382.403.

Two years covers records related to the collection process, except calibration of evidential breath testing devices, which sits in the five-year band. One year covers negative and cancelled controlled substances results, MRO reversals of cancelled results, and alcohol results below 0.02. And training records for breath alcohol technicians, screening test technicians, supervisors and drivers are kept while the individual performs the function and for two years after they stop.

The practical consequence is that a single drug and alcohol file cannot have one retention rule applied to it. A negative result and a refusal in the same month have retention periods four years apart.

How this gets managed, and where systems fail

Retention failures are almost never decisions. They are three mechanical problems.

The first is a period measured from an event the records system cannot see. A driver qualification file has to survive three years past a termination date that lives in HR, and maintenance records have to survive six months past a disposal date that lives in finance or in a spreadsheet. If the retention clock is in one system and the trigger is in another, records get purged on schedule by something that does not know the rule.

The second is the location requirement. Two of the periods in the table — 396.3(c) and 396.21(b)(1) — say the record must be kept where the vehicle is housed or maintained. A central cloud archive satisfies this if the yard can retrieve it; it does not if retrieval depends on someone in head office during business hours. This is a question worth asking a vendor directly rather than assuming.

The third is partial sets. 396.11(a)(4) names three documents, 396.3(b) names four record types, 390.15(b) names six fields plus attachments, and 396.21(a) names six report contents. An auditor checks the set, not the headline document, and a system that stores the primary record while dropping the certification or the component-level detail produces a finding even though nothing was deleted early.

When you are shopping for fleet maintenance software, those three problems are better evaluation questions than a feature list. Ask how a retention period keyed to a disposal or termination date is enforced, ask how a record is retrieved at the yard rather than from head office, and ask to see one completed record of each type rather than a sample dashboard. Our comparison of Fullbay and Dossier shows how differently two vendors in this category present themselves on exactly these points — including the fact that only one of them publishes a price at all.

For the inspection side of the same obligation — who may perform the annual inspection, what fails a vehicle, and why the report is kept for fourteen months rather than twelve — see DOT annual inspection requirements. The DOT compliance checklist and DOT audit preparation checklist cover the document-gathering side. Verify both against the current regulation before you rely on them: the regulation governs, not the template.