Fleet management in Excel: a vehicle, fuel and maintenance template that works, where it breaks, and what replaces it
Small fleets almost always run on fleet management in Excel. A vehicle list, a fuel log, a sheet of service dates, a folder of inspection forms. For a handful of vans and one person looking after them, a good spreadsheet is enough — and honestly more useful than a lot of software that leads with a live map.
Then the fleet grows past a dozen vehicles, drivers start submitting their own readings, a van goes out with a fault somebody reported on paper, and the spreadsheet stops being trustworthy. It stops in the same five places every time.
This is the honest version: a fleet maintenance spreadsheet structure that is worth copying, exactly where each part of it fails, and what your options are when it does.
The fleet spreadsheet worth copying
Most free fleet management Excel templates are one sheet per vehicle with a mixture of fuel, services and notes in whatever order they were typed. You can read one vehicle's history, but you cannot ask a single question across the fleet. Start with five sheets, one per kind of event.
Sheet 1 — Vehicles. One row per vehicle. No mileage here; mileage comes from the logs.
| Unit | Registration | Make / model | Year | Status | Assigned driver |
|---|---|---|---|---|---|
| V-07 | KX21 ABC | Ford Transit 350 | 2021 | In service | M. Qureshi |
| V-11 | LM22 DEF | Vauxhall Vivaro | 2022 | Off road | — |
Sheet 2 — Fuel log. One row per fill, always with the odometer reading.
| Date | Unit | Odometer | Litres | Cost | Full tank? | Driver |
|---|---|---|---|---|---|---|
| 2026-09-02 | V-07 | 48,210 | 62.0 | 91.14 | Yes | M. Qureshi |
| 2026-09-09 | V-07 | 48,780 | 58.5 | 86.00 | Yes | M. Qureshi |
Fuel economy is the distance between two full fills divided by the fuel added at the second one — 570 km on 58.5 litres here. That is why the odometer column is not optional. A fuel entry without an odometer reading cannot produce a consumption figure, and a lot of fleet tools, and a lot of AI-built ones, fill that gap with an estimate.
Sheet 3 — Maintenance schedule. One row per vehicle per recurring service, with an interval in both distance and time.
| Unit | Service | Every (km) | Every (days) | Last done (date) | Last done (km) |
|---|---|---|---|---|---|
| V-07 | Oil and filter | 15,000 | 365 | 2026-03-18 | 40,100 |
| V-07 | Brake inspection | 30,000 | 730 | 2025-11-02 | 35,600 |
Next due is whichever comes first:
Due by date = [@Last done date] + [@Every days]
Due by km = [@Last done km] + [@Every km]
Current km = MAXIFS(Fuel[Odometer], Fuel[Unit], [@Unit])
Overdue = OR(TODAY() >= [@Due by date], [@Current km] >= [@Due by km])
Sheet 4 — Service history. One row per job actually done, never edited afterwards.
| Date | Unit | Odometer | Work | Cost | Vendor |
|---|---|---|---|---|---|
| 2026-03-18 | V-07 | 40,100 | Oil and filter | 145.00 | Main Street Garage |
Sheet 5 — Inspections and defects. One row per failed item on a check, with a status.
| Date | Unit | Driver | Item | Defect status |
|---|---|---|---|---|
| 2026-09-14 | V-07 | M. Qureshi | Nearside brake light out | Open |
Cost per mile (or per km) then comes from these logs: total fuel and service spend for a period, divided by the distance driven in that period — the last odometer reading minus the first. Not divided by the odometer itself; that mistake, surprisingly common, makes a van look like it costs a fraction of a penny to run.
That is the whole structure, and the principle underneath it is simple: mileage, consumption, next-due and cost are all derived from dated events. Nobody types a "current mileage" or a "next service" by hand.
Where it breaks
1. The readings come in late, and wrong
Everything above hangs off odometer readings, and those come from drivers — on a fuel receipt, a WhatsApp photo, a note at the end of the week. Some arrive days late, some are missed, and some are typos that put a van 10,000 km into the future. One bad reading and the consumption figure jumps, the maintenance schedule says a service is due tomorrow, and nobody believes the sheet any more.
2. The schedule only advances if someone remembers
The next-due formula works as long as Last done is updated after every service. When a van comes back from the garage and nobody updates the schedule, the service stays overdue forever or, worse, somebody updates the date but not the odometer and it looks fine for another year. A maintenance schedule in a spreadsheet is a to-do list that depends on the person who ticks it.
3. A failed inspection doesn't stop the van
This is the failure that matters most. A driver's pre-trip check finds a faulty brake light, and it gets written on a form or typed into Sheet 5 as Open. Nothing about that row takes the van out of service. Nobody is assigned to fix it. The next driver takes the van out anyway. In a real fleet system, a failed safety item raises a defect, the defect blocks the vehicle from being assigned, and a work order carries it back to in service once it is fixed. A spreadsheet records the problem and does nothing with it.
4. Costs live in five other places
Fuel is on the fuel card statement. Repairs are on garage invoices. Tyres were bought on a company card. Insurance and tax are annual. To get a true cost per vehicle, someone copies all of that into the sheet, and the copy is always incomplete. The cost-per-mile figure then looks healthy precisely because half the cost is missing.
5. Drivers, a yard and a phone
Drivers do not use spreadsheets at the pump or in the yard. They need a single, fast form on a phone: vehicle, odometer, litres, done. Give them the shared file instead and they either don't submit, or they edit each other's rows, or they see the whole fleet's records when they only need their own van.
What a real one has that a spreadsheet doesn't
We keep a hand-counted inventory of what fleet management products actually ship, built from 60 products. The top of the list and the parts that matter most for the failures above:
| Capability | Products (of 60) |
|---|---|
| Fuel management and consumption | 41 |
| Dashboards and reports that drill to source rows | 41 |
| Vehicle and asset inventory | 40 |
| Preventive maintenance schedules | 40 |
| Driver mobile app and field capture | 32 |
| Digital inspections and checklists | 31 |
| Expenses, cost per mile and total cost of ownership | 31 |
| Live GPS map and vehicle location | 30 |
| Service and repair history | 20 |
| Work orders and repair execution | 18 |
| Defect, fault and issue management | 14 |
Two things are worth noticing. The top four — fuel, reports, the vehicle register and maintenance schedules — are exactly the sheets above. A well-built spreadsheet covers the most common capabilities in the category surprisingly well.
The bottom three are the chain that fixes failure 3: an inspection raises a defect, the defect becomes a work order, and the work order returns the vehicle to service and writes the repair history. Only 14 to 20 of 60 products document those links publicly, because marketing leads with maps and dashboards. They are still the mechanism that keeps an unsafe van off the road. And notice the live map, at 30 of 60, is common but not universal: a fleet system can be complete without one.
Your three options, honestly
Keep the fleet spreadsheet
Correct for a small fleet — up to a dozen or so vehicles, one person responsible, drivers who hand in readings reliably. Use the five sheets above, check the overdue column weekly, and treat an open defect as a reason to keep the van in the yard, whatever the sheet says.
Stop when readings stop arriving on time, when a vehicle goes out with a known fault, or when you cannot say what a van actually costs to run.
Buy software
Correct for most fleets past that size. Fleet software gives drivers a phone form, advances maintenance schedules on its own, and connects inspections to repairs. If you run regulated vehicles — hours of service, tachographs, fuel-tax reporting — buying is usually the right answer, because those rules are jurisdiction-specific and change.
The real cost is fit. Many products are built around GPS tracking and priced per vehicle per month for it. If what you actually need is inspections, maintenance and cost, check you are not paying for a map you will rarely open.
Build it
A coding agent can now build a working fleet system in days, and the risk is the one described in our guide to building a fleet management system: it builds the live map first, because that is the most photographed screen in the category, and improvises the rest. When four AI models built the same fleet spec, the lowest-scoring build accepted a fuel reading and threw away the litres and the odometer, and stored costs with no amount at all — exactly the fields a well-built spreadsheet keeps without any trouble.
If you build it, build these first
- The vehicle register as the centre, with each vehicle's status, driver and full history on one record.
- Dated logs for fuel and odometer, with every consumption and cost figure derived from them.
- Maintenance intervals in distance and time whose next-due recomputes when a job is completed.
- The inspection → defect → work order chain, where a failed safety item takes the vehicle out of service until the work order closes it.
- A fast driver form on a phone that shows each driver their own vehicle and nothing else.
Dispatch, GPS tracking, parts inventory and regulated compliance are real scope, and optional for a first version unless your operation requires them.
If you are building with a coding agent, the Fleet Management planner is the spec we hand ours: the vehicle as the core object, the readiness gate and the inspection-to-repair chain, written so the agent cannot quietly skip them.