Scan Reports: What They Actually Prove, and What They Do Not
Short answer: a clean dashboard proves nothing, most faults never light a lamp. You are owed a pre-repair scan (the baseline that separates crash damage from repair damage) and a post-repair scan showing systems healthy on their own account, not merely cleared. And a scan is not a calibration: one reads status, the other aims a sensor, a camera can pass every scan while looking the wrong way. If glass, a bumper, a mirror or suspension was touched, ask for both documents.
A modern vehicle carries dozens of networked control modules. After a collision, some of them know things that no warning light will tell you: a fault stored during the impact, a sensor reporting out of range, a module that lost communication and never re-established it.
A diagnostic scan interrogates those modules and reports what they hold. It has become standard practice to scan before repair and again after, and most manufacturers now publish position statements saying so, though not all of them say the same thing: twelve require both scans and three only recommend one. It is also one of the most misunderstood documents you will be handed.
Why the dashboard is not evidence
The instrument cluster shows a small, curated subset of faults, chosen by the manufacturer as things a driver should act on immediately. A great deal never surfaces there.
Stored and pending codes, faults in systems with no dedicated warning lamp, calibration status flags, and modules that simply stopped responding can all sit in the network with a completely clean dash. "No lights on" tells you the car is not currently demanding attention. It does not tell you the electronics came through the crash intact.
Pre-repair versus post-repair, and why both
The pre-repair scan establishes what was wrong before anyone touched the vehicle. It informs the repair plan, catches damage that is invisible from outside, and, importantly for you, creates a baseline. Without it there is no way to distinguish a fault caused by the collision from one caused by the repair.
The post-repair scan confirms the network is healthy at handover: faults resolved rather than merely cleared, modules communicating, calibrations reporting complete.
The pre-repair scan is the one most often skipped, because it costs time before the work has been authorised. It is also the one that protects you most.
Clearing a code is not fixing a fault
This is the distinction that matters most, and the easiest one to be reassured past.
Any scan tool can erase stored codes. The lamp goes out and the report comes back clean. If the underlying condition still exists the code returns: sometimes immediately, sometimes after a specific drive cycle, sometimes weeks later when the right conditions recur.
A scan report showing no faults after codes were cleared and before the vehicle was driven proves very little. What you want is a post-repair scan performed after the repair is complete, showing the systems reporting healthy on their own account.
If someone tells you "we cleared the codes and the light stayed off," that is a description of a symptom, not a diagnosis.
A scan is not a calibration
These get conflated constantly, and they are different operations.
A scan reads status. A calibration aims a sensor: physically and in software: so the vehicle knows where that sensor is pointing. A camera can pass a scan with no fault codes at all while being aimed incorrectly, because nothing is broken; it is simply looking somewhere slightly wrong.
So a clean scan does not mean calibration was performed, and a scan report is not a substitute for a calibration record. If your repair involved a windshield, bumper cover, grille, mirror, or suspension work, you should receive both.
OEM tools versus aftermarket tools
Scan tools are not equivalent. The manufacturer's own diagnostic software generally reaches every module and every code; aftermarket multi-brand tools vary in coverage, and some read the main systems while missing modules or code types entirely.
This matters because a scan is only as complete as the tool that performed it. A report generated by a tool with partial coverage can be entirely truthful and still miss the fault. Manufacturer position statements increasingly specify OEM-level scanning for exactly this reason, and eight of the fifteen name one tool and say it is the only one they will stand behind.
You do not need to audit the tooling. You do want to know that the shop has an answer when asked what they scanned with.
What you should receive
For a repair on a modern vehicle, the documentation set is:
- Pre-repair scan report: dated before work began, listing what was found.
- Post-repair scan report: dated at completion, showing systems healthy.
- Calibration records for any sensor system that required it, showing the procedure performed and its pass status.
- The repair order reflecting the scans as performed operations.
These should be handed over without you having to ask twice, and it is far easier to obtain them before you accept the vehicle than after.
What a scan report does not tell you
Being honest about the limits, because that is the point of this registry:
A scan reports what the modules say about themselves. It does not confirm that a repair was performed to the manufacturer's procedure, that the correct parts were used, that corrosion protection was restored, or that the structure was returned to specification. A clean network is necessary and it is not sufficient.
The scan is one document among several. Ask for the set.
General consumer information. Scanning requirements, position statements and tool coverage vary by manufacturer and model year.
After a crash: the complete walkthrough · ADAS calibration explained · Estimate line items decoded
General consumer information: not legal, insurance, or financial advice. Requirements, coverage, and practices vary by state, policy, and manufacturer.
Where this fits
Each link says what it is for. We add one only when a reader on this page has a real reason to need that page next.
- ADAS Calibration Explained: Why Your Car Needs It After Repairs (what the codes are pointing at)
- When Insurance Won't Pay for a Proper Repair: ADAS, OEM Procedures, and Your Options (using the scan as evidence in a refused-procedure dispute)
- Estimate Line Items Decoded: Labour Types, Part Codes and the Operations People Miss (how scan and calibration appear on the estimate)
- Pre and Post Repair Scanning: What Fifteen Manufacturers Actually Require (which manufacturers actually require the scan you are holding, and which only recommend it)
- Montana Bans Paying DRP and Non-DRP Shops Differently. Whether You Can Sue Over It Is a Separate Question. (what one state regulator said when an insurer paid for the scan at its own network shop and refused it at an independent)
- Who Requires the Scan (If the scan is being argued about, this is who actually requires it and who never agreed to pay.)