This fleet preventive maintenance schedule Excel file is a free Excel template for planning recurring vehicle service in 2026. It organizes manually maintained vehicle, odometer, and completed-service information across the Dashboard, Vehicles, PM Schedule, and Settings sheets.
Enter fleet details and regularly update Current Odometer (Miles), odometer update dates, and completed-service baselines. Excel then compares mileage and calendar intervals with the selected Report Date. The populated rows near the top contain sample records for understanding the layout. Replace or remove those examples before using the remaining prepared rows for your operation. Calculations depend on accurate manual entries and Excel recalculation.
In practice
What this workbook helps you do
- ✓See overdue, due-soon, up-to-date, and review-required task counts in one summary.
- ✓Plan recurring service using both mileage intervals and calendar-month intervals.
- ✓Connect each preventive maintenance task to a vehicle record through its Unit ID.
- ✓Compare estimated costs for tasks currently classified as Overdue or Due Soon.
Instructions
How to use the file
Set the planning date and maintenance thresholds
Start on Settings. Enter the planning date in B4, the mileage threshold in B5, the day threshold in B6, and the stale-odometer threshold in B7. The Due Soon Thresholds determine how close a valid task can be to its mileage or date limit before it receives a Due Soon status. Maintain service types, default mileage intervals, month intervals, and estimated costs in A11:D110.
Replace the sample vehicle records
On Vehicles, rows 5 through 504 form the prepared operating range. The populated rows near the top are examples, while the unused rows are available for fleet records. Enter or replace the Unit ID, year, make, model, vehicle type, department, assigned driver, current odometer, odometer update date, and vehicle status. Each Unit ID should be unique. Vehicle type, department, and status fields use lists maintained on Settings.
Enter each preventive maintenance task
On PM Schedule, user-entry columns are A, B, E, F, G, R, S, and T. Enter a unique PM ID, select the Unit ID and service type, record the Last Service Date and last service odometer, and optionally add a service provider, work order or PO, and notes. Rows 5 through 504 are prepared. Sample tasks appear near the top, and blank operating rows remain available below them.
Review calculated fields and dashboard results
Columns C, D, and H through Q on PM Schedule contain formulas for all 500 prepared rows. They return the vehicle description and status, service intervals, current odometer, next due odometer, next due date, miles remaining, days remaining, Data Check, Status, and estimated cost. Do not replace these formula cells with manual values. After work is completed, update the last service date and last service odometer manually. Then review Dashboard totals, the status chart, estimated costs, and data-quality checks.
Inside the file
Included features
Review preventive maintenance priorities on the Dashboard
The Dashboard summarizes total vehicles and PM tasks, then separates schedule rows into Overdue, Due Soon, Up to Date, and Review categories. Its chart plots task counts for those four categories.
Estimated Cost Needing Attention adds the service-type estimates for Overdue and Due Soon rows. Attention Rate divides those same two task counts by the total populated PM task count. These are planning figures based on Settings values, not invoices or booked accounting expenses.
Additional checks report odometer updates older than the allowed threshold, schedule rows with data issues, duplicate Unit IDs, and duplicate PM IDs. Duplicate and data-issue counts should normally be zero and should be reviewed before relying on the planning results.
Maintain current vehicle and odometer information
The Vehicles sheet is the source for vehicle identity, current mileage, odometer update date, and operating status. PM Schedule formulas use the selected Unit ID to retrieve the year, make, model, vehicle status, and current odometer.
Validation is configured for model years from 1990 through 2100, odometers from 0 through 2,000,000 miles, and odometer update dates from January 1, 2000 through the report date. The stale-update setting provides an operational reminder when an entered update date is too old. Mileage and update dates must still be entered manually.
Calculate service timing by mileage and calendar date
For mileage-based planning, Next Due Odometer equals the last service odometer plus the service interval. Miles Remaining compares that result with the vehicle's current odometer. For calendar planning, Next Due Date adds the configured number of months to the last service date, and Days Remaining compares it with the report date.
A valid row becomes Overdue when an enabled mileage or month interval has passed. It becomes Due Soon when an enabled interval falls within the configured mileage or day window. Otherwise, it is Up to Date. Any row whose Data Check is not OK receives Review instead of a maintenance timing status.
Configure service types, costs, and operating lists
Settings provides a service-type table from rows 11 through 110. Each entry can carry a default interval in miles, a default interval in months, and an estimated cost in U.S. dollars. PM Schedule retrieves these values from the selected service type.
The same sheet contains source lists for departments, vehicle statuses, service providers, and vehicle types. Editing those lists changes the choices offered by the related validated fields. The supplied entries are editable planning data rather than required classifications.
Common questions
About this workbook
Yes. Each PM Schedule row has its own PM ID, Unit ID, and service type. A vehicle can therefore have separate rows for different recurring services. Keep every PM ID unique and select a Unit ID that exists on Vehicles.
If the linked vehicle status is Out of Service or Sold, the schedule's Data Check returns Inactive Vehicle. Because the data check is not OK, the task status becomes Review rather than Overdue, Due Soon, or Up to Date.
Yes. A service type may have zero in one interval field and a positive value in the other. The corresponding unused next-due calculation remains blank. However, the schedule's data check expects both a last service date and a last service odometer as the completed-service baseline.
PM IDs have duplicate-check validation, Unit IDs and service types use source lists, service dates run from January 1, 2000 through the report date, and service odometers accept whole numbers from 0 through 2,000,000. Work Order / PO entries are limited to 80 characters, and Notes entries are limited to 500 characters.
No. Current odometers, odometer update dates, and completed-service details are maintained manually. The formulas calculate planning outputs from those entries, but the file does not provide telemetry or other automatic data collection.
No. It is a manually maintained planning workbook and does not replace accounting records or legal, tax, DOT/FMCSA, safety, or compliance advice. Review source documents, completed work, vehicle condition, and applicable requirements separately.
Editorial team
Prepared and checked with care
Casey Morgan
Fleet operations editorCasey turns dispatch, driver, vehicle, and delivery workflows into clear workbook guides.
About the editorial identities
Jordan Lee
Workbook quality editorJordan documents the automated formula, recalculation, download, and usability checks applied before publication.
About the editorial identities