Free checklist · EV readiness

EV Software Update Checklist

Covers OTA update status, workshop update process, diagnostic logs, customer consent, update verification, rollback process, and record keeping.

  • 15 checks
  • 4 categories
  • PDF, 10 pages
  • Updated October 2026
  • 15checks to score
  • 4categories
  • 75points, scored 1–5 each
  • 10page PDF, free

What this checklist covers

The EV Software Update Checklist is a 15-point scorecard for OTA update status, workshop update process, diagnostic logs, customer consent, update verification, and record keeping. Each criterion is scored from 1 to 5 on what the auditor sees on the day, and every gap goes into an action plan with an owner and a close date.

AutoSmart tip: EV software update audits should verify version confirmation, not only update initiation. A common failure is that the update process was started, interrupted (network drop, vehicle power state change), and marked as complete on the job card without the technician confirming that all modules were successfully updated to the target version. Always verify the installed version number against the target version in the OEM update portal after completion.

The checks

Tap Yes, No or Maybe to try it: your answers stay in this page and clear when you refresh. For a detailed walkthrough, download our PDF or book a demo.

Ota update status and customer consent

4 checks

  • Is the OTA (over-the-air) update status checked for every EV entering the workshop, confirming whether pending updates should be applied before or after the service?
  • Is customer consent obtained before applying any software update that changes vehicle behaviour, appearance of the user interface, or feature availability?
  • Are customers informed of what a pending update contains — particularly if it affects range reporting, charging behaviour, or driver assistance system calibration — before they are asked to consent?
  • Is the customer informed if an OEM-mandated update (safety-related or required for warranty compliance) must be applied during the current workshop visit?

Workshop update process

4 checks

  • Is the workshop software update process documented — covering preparation steps, network connectivity requirement, update initiation, vehicle state requirements (charge level, ignition status), and completion verification?
  • Are workshop-applied software updates performed using the OEM diagnostic tool and update portal, not through unofficial channels or third-party software?
  • Is the vehicle confirmed as stationary, with handbrake applied and in the correct power state, before any software update is initiated — per the OEM update procedure?
  • Are software updates applied by technicians trained on the OEM update process for the specific model, not by any staff member with access to the diagnostic tool?

Update verification and rollback

3 checks

  • Is the software version verified as correct after update completion — confirming the update was applied to all modules as intended, not just initiated?
  • Is a post-update functional check performed, confirming no new fault codes, warning lights, or feature anomalies are present before the vehicle is returned to the customer?
  • Is a rollback or recovery process understood and documented for scenarios where an update fails mid-process, leaving the vehicle in an incomplete software state?

Diagnostic logs and record keeping

4 checks

  • Is the pre-update software version and post- update software version recorded on the job card for every software update performed in the workshop?
  • Are diagnostic logs from the update session retained and attached to the job card, providing a retrievable record of the update process for warranty or technical investigation purposes?
  • Is software update history for each vehicle visible in the DMS, allowing future service visits to confirm what versions are installed without re-scanning the vehicle from scratch?
  • Are failed or incomplete update attempts logged as a service event and reported to the OEM technical support channel, rather than only noted informally by the technician?

How to run it

How the scoring works

Before the visit, fill in the dealer or centre, the auditor, the date and the audit cycle. Then score each of the 15 checks from 1 to 5 on what you see on the day, not on what the site aims for, and add them up out of 75.

  1. 1Not in place
  2. 2Attempted
  3. 3Defined
  4. 4Managed
  5. 5Fully sustained
  • Green60–75 · 80–100%Compliant. Keep the standard.
  • Amber38–59 · 50–79%Improvement needed: a structured action plan within 30 days.
  • Red0–37 · Below 50%Priority intervention, escalated to regional management.

Then close every gap

Each gap goes into the action plan tracker and moves through four stages until the auditor closes it.

  1. 1PendingOwner and close date set
  2. 2In progressWork under way, evidence gathered
  3. 3CompletedEvidence submitted for review
  4. 4ApprovedVerified and closed by the auditor

Free download

Get the EV Software Update Checklist as a PDF

10-page PDF, ready to print or fill in on a tablet. Free: enter your email and it downloads.

  • Part 1ScorecardAll 15 checks, each with 1–5 score circles and a notes column.
  • Part 2Category summary and sign-offTotals per category, the Green, Amber or Red result, and signatures from the auditor and the manager.
  • Part 3Action plan trackerEvery gap with an owner and a close date, moved from pending to approved.

From checklist to live audit

Run ev readiness audits across your network

Book a demo and we’ll show this checklist running in AutoSmart: on mobile, offline, with photo evidence and an owner for every failed check.

  • Unlimited users and checklists
  • Works offline