Quick Links
Use the Maintenance report category to review driver-reported vehicle defects and analyze current and historical fleet maintenance activity. These spreadsheet reports support short-term defect follow-up, repair research, recurring issue analysis, and long-range maintenance planning.
Understanding Maintenance Reports
Maintenance reports bring together inspection, defect, repair, and component-level information so you can:
- Review eDVIR inspections and reported defects from a rolling three-month period.
- Check the recorded status of driver-reported defects.
- Identify defects that may require additional review or service coordination.
- Research current and historical fleet maintenance and repairs.
- Review maintenance history using a two-year or seven-year reporting period.
- Analyze repairs by VMRS system, assembly, and component codes.
- Review recorded repair reasons and part descriptions.
- Compare recent repair activity with longer-term vehicle history.
- Export detailed records for additional filtering, analysis, or documentation
- The Maintenance category includes eDVIR Defects, Maintenance History (2 Years), and Maintenance History (7 Years).
eDVIR Defects
The eDVIR Defects report contains Electronic Driver Vehicle Inspection Report inspections, defects, and the recorded status of those defects for a rolling three-month period. Use it to review recently reported vehicle concerns and determine which records may need closer attention.
The report includes eDVIR inspections, reported defects, defect status, and a rolling three-month history. The eDVIR Defects report reflects reported inspections, defects, and recorded statuses. A defect entry does not necessarily represent every repair completed during a shop visit, and the displayed status should be validated before drawing conclusions about the work performed.
Use this report to:
- Review recently submitted eDVIR inspections.
- Identify vehicles with reported defects.
- Check the recorded status of each defect.
- Find defects that remain unresolved or require validation.
- Compare recent defect activity across vehicles.
- Prepare a working list for maintenance follow-up.
- Support conversations about recently reported vehicle concerns.
- Export recent inspection and defect records for additional analysis.
Maintenance History (2 Years)
The Maintenance History (2 Years) report provides current and two years of historical fleet maintenance and repair details. It is designed for recent service research, recurring repair analysis, and detailed review of the systems, assemblies, components, reasons, and parts associated with maintenance activity.
The report includes current maintenance and repair details, two years of historical maintenance and repair details, repair reason, part description, VMRS system codes, assembly codes, and component codes. Use this report for most recent history questions. Its narrower period can make it easier to focus on current maintenance patterns without reviewing older records that may no longer be relevant.
Maintenance History (7 Years)
The Maintenance History (7 Years) report provides current and seven years of historical fleet maintenance and repair details. It contains the same described maintenance fields as the two-year report but offers a longer view for lifecycle research and long-term pattern analysis.
The report includes current maintenance and repair details, repair reason, part description, seven years of historical maintenance, repair details, VMRS system codes, assembly codes, and component codes. A longer reporting period provides more context but may also include repairs that are no longer representative of the vehicle's current condition. Give greater weight to relevance, recurrence, and supporting documentation rather than age alone.
Common Questions
Does a defect status confirm that a repair was completed?
Not by itself. The status is one report field and should be reviewed with maintenance history and supporting repair documentation when confirmation of completed work is required.
Can every eDVIR defect be matched to a maintenance-history record?
A direct match should not be assumed. The reports cover different information and time periods, and a reported defect may not correspond one-to-one with a repair record.