EV Fleet · Excel template
Free EV Charger Maintenance Log
A per-charger record of faults, uptime, and service history for depot charging infrastructure — the log that separates a charger problem from a vehicle problem.
Built and reviewed by the FleetOpsClub research team. Preview it free below. Enter your name and email to unlock the full template and the editable spreadsheet — a CSV that opens in Excel, Google Sheets, or Numbers.
- Editable CSV — yours to keep
- Print or save as PDF
- No spam · unsubscribe anytime
What you get
- A charger inventory with location, connector type, and rated output
- A fault log capturing what happened, when, and how it was resolved
- An uptime tracker so a chronically unreliable charger is visible before it becomes the excuse for a missed route
- A firmware and service-visit history per unit
- A cross-reference field linking a fault to the vehicle that was charging when it occurred
How to use it
- 1
Inventory every charger with a fixed ID, location, and connector type before logging anything against it — a fault reported as 'the charger by the fence' doesn't scale past a handful of units.
- 2
Log every fault as it's reported, including ones that resolve themselves, since a charger that self-resolves five times a month is not actually reliable.
- 3
Calculate uptime per charger per month rather than relying on impression — the one everyone complains about and the one that's actually failing most are not always the same unit.
- 4
Record firmware updates and service visits against the specific charger, so a recurring fault can be checked against what changed and when.
- 5
Cross-reference a fault against the vehicle charging at the time; a pattern of faults tied to one vehicle points at the vehicle's onboard charger, not the depot hardware.
Preview the template
Here's a real sample of the layout — the actual columns and structure you'll work in. The complete template, plus the editable spreadsheet, unlocks the moment you enter your email.
Preview
EV Charger Maintenance Log
Charger diagnostics and fault codes differ by manufacturer. Log the fault in plain language here even when a proprietary code is also available, so the record stays usable if you switch charging-network providers.
| Charger ID | Location | Date | Fault / Event | Vehicle Charging | Resolution | Downtime |
|---|---|---|---|---|---|---|
| DC-02 | Bay 2, east wall | 2026-03-11 | Connector fault, session would not start | EV-101 | Reset unit, session started | 0.4 hrs |
| L2-05 | Row C, spot 5 | 2026-03-19 | Charging stopped at 60% | EV-104 | Vendor ticket raised | 6 hrs |
Free unlock
Unlock the full template
Enter your name and email to reveal the complete template and download the editable spreadsheet. You can print it, save it as a PDF, or adapt the columns to your own vehicles. It's a fair trade: the preview costs nothing, and the full file costs you about 20 seconds.
- Editable CSV
- Every row & section
- Branded PDF
Frequently asked questions
Quick answers to the questions buyers usually ask once the category, software, or rollout details start getting more specific.
Fault count tells you how often something went wrong; uptime tells you how much charging capacity you actually had. A charger with three short faults and a charger with one long outage can log the same fault count but very different amounts of lost capacity — calculate downtime hours per fault, not just an incident tally, if you want the number that predicts a missed route.
Because a fault can originate on either side of the connector, and the log is how you tell which. If the same connector faults with multiple different vehicles, the charger is the problem; if faults cluster around one vehicle across multiple chargers, the vehicle's onboard charging system is worth inspecting instead — without the cross-reference, both patterns look identical from the fault log alone.
Yes — an update is a change to the unit's behaviour whether or not a fault triggered it, and it's the first thing worth checking when a new fault pattern appears afterward. A recurring fault that starts the week after a firmware push is a strong lead; without the update logged, that connection is invisible.
Anything where the session didn't complete as expected — stopped early, wouldn't start, delivered a lower rate than the unit's rating — even if a retry succeeded. A charger that intermittently needs a second attempt is degrading, and the only way to see that trend is if the first, seemingly minor, failed attempts are in the log.
Related guides & tools
Looking for more? Browse all fleet templates or run a fleet calculator.