Maintenance Records & Work Orders · Excel template
Free ADAS Calibration Record
A per-vehicle record of every ADAS calibration — what triggered it, static or dynamic, the pre- and post-scan results, and who signed it off.
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
- One row per calibration with the trigger event, so a windshield replacement and a collision repair are not filed as the same thing
- A static-or-dynamic field, plus the bay conditions a static calibration depends on
- Pre-scan and post-scan fault-code columns, which is the pair that evidences the work actually cleared
- The tool, software version and OEM procedure reference used — the detail that makes the record defensible later
- A road-test verification column for dynamic calibrations
- A technician sign-off and date, and a field for any system left uncalibrated and why
How to use it
- 1
Log the trigger before the work starts: glass replacement, camera or radar removal and refitting, alignment or ride-height change, suspension work, or collision repair.
- 2
Run and record a pre-repair scan. Without the before state there is no way to show afterwards which faults the calibration resolved and which were already present.
- 3
Record whether the OEM procedure calls for static calibration, dynamic calibration, or both for that system on that vehicle — it varies by manufacturer, system and model year, so take it from the service information rather than from habit.
- 4
For a static calibration, note the bay conditions the procedure specifies and whether they were met; for a dynamic one, note the road-test conditions and the distance or duration completed.
- 5
Record the post-calibration scan, the tool and software version used, and the OEM procedure or bulletin reference.
- 6
Have the technician sign and date the row, and list explicitly any system that could not be calibrated and the reason — an unfinished calibration left undocumented is the one that surfaces after an incident.
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
ADAS Calibration Record
Which systems need calibration, whether the procedure is static or dynamic, and the bay or road conditions it requires are set by the vehicle manufacturer and differ by make, model and year. Take every procedure from the OEM service information for the specific vehicle. The values below are illustrative of the record's shape, not of any manufacturer's requirement.
| Date | Unit / VIN | Trigger event | System(s) | Static / dynamic | Pre-scan faults | Post-scan faults | Tool / software version | Verified by |
|---|---|---|---|---|---|---|---|---|
| 2026-04-02 | TRK-112 | Windshield replacement | Forward camera (LDW, AEB) | Static | 2 stored | 0 | Scan tool v4.18.2 | D. Okafor |
| 2026-04-15 | VAN-031 | Front-end collision repair | Front radar, forward camera | Static + dynamic | 5 stored | 0 | Scan tool v4.18.2 | D. Okafor |
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.
The triggers that come up most in fleet work are windshield or glass replacement where a camera is mounted to it, removal and refitting of a camera or radar, collision repair to a panel carrying a sensor, and anything that changes the vehicle's attitude or sensor aim — alignment, ride height, suspension work. Whether a given job on a given vehicle requires calibration is an OEM determination though, not a general rule, so the service information for that make, model and year is the authority rather than a generic trigger list.
Static calibration is done stationary in a bay, with targets positioned at measured distances in front of the vehicle. Dynamic calibration is done by driving the vehicle under specified conditions while the system learns. Some systems require one, some the other, and some both in sequence. Which applies is set by the manufacturer for that system on that vehicle, so the record should capture what the procedure called for rather than what the shop usually does.
Because without it you cannot separate faults the calibration fixed from faults that were already stored. A post-scan showing zero codes proves very little on its own; a pre-scan showing two stored faults and a post-scan showing none is a record of work done. It also protects the shop when a fault unrelated to the calibration is found afterwards — the pre-scan shows it was there first.
A work order records that a job was done and what it cost. A calibration record captures the things a work order line almost never does: which system, static or dynamic, the conditions, the tool and software version, and the before-and-after fault state. That detail matters disproportionately because ADAS work gets questioned after an incident rather than at the time, often years later and by someone who was not there.
That depends on the manufacturer's requirements, the equipment the procedure needs, and in some cases the bay itself — static calibrations typically specify floor, lighting and clearance conditions a general service bay may not meet. Treat the question as one to settle per OEM procedure and per site rather than per technician, and record which site and equipment were used so the answer is on file.
Related guides & tools
Looking for more? Browse all fleet templates or run a fleet calculator.