Guide to Vehicle Maintenance Records for Fleets

A truck can be mechanically sound and still create a compliance problem if the maintenance file is incomplete, misfiled, or impossible to produce. This guide to vehicle maintenance records explains what commercial carriers need to document, how long to keep it, and how to build a process that holds up under an audit, post-crash review, or roadside inspection.

For fleets, owner-operators, maintenance managers, and qualified inspectors, the goal is not simply collecting paperwork. The goal is proving that each commercial motor vehicle was systematically inspected, repaired, and maintained in accordance with federal requirements.

What FMCSA Requires in Vehicle Maintenance Records

Under 49 CFR 396.3, every motor carrier must systematically inspect, repair, and maintain vehicles subject to Part 396. The carrier must keep maintenance records for each vehicle it controls for 30 consecutive days or more.

The required vehicle maintenance file should identify the vehicle and show the work performed throughout its service life with the carrier. At a minimum, the record must include the vehicle identification information, the maintenance schedule used, and a record of each inspection, repair, and maintenance operation.

Vehicle identification should be specific enough to prevent confusion between units. Use the company unit number, VIN, year, make, tire size, and owner information when applicable. A unit number alone may work within a small fleet, but pairing it with the VIN creates a stronger, more traceable record.

The maintenance schedule should reflect the manufacturer’s recommendations and the way the equipment is actually used. A long-haul tractor operating in severe weather, high-mileage service, or heavy loads may need more frequent attention than a lightly used local vehicle. FMCSA does not prescribe one universal preventive maintenance interval, but it does require a system that keeps equipment in safe operating condition.

For each maintenance event, record the date, the nature of the work, and the vehicle involved. That includes preventive maintenance services, repairs, inspections, tire work, brake adjustments, lighting repairs, defect corrections, and outsourced shop work. An invoice can support the file, but it should clearly connect to the specific vehicle and service performed.

Separate the Core Records From Related DOT Documents

A complete compliance file is easier to manage when the team understands that not every inspection document serves the same purpose. Annual inspection reports, driver vehicle inspection reports, work orders, and preventive maintenance logs may all relate to the same truck, but they satisfy different operational needs.

The annual inspection required by 49 CFR 396.17 is a periodic inspection of the vehicle’s safety components. It must meet, at a minimum, the standards in Appendix G to Subchapter B of Chapter III, or an equivalent inspection program. The inspection must be performed by a qualified inspector, and the report must be retained for 14 months from the inspection date.

The annual inspection report does not replace the vehicle’s maintenance record. It confirms that the unit passed a qualifying periodic inspection on a particular date. The maintenance file shows the continuing program used to keep that unit safe before and after the annual inspection.

Driver-reported defects also require a clear workflow. Drivers must inspect vehicle condition as required and report safety defects or deficiencies they identify. When a driver report identifies a defect, the carrier should connect the report to a repair order, inspection result, or documented determination that repair was unnecessary. Leaving driver reports in a separate inbox without showing the resolution creates an avoidable documentation gap.

Build a Vehicle File That Works Under Pressure

The best recordkeeping system is one that a safety manager, shop supervisor, or auditor can understand in minutes. Whether your fleet uses paper files, fleet maintenance software, or a shared digital document system, the file structure should be consistent across every unit.

A practical vehicle file usually contains these four sections:

• Vehicle profile and ownership information, including VIN, unit number, registration details, and equipment specifications.
• Preventive maintenance schedule, with service intervals based on time, mileage, engine hours, or another documented trigger.
• Inspection and repair history, including work orders, invoices, technician notes, defect corrections, and parts replacements.
• Required periodic inspection documentation, including the annual inspection report and evidence of inspector qualification when maintained internally.

Avoid relying on a stack of invoices as the entire maintenance program. Invoices are useful proof, but they often do not show whether the work was preventive, corrective, or connected to a known defect. A simple maintenance log that lists date, mileage, service type, findings, corrective action, and next due date can turn scattered paperwork into a usable compliance record.

Digital files are acceptable when they are accurate, protected from unauthorized changes, and readily retrievable. The format is less important than the control process. If a shop uploads a repair invoice two weeks late, or drivers submit defects through an app that nobody reviews, the fleet still has a compliance weakness.

Retention Rules That Fleets Commonly Miss

For vehicle maintenance records required by 49 CFR 396.3, the carrier must keep the records for one year at the location where the vehicle is housed or maintained. If the vehicle leaves the carrier’s control, the records must be retained for six months after that date.

That rule applies to the maintenance history, not just major repairs. Fleets should have a documented offboarding process for sold equipment, returned lease units, and equipment transferred between related companies. Deleting digital records the day a truck is sold may save storage space, but it can leave the carrier without records needed for an investigation or review.

Annual inspection reports have their own retention period. Keep them for 14 months from the inspection date. Because the annual inspection cycle and the general maintenance retention rule are different, it is often easier to keep the annual inspection report within the vehicle’s main file while using retention controls that preserve it for the longer applicable period.

If your fleet operates leased equipment, clarify who creates and retains each record. A lease agreement may assign maintenance responsibilities, but it does not remove the motor carrier’s need to ensure the equipment is properly maintained while under its control. Confirm who receives repair documents, who tracks annual inspection due dates, and who can produce the file quickly.

Turn Maintenance Records Into a Compliance Process

Records are only reliable when employees know their role. Drivers need a direct method for reporting defects. Technicians need to document work clearly. Supervisors need to review overdue services and unresolved defects. Safety personnel need to verify that annual inspections are current and that the inspectors who perform them meet qualification requirements.

Start by assigning one owner for each part of the process. In a small operation, that may be the owner or maintenance manager. In a larger fleet, the shop, safety department, and dispatch team may share responsibilities. Shared responsibility is workable only when each handoff is documented.

Set preventive maintenance triggers in advance. For example, a fleet may schedule tractor services by mileage and time, while trailer inspections are scheduled by calendar date and usage. The specific interval depends on equipment, operating conditions, manufacturer guidance, and fleet experience. What matters is that the schedule is defined, followed, and adjusted when recurring defects reveal a problem.

Review open defects daily or at another documented interval that matches your operation. Brake, steering, tire, coupling, lighting, and cargo securement-related issues can quickly become out-of-service concerns. A maintenance record should show more than that the defect was reported. It should show when the vehicle was repaired, who performed the work, and whether the unit was returned to service safely.

Prepare for Audits and Roadside Questions

When a compliance review begins, disorganized records create delays that can expand the scope of the review. Build a retrieval standard before records are requested. A manager should be able to locate a vehicle’s annual inspection, latest preventive maintenance service, recent repairs, and unresolved defect status without searching through multiple systems.

Perform internal file checks on a sample of vehicles each month. Compare the maintenance schedule against actual services completed. Confirm that annual inspection dates are current. Trace a few driver-reported defects through to repair completion. If the same issue appears repeatedly, such as lighting failures or tire damage, investigate the operational cause rather than treating every repair as an isolated event.

Training matters here. Personnel who conduct periodic inspections must understand the applicable inspection criteria and qualification requirements. Safety and maintenance teams also need to know the difference between an annual inspection report, a preventive maintenance record, and a repair invoice. DOT Safety Class training can help fleets strengthen inspection knowledge and support documentation practices tied to FMCSR responsibilities.

A clean maintenance file does not keep brakes adjusted or tires properly inflated. It does, however, prove that your fleet has a disciplined system for finding defects, correcting them, and keeping unsafe equipment off the road. Build that system before the next inspection request arrives, and your records become evidence of control rather than a last-minute paperwork scramble.