3
Records required per vehicle (396.3(b))
1 yr
Retention while vehicle in service
6 mo
Retention after vehicle leaves control
30 days
Control threshold that triggers a file
In This Guide
The Systematic Maintenance Requirement
Section 396.3 of the Federal Motor Carrier Safety Regulations is the foundation of vehicle maintenance compliance. It does two distinct things: it imposes a duty to maintain vehicles, and it imposes a duty to document that maintenance. Under 49 CFR 396.3(a), 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. The same subsection requires that parts and accessories be in safe and proper operating condition at all times, including those specified in Part 393 and any additional parts and accessories that may affect the safety of operation, such as frame and frame assemblies, suspension systems, axles, wheels, and steering systems.
The operative word is "systematically." FMCSA does not publish a single mileage or time interval that every carrier must follow, because a long-haul sleeper team and a local delivery box truck do not wear the same way. Instead, the regulation expects the carrier to establish a maintenance program with regular, scheduled intervals appropriate to its vehicles and operations — and to follow it. A program is systematic when there is a documented schedule and a documented history showing the schedule was actually met. A program that only fixes things when they break is reactive, not systematic, and an FMCSA auditor will recognize the difference immediately.
Two duties in one section
396.3(a) is the duty to maintain — keep the vehicle safe and its parts in proper operating condition at all times. 396.3(b) is the duty to document — keep a file per vehicle proving you did. A carrier can technically maintain its trucks well and still fail an audit on 396.3 if the records aren't there to prove it. Maintenance without documentation is, for compliance purposes, undocumented.
The Three Records Every File Needs
The documentation requirement is in 49 CFR 396.3(b). It states that a motor carrier must maintain records for each motor vehicle it controls for 30 consecutive days or more — and for intermodal equipment under an interchange agreement. For each such vehicle, the file must contain three specific records. They are short to state but easy to get wrong.
Identification
An identification of the vehicle including company number (if so marked), make, serial number, year, and tire size.
Schedule
A means to indicate the nature and due date of the various inspection and maintenance operations to be performed.
History
A record of inspection, repairs, and maintenance indicating their date and nature.
These three records map to three questions an auditor will ask of any vehicle: What is this truck? When is its next service due, and what does the program call for? And what has actually been done to it, and when? A complete file answers all three. A file missing any one of them is incomplete — and incompleteness across multiple vehicles signals a systemic recordkeeping failure rather than an isolated gap.
1. Vehicle Identification (396.3(b)(1))
The first record is the vehicle's identity. Under 49 CFR 396.3(b)(1), the file must identify the vehicle including its company number if the vehicle is so marked, make, serial number (the VIN), year, and tire size. This sounds trivial, but it serves a real purpose: it ties every schedule entry and every repair record unambiguously to one specific unit. In a fleet with several trucks of the same make and model year, the company number and VIN are what prevent records from being attributed to the wrong vehicle.
The identification record (396.3(b)(1))
- Company number — if the vehicle is so marked
- Make
- Serial number (VIN)
- Year
- Tire size
2. The Maintenance Schedule (396.3(b)(2))
The second record is the schedule — the documented plan that makes the program "systematic." Under 49 CFR 396.3(b)(2), the file must include a means to indicate the nature and due date of the various inspection and maintenance operations to be performed. This is the proactive half of the file: it lays out what is supposed to happen and when, so that scheduled service is anticipated rather than discovered after a failure.
The regulation deliberately does not dictate the format or the intervals. A carrier can use a preventive maintenance schedule keyed to mileage, engine hours, calendar time, or a combination. What matters is that the schedule states the nature of each operation — what is being inspected or serviced — and its due date, and that it is documented per vehicle. At a practical level, a sound schedule addresses the safety-critical systems first: brakes, tires, steering, and lights are the components most likely to generate roadside violations, so they are the components a defensible maintenance schedule prioritizes.
The schedule is what proves "systematic"
Auditors look for the 396.3(b)(2) schedule because it is the difference between a program and a habit. A carrier that services trucks "when they seem to need it" has no schedule to show — and no way to demonstrate the program is systematic. Set intervals appropriate to your vehicles, write them down per unit, and you have satisfied this element regardless of the exact mileage you choose.
3. The Inspection and Repair History (396.3(b)(3))
The third record is the history — the proof that the schedule was followed and that defects were addressed. Under 49 CFR 396.3(b)(3), the file must contain a record of inspection, repairs, and maintenance indicating their date and nature. Where the schedule looks forward, the history looks back: it is the dated log of every inspection performed, every repair made, and every maintenance operation completed on the vehicle.
In practice, the history is built from dated work orders and invoices that describe the work done. Each entry should make clear which vehicle was serviced, when, and what the nature of the service or repair was. This is also where the maintenance file connects to the rest of Part 396: when a driver reports a defect on a DVIR under 49 CFR 396.11 and the carrier repairs it, the repair work order belongs in this history. The DVIR proves the defect was found and the repair certified; the maintenance file's history record proves the repair was actually performed and documents its nature. The two records corroborate each other.
What each history entry should establish
Which vehicle (tied to the 396.3(b)(1) identification), the date the work was performed, and the nature of the inspection, repair, or maintenance. Dated work orders and invoices are the standard documentation.
Why brake and tire records matter most
Brake and tire defects are the most frequently cited Vehicle Maintenance violations at roadside. A clean, dated repair history for these systems is the evidence that supports a DataQs challenge when a violation is disputed.
How it connects to the DVIR
A defect reported on a DVIR (396.11) and repaired should appear as a dated repair record here. The DVIR shows the defect and the repair certification; this history shows the repair was done and what it involved.
Retention: One Year in Service Plus Six Months After
Under 49 CFR 396.3(c), the records required by 396.3(b) must be retained where the vehicle is either housed or maintained for a period of one year, and for six months after the motor vehicle leaves the motor carrier's control. This is a two-part retention rule, and the second part catches many carriers off guard: when you sell, trade, or return a vehicle, your recordkeeping obligation for that vehicle does not end on the day it leaves — it continues for another six months.
The retention period for the maintenance file is distinct from the other Part 396 records, and the differences matter. The daily driver vehicle inspection report under 49 CFR 396.11 is kept for only three months. The annual (periodic) inspection report is kept for fourteen months. The systematic maintenance file is the longest-running of the three while a vehicle is in service. Keeping these distinct windows straight by hand is error-prone, which is one reason carriers move maintenance records into a system that tracks each retention clock per record type.
| Record | Regulation | Retention period |
|---|---|---|
| Systematic maintenance file (per vehicle) | 49 CFR 396.3(c) | 1 year in service + 6 months after vehicle leaves carrier |
| Annual (periodic) inspection report | 49 CFR 396.17 / 396.21 | 14 months from date of inspection |
| Driver Vehicle Inspection Report (DVIR) | 49 CFR 396.11(a)(4) | 3 months from date report was prepared |
Common Maintenance-File Mistakes
The maintenance file is one of the most commonly cited areas in FMCSA reviews, and the failures follow predictable patterns. These are the gaps that turn a fleet that maintains its trucks well into a fleet that fails on 396.3.
What gets carriers cited
- No documented maintenance schedule — only repair receipts after failures
- Repair history entries missing the date or the nature of the work
- Records not tied to a specific vehicle by company number or VIN
- Discarding a sold vehicle's file before the 6-month post-control window closes
- DVIR-reported defects with no corresponding repair record in the file
- Brake and tire work that is performed but not documented
What a clean file looks like
- Every vehicle has all three 396.3(b) records present and current
- A written PM schedule states the nature and due date of each operation
- Every repair is dated, describes the work, and names the vehicle
- Files are retained the full 1 year + 6 months after the vehicle leaves
- DVIR defects cross-reference the repair record that cleared them
- Brake and tire history is complete enough to support a DataQs challenge
How FileFlo Organizes the Maintenance File
FileFlo is the records and proof layer for your fleet. It is not a shop maintenance system and it does not perform or schedule repairs — you keep using whatever tools your maintenance team relies on. What FileFlo does is organize the per-vehicle records 49 CFR 396.3 requires, keep each retention clock straight, and produce the file an auditor asks for without a scramble.
What FileFlo does with your maintenance records
- Keeps a complete file per vehicle: Store the 396.3(b) identification, schedule, and inspection/repair history together for each unit, so every vehicle's file is complete and tied to its company number and VIN.
- Tracks maintenance due dates: Hold the maintenance schedule — the nature and due date of each operation under 396.3(b)(2) — and surface what is coming due, so scheduled service is anticipated rather than missed.
- Holds the file for the full retention window: Track the 1-year-in-service-plus-6-months-after clock under 396.3(c) automatically, including the easy-to-miss six months after a vehicle leaves your control.
- Connects repairs to DVIR defects: Link a repair record to the DVIR defect it resolved, so the maintenance file and the driver report corroborate each other and the close-out loop is provable.
- Exports an audit-ready package: When FMCSA reviews your Vehicle Maintenance records, export each vehicle's full file — identification, schedule, and dated repair history — as an organized package in minutes.
Key Takeaways
- 49 CFR 396.3 imposes two duties: maintain vehicles systematically (396.3(a)) and document that maintenance per vehicle (396.3(b)). Good maintenance without records still fails the audit.
- The file has three records: identification (b)(1), a maintenance schedule showing nature and due date (b)(2), and a dated inspection/repair history (b)(3).
- Retention is 1 year in service plus 6 months after the vehicle leaves your control. The post-control six months catches carriers who discard files when they sell a truck.
- The schedule is what proves "systematic." FMCSA does not set fixed intervals — it expects you to set appropriate ones and document them per vehicle.
- The maintenance file connects to the DVIR. A defect reported under 396.11 and repaired should appear as a dated repair record here — the two records corroborate each other.
DOT Vehicle Maintenance File: FAQ
Answers to common questions about the systematic maintenance program and the per-vehicle records required under 49 CFR 396.3.
Under 49 CFR 396.3(b), a motor carrier must keep a maintenance file for each vehicle it controls for 30 consecutive days or more. The file must contain three things: (1) an identification of the vehicle, including company number if so marked, make, serial number, year, and tire size; (2) a means to indicate the nature and due date of the various inspection and maintenance operations to be performed; and (3) a record of inspection, repairs, and maintenance indicating their date and nature. The first element identifies the vehicle, the second is the maintenance schedule, and the third is the running history of work performed.
Under 49 CFR 396.3(c), the per-vehicle maintenance records required by 396.3(b) must 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. So if you sell or return a truck, you still have to keep its maintenance file for another six months. This is a longer and different retention period than the daily driver vehicle inspection report (DVIR), which is kept for only 3 months under 396.11, and the annual inspection report, which is kept for 14 months.
No. They are different records governed by different sections of Part 396. The vehicle maintenance file under 49 CFR 396.3 is the long-term, per-vehicle history of identification, scheduling, and all inspection and repair work, retained 1 year plus 6 months after the vehicle leaves your control. The DVIR under 49 CFR 396.11 is the daily, defect-driven driver report retained for only 3 months. A defect that a driver reports on a DVIR, once repaired, should be reflected as a repair record in the vehicle maintenance file — so the two records connect, but they are not interchangeable.
49 CFR 396.3(a) requires every motor carrier to systematically inspect, repair, and maintain all motor vehicles subject to its control, and to keep parts and accessories in safe and proper operating condition at all times. 'Systematic' means the program is regular, scheduled, and documented — not reactive. FMCSA does not prescribe a single fixed mileage or time interval that fits every fleet; instead it expects the carrier to establish intervals appropriate to its vehicles and operations and to follow them. The maintenance schedule required by 396.3(b)(2) — the means to indicate the nature and due date of operations — is the documentation that proves the program is systematic rather than ad hoc.
Under 49 CFR 396.3(b), the recordkeeping requirement applies to each motor vehicle a carrier has controlled for 30 consecutive days or more — and to intermodal equipment that is intermodal equipment interchange agreement equipment. The practical effect is that a vehicle a carrier owns or leases on a long-term basis needs a maintenance file, while a unit borrowed for a few days generally does not. The systematic inspection, repair, and maintenance obligation in 396.3(a), however, applies to all vehicles subject to the carrier's control regardless of the 30-day record threshold, so a carrier cannot skip maintenance just because a record is not yet required.
Under 49 CFR 396.3(b)(3), the file must contain a record of inspection, repairs, and maintenance indicating their date and nature. At a minimum, each entry should make clear which vehicle the work was done on, the date it was performed, and what was done — the nature of the inspection or repair. In practice, carriers document this with dated work orders and invoices that describe the service. Brake and tire work in particular should be well documented, because those systems are the most common sources of Vehicle Maintenance violations, and a clean repair history is the evidence that supports a DataQs challenge if a violation is later disputed.
Keep a Complete 396.3 File for Every Truck
FileFlo organizes the identification, maintenance schedule, and dated repair history 49 CFR 396.3 requires for every vehicle, tracks each retention clock — including the six months after a truck leaves your control — and exports an audit-ready file in minutes. Stay maintenance-record ready every day, not just when FMCSA calls.
Plans from $89/month — No credit card required — 5-day free trial