FMCSA Vehicle Maintenance Record Services

FMCSA vehicle maintenance record services organize the evidence that a carrier systematically inspects, repairs and maintains every commercial motor vehicle under its control. The work is broader than scanning repair invoices. A usable system connects each vehicle to a maintenance schedule, inspection findings, completed repairs, annual inspections and an exception queue that prevents defects from disappearing between the shop and dispatch.

Which vehicle records are required?

For vehicles controlled for 30 consecutive days or more, Section 396.3 requires identifying information, a schedule of inspections and maintenance, and records showing the date and nature of inspection, repair and maintenance work. Those Section 396.3 records generally remain at the location where the vehicle is housed or maintained for one year and for six months after the vehicle leaves the carrier’s control. Periodic inspection reports have a separate 14-month retention requirement. Roadside inspection reports and repair certifications are generally retained for 12 months under Section 396.9, while required driver vehicle inspection reports and certifications use the applicable three-month rule in Section 396.11. A system should assign retention by record type rather than one blanket date.

What maintenance record management should include

Maintenance software does not make the release decision

A dashboard can flag a defect or overdue service, but the motor carrier remains responsible for ensuring that an unsafe or noncompliant vehicle is not operated. Appropriately authorized internal or outside maintenance personnel may inspect, repair and make required certifications, with specific federal qualification rules applying to functions such as periodic inspections and brake work. Dispatch must be blocked for an out-of-service condition, an expired required periodic inspection or a defect that must be repaired before operation, not automatically for every open maintenance item. Where the rule permits it, closure may certify that repair was unnecessary rather than inventing a repair. The driver still has the applicable pre-trip duty to be satisfied that the vehicle is in safe operating condition.

When an outside shop performs the work, the carrier still needs evidence adequate to show the defect was corrected. A credit-card line or invoice reading “truck repair” is not a detailed maintenance record. Require unit number, date, complaint, findings, labor and parts description, and completion status.

How to compare vehicle maintenance record providers

• Can the system maintain tractors, trailers and leased units separately with exact control dates?
• Does it support time, mileage and engine-hour service intervals?
• Can driver or roadside defects create a work order without manual re-entry?
• How is repair completion approved, and can dispatch see unresolved safety holds?
• Can vendor invoices and annual inspection reports be indexed to the correct unit?
• Does it retain records after a vehicle is sold or returned?
• Can records be exported by unit and period in a readable audit package?
• Will the provider help migrate existing files without losing service history?
• Does the system record who changed a due date, status or closure?

A practical implementation sequence

1. Reconcile the equipment list. Compare registrations, leases, insurance schedules and dispatch records.
2. Load current baselines. Enter odometers, last services, annual inspection dates and known open defects.
3. Define maintenance intervals. Use manufacturer guidance, operating conditions, experience and regulatory needs.
4. Assign responsibilities. Name who reports defects, approves work, updates mileage, releases vehicles and reviews overdue items.
5. Test one complete record. Follow a defect from driver report through repair and confirm the evidence is retrievable.
6. Review exceptions routinely. Overdue, missing or repeatedly repaired items should be management work, not dashboard decoration.

Common recordkeeping failures

Carriers often maintain annual inspection reports but cannot show a systematic program between inspections. Other failures include records filed under inconsistent unit numbers, trailer work omitted, inspection defects marked closed without repair detail, maintenance due dates altered without explanation, and files discarded as soon as equipment is sold. Weak records can also hide a real safety problem until roadside inspections reveal it repeatedly.

The provider should help make recurrence visible. Repeated brake, light, tire or coupling defects may indicate weak inspection quality, parts problems, driver reporting gaps or an unrealistic maintenance interval. Treat the record system as an operating control, not only an audit archive.

For hours-of-service and electronic log review, use ELD and HOS compliance services. For a broader operational assessment, compare mock DOT audit support.