Skip to content
Back to Resources
Shop OperationsFleet Contracts

Fleet Maintenance Spreadsheet: What to Track, a Free Template, and When to Move Off It

MetaFleet Team
A fleet maintenance office at dusk with a laptop showing a spreadsheet with highlighted rows, looking out at parked tractors, a trailer and an excavator in the yard

The tabs and columns a fleet maintenance spreadsheet needs, from the unit list and PM schedule to DVIR defects and annual inspection dates, a free Excel template with the formulas built in, how to keep it accurate and the signs it's time for software.

A fleet maintenance spreadsheet needs a unit list with VIN, year, make, model and current miles or hours, a PM schedule by miles, hours or months, a work history, DVIR defects with repair certification dates, annual inspection due dates, and parts and tires. Formulas flag what's due, and one person keeps it current.

A fleet maintenance spreadsheet needs a unit list with one row for every truck, trailer and machine, plus tabs for the PM schedule, work history, DVIR defects, annual inspection dates, and parts and tires. Formulas work out when each PM and each annual inspection comes due, and colors flag what's overdue. Start with our free template, give it one owner, and move to software when the spreadsheet starts missing PMs or losing records.

This guide is for fleets that maintain their own trucks and equipment with their own techs, and for repair shops that track their fleet customers' units. Federal rule text comes from the eCFR as of November 19, 2026. It's general information, not legal advice, so check the current rule for your operation.

Free Excel template

Fleet Maintenance Spreadsheet Template

A tab for each list in this guide, with example rows, drop-down lists, formulas for the next PM and the next annual inspection, and red and amber rows for what's overdue or due soon.

No spam. Just the occasional guide for repair shops and fleets.

What federal rules expect you to keep

For trucks under Part 396, the rules set the floor. For each vehicle a carrier controls for 30 consecutive days, it keeps records that include these three (49 CFR 396.3(b)):

  • An identification of the vehicle: "company number, if so marked, make, serial number, and year," plus who furnished it if the carrier doesn't own 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."

Those three map to the first three tabs below. For who owns which record when a shop does the work, see 49 CFR Part 396 explained for repair shops. Whether a unit falls under these rules depends on whether it's a commercial motor vehicle. Track your machines the same way either way, because they need PM too.

The tabs and columns that matter

1. Units

One row per unit. Everything else in the file points back to the unit number, so use the same one everywhere.

ColumnsWhat goes in them
Unit #, VIN or serial #, year, make, modelHow you identify the unit. Use the number painted on it.
Unit type and meterTractor, straight truck, trailer, reefer unit or machine. Miles or hours.
Current reading and reading dateThe odometer or hour meter, updated every week
StatusIn service, out of service, or sold or returned
Owned byWho furnished it, if it's leased or rented
Date it left the fleetStarts the clock on how long you keep its records

2. PM schedule

One row per PM level per unit. A tractor might have rows for PM A, B and C. A machine might have a 250-hour service. Set each PM interval from the makers' schedules, by miles, engine hours or months, whichever comes first. The guide to PM A, B and C covers what goes in each level and how to set intervals.

ColumnsWhat goes in them
Unit #, PM serviceWhich unit, and which PM level
Every (miles or hours), every (months)The interval. Fill in one or both.
Last done date and readingWhen the last one was done, and the reading at the time
Next due at, next due byFormulas: the next reading and the next date
Left, days left, statusFormulas: what's left, and OVERDUE, DUE SOON or OK

3. Work history

One row per job, from the repair order. This is the "date and nature" record, so write what was done in plain words. The days-down column shows how long each job kept the unit off the road, and the guide to cutting truck downtime covers how to shrink it.

ColumnsWhat goes in them
Date in, date out, unit #, readingWhen it came in, when it went back out, and the miles or hours
Work order #, typePM, repair, DVIR repair, annual inspection, road call, tires or warranty
Complaint, cause, correctionThe problem, what the tech found and what fixed it: the 3 Cs
Parts used, labor hours, done byWhat went on the truck, how long it took, and which tech or shop
Comeback?, days downWhether it came back for the same problem, and a formula for days out of service

Maintenance records are kept 1 year, and for 6 months after the vehicle leaves the carrier's control (396.3(c)). The glossary has every DOT record retention period in one place.

4. DVIR defects

One row per defect a driver writes up. The point of the tab is that no defect sits open with nobody sure whether the truck can run.

ColumnsWhat goes in them
Report date, unit #, driver, defectThe defect as the driver wrote it
Affects safe operation?, actionYes, no or not sure. Repaired, repair unnecessary or waiting on parts.
Certified by, certified on, work order #Who signed the repair certification on the DVIR, and when
Next driver reviewed on, keep untilThe driver's review date, and a formula for 3 months from the report date

The DVIR, the repair certification and the driver's review are kept three months from the date the report was prepared (396.11(a)(4)). For what has to be fixed before the truck runs and how to word the certification, see DVIR rules and certifying repairs.

5. Annual inspections

One row per unit, trailers and converter dollies included, since each needs its own (396.17(a)). A unit must have passed an inspection "at least once during the preceding 12 months," with proof on the vehicle (396.17(c)).

ColumnsWhat goes in them
Unit #, last annual, inspector, shopThe date on the report, and who did it where
Passed?, failed items fixed onThe result, and the repair date for anything that failed
Report or decal on the unit?Yes or no
12-month anniversary, days left, statusFormulas: book the next one before the anniversary
Keep report untilA formula for 14 months from the report date

The report is kept 14 months from the date of the inspection report (396.21(b)(1)). The DOT annual inspection checklist covers what gets inspected and who can sign.

6. Parts and tires

The parts tab tracks part number, description, which units it fits, where it's kept (bin, shelf or service truck), on hand, reorder point, order-up-to level and vendor. A formula flags REORDER when on hand drops to the reorder point. The tires tab tracks unit, position, size, install date and reading, last check date, tread depth and pressure.

The formulas that do the work

The template has these built in. If you build your own sheet, here's the logic in plain words:

  • Next PM by reading = last done reading + interval.
  • Next PM by date = last done date + interval in months. In Excel, the EDATE function does the month math: EDATE(last date, months).
  • PM status = OVERDUE if the current reading has passed the next due reading or today has passed the due date. DUE SOON inside a window you set, such as a number of days or a share of the interval.
  • Annual anniversary = last annual date + 12 months.
  • Keep until = the record date + 3 months for DVIRs, or + 14 months for annual reports.

Color the whole row red when it's overdue and amber when it's due soon, so the list reads at a glance.

How to keep it accurate

  • Give it one owner. One person updates it and answers for it. Everyone else reads.
  • Keep one file. Store it in one shared place. Emailed copies drift apart.
  • Update readings every week. A PM schedule by miles or hours is only as good as the last reading.
  • Log work the day it's done. Copy it from the repair order, not from memory.
  • Check the red and amber rows every Monday. Book what's due before it's overdue.
  • Lock the formula columns. One bad paste can break a column of due dates.
  • Back it up. If the file is your record, losing it means losing your records.

Signs it's time to move off the spreadsheet

  • A PM got missed because the reading wasn't updated or the one person who keeps the file was out.
  • Two people are editing two copies.
  • Techs write on paper and someone types it in later, or never.
  • Pulling one unit's history for an auditor or a fleet customer takes an afternoon.
  • DVIR defects sit open and nobody's sure whether the truck can run.
  • You buy parts you already had because nobody knows what's on the shelf or the service truck.
  • Fleet customers want to request work and approve repairs without calling you.

Two or three of those, and the spreadsheet is costing you more than it saves.

Where MetaFleet fits

MetaFleet runs the repair work for fleets that maintain their own trucks and equipment, and for shops that service fleet accounts. PM programs come due by miles, engine hours or months, with reminders and a PM history for each unit. Inspections run on your own forms, DVIR and annual inspection forms included, from any phone browser. Parts are tracked across warehouses, bins and service trucks, with purchase orders. If you service fleets, your customers request work and approve each repair from the customer portal. MetaFleet doesn't do telematics, GPS or fuel tracking, so keep your telematics for that. See MetaFleet for fleets with their own shop, inspections and PM and parts inventory.

Sources (4)

Rule text checked against the eCFR on November 19, 2026.

FAQs

A unit list with unit number, VIN, year, make, model and current miles or hours; a PM schedule with intervals and next due dates; a work history for every job; DVIR defects with repair certification dates; DOT annual inspection dates; and parts and tires. Use the same unit number on every tab so each one points back to the unit.
Give each PM row an interval in miles or hours, in months, or both. The next due reading is the last done reading plus the interval. The next due date is the last done date plus the months, which Excel's EDATE function works out. Whichever comes first sets the due date, so flag the row when either one passes.
Under Part 396, maintenance records are kept 1 year, and for 6 months after the vehicle leaves the carrier's control (49 CFR 396.3(c)). DVIRs, repair certifications and the driver's review are kept 3 months (396.11(a)(4)). Annual inspection reports are kept 14 months (396.21(b)(1)).
Keep one row per unit, trailers and converter dollies included, with the date of the last annual. Add 12 months to get the anniversary, since each unit must have passed an inspection within the preceding 12 months (49 CFR 396.17(c)). Flag rows that are close and book the next inspection before the anniversary.
When the spreadsheet starts to cost you: PMs missed because readings weren't updated, two people editing two copies, techs' paper notes typed in late, open DVIR defects nobody tracks, or a unit's history that takes an afternoon to pull. Software keeps the schedule, the history and the parts in one place everyone works from.

Ready to move your fleet off the spreadsheet?

See MetaFleet in Action

Book a demo and we'll walk through how you track units, PMs and inspections today, show you where MetaFleet fits, and build a simple rollout plan your team can follow.

Not ready to talk? Try a free shop tool

Related Articles