How to Verify a Calibration Was Actually Done
The short answer
- Ask for three documents before you pay: a pre-scan report, a post-scan report and a calibration completion record naming the systems that were calibrated.
- A post-scan with no fault codes is not proof of calibration. It only shows the network is quiet, which it can be on a car nobody ever aimed.
- The completion record should name features in words (lane keeping, forward collision warning, adaptive cruise), not just say ADAS calibration complete.
- If any part of the job was dynamic, ask for a road test note stating road type, speed range, weather and light, plus confirmation the module reported the learn complete.
- Run your own checks in the first week: a straight marked road driven both directions with lane centering on, the washers to trigger the rain sensor, and the adaptive cruise gap you always use.
- Never test automatic emergency braking yourself. Aim errors show up in scenarios you cannot stage safely.
Ask for three documents before you pay: a pre-scan report, a post-scan report, and a calibration completion record that names your vehicle, the procedure performed and the specific systems that were calibrated. If any part of the job was dynamic, a road test note belongs with them. Those pages are the only evidence you will ever have that the camera behind your new glass was re-aimed, and the moment to ask for them is while the car is still on the shop's ticket, not three months later.
The three documents that prove the work happened
A calibration is a software event. Nothing about it is visible on the finished car, which is why the paperwork carries all the weight, and each of the three parts answers a different question.
- The pre-scan. A diagnostic read of every module the tool can reach, taken before anyone touches the glass. If your blind spot module already had a stored fault, the pre-scan is what stops that becoming an argument later.
- The post-scan. The same read taken after the calibration is finished. It should show the ADAS modules clear of stored and pending faults, and it should list the modules by name so you can see the forward camera was actually interrogated.
- The calibration completion record. The output from the calibration equipment itself, showing the procedure it ran and the result it reached. This is the document people mean when they say certificate, and it is the one most often missing.
Why any of this is required is covered in the calibration explainer, and the triggers after glass work are listed in when calibration is required. This page is about what you hold in your hand afterward.
How to read a scan report without being a technician
You are not looking for fault codes you can decode. You are looking for four structural things, and all four are visible to anyone.
- Your VIN, printed by the tool. A scan report generated from the car reads the VIN off the network. A VIN typed into a template by hand is a different kind of document. Check the last six characters against your dash.
- A module list, not a summary line. A real scan enumerates the control units it reached: engine, transmission, restraints, forward camera, radar, steering angle, and so on. A single page that says "no faults found" with nothing listed tells you nothing about whether the camera module was ever addressed.
- Two timestamps that make sense. The pre-scan should be stamped before the glass work and the post-scan after it, separated by the length of the job. Two reports stamped four minutes apart at the end of the day describe a paperwork exercise.
- Stored versus pending. Faults are recorded as current, stored (historic) or pending (seen once, not yet confirmed). A pending code in a camera module on a post-scan is not a pass. It usually means the module has already noticed something it does not like and is waiting for a second occurrence to set the light.
What each document proves, and what its absence means
| Document | What it should show | What it proves | If it is missing or vague |
|---|---|---|---|
| Pre-scan report | VIN, date and time, full module list, any faults present on arrival | The condition of your car before the job | You have no baseline. Any fault found later can be blamed on something that was there all along. |
| Post-scan report | Same VIN and module list, ADAS modules clear of stored and pending faults | The network is quiet after the work | A quiet dash is not evidence. Ask for the scan, not a verbal assurance. |
| Calibration completion record | Procedure type, systems calibrated by name, an explicit pass or complete result | The aiming procedure ran and finished | This is the gap that matters most. A post-scan alone does not show a calibration was attempted. |
| Road test note | Route or road type, speed range, weather and light, confirmation the learn completed | A dynamic procedure met its conditions | Dynamic work billed with no drive record is the easiest line to invoice and the hardest to verify. |
| Invoice line item | Calibration named separately from glass and labor, with the type stated | You were charged for a defined procedure | Calibration folded into a single total leaves nothing to dispute against. |
| Glass identification | Part description showing the camera bracket and sensor features your car needs | The right glass went in | A wrong or lower tier part is the most common reason a calibration will not hold. |
| Equipment identification | The scan or calibration system used, and who operated it | Someone specific stands behind the result | An unattributed record is hard to escalate on and hard to rely on years later. |
Why "ADAS calibration: complete" is not enough
Modern cars do not have one driver assistance system, they have a stack of features that share a camera. A record that names only the camera, or only the phrase ADAS, does not tell you which features were validated. Ask for the functions to be listed. In plain terms you want to see the ones your car actually has, described in words rather than a code:
- The forward camera itself, sometimes listed as a multipurpose camera, front sensing camera or similar. This is the module that gets aimed.
- Lane departure warning and lane keeping or lane centering, which are separate features on many cars.
- Forward collision warning and automatic emergency braking, including pedestrian detection where the car has it.
- Adaptive cruise control, which on most vehicles fuses the camera with a radar behind the grille. If the radar was disturbed, it has its own aiming procedure.
- Traffic sign recognition and automatic high beam control, the two features that most often reveal a small aim error to a driver.
Manufacturers brand these differently and your record will use your car's names, which is fine. What matters is that the list is longer than one line and matches the features the car came with. If the record names only a forward camera on a vehicle with adaptive cruise, ask what happened to the rest.
Get it in a form you can keep. A photograph of a screen on the shop's tablet is better than nothing, but ask for the file or a printout. This record has a second life at trade-in, on a lease return, and in any dispute about how a system behaved. Calibration, liability and your records covers how long to keep it and who asks for it.
The road test note, and what a real one says
Dynamic calibration is a drive under conditions the manufacturer defines: a speed band held steady, clear lane markings, adequate daylight, dry roads on most procedures, and on some systems a vehicle ahead to track. Those conditions are the whole procedure. A drive that does not meet them does not complete, and the difference between static and dynamic work is laid out in static versus dynamic calibration.
So a useful road test note records the conditions, not the mileage: road type, approximate speed range, weather and light, and a statement that the module reported the learn complete rather than the technician's opinion that it felt fine. Shops that take this seriously already have a form for it, because the same note protects them. One honest caveat: some vehicles complete a dynamic learn quietly over ordinary driving with no tool confirmation available, in which case the record should say exactly that.
Checks you can run yourself in the first week
Paperwork tells you what a machine reported. These tell you what your car does. Run them once in the first week, in daylight, on roads you already know, and write the date on the invoice.
- Read the dash on a cold start. Cycle through the driver assistance menu and confirm every feature shows as available rather than temporarily unavailable. Some cars only report camera status once moving, so check again after a mile.
- Wet the glass deliberately. Use the washers on a dry day and confirm the automatic wipers respond and then stop. The rain sensor sits in the same housing area as the camera and is disturbed by the same job: see the rain and light sensors behind the glass.
- Drive a straight, well marked road at steady speed. With lane centering on, note where the car sits in the lane. Then drive the same stretch in the opposite direction. A car that sits off center to the same side of the lane both ways is telling you something the paperwork will not.
- Set adaptive cruise to the follow gap you always use. The gap should feel like it always did. You are the instrument here, which is why the check works better in the first week than in the third month.
- Try automatic high beams on a road you know. They should drop for oncoming traffic at the distance they always did.
- Watch the speed limit display for a few days. Traffic sign recognition reading signs from a parallel road or a slip road is a small, specific clue.
Never test automatic emergency braking. Do not aim your car at anything to see whether it stops. AEB is validated by procedure and by scan data, not by experiment, and a system with a small aim error may perform normally in the one scenario you stage and badly in the one you meet by accident. If you suspect a problem, read the warning signs of a bad calibration and take the car back.
If the shop cannot produce any of it
Start with the plain possibility that the record exists and nobody sent it. Ask for the pre-scan, post-scan and calibration record for your VIN by email and give it a couple of days, since many shops sublet calibration and the file sits with the specialist.
If it does not arrive, escalate in order. Put the request in writing so there is a dated trail, and ask whether the calibration was performed in house or sublet, and to whom. If a claim paid for the job, ask your insurer for the file, because the documentation usually travels with the bill: how a glass claim is filed explains who holds what. If no calibration was performed on a vehicle that needed one, that is a redo at the shop's cost, not a negotiation, and making a warranty claim stick covers how to frame it.
The cost of having it done independently is worth knowing before that conversation, because it sets the size of the problem: standalone recalibration typically runs $150 to $400, with dual and dealer procedures higher, as broken down in the calibration cost guide.
What to do next
If you have not booked yet, ask for the documentation before you accept the quote rather than after the job, and add it to the list in the questions to ask before booking. A shop that says yes without hesitating is telling you it already produces these records as routine.
If the job is done and the paperwork is thin, work through the post job inspection checklist before you pay, and read what the warranty covers so you know what you are entitled to ask for if a system misbehaves later.
Frequently asked questions
Is a calibration certificate a legal requirement?
There is no single federal rule that hands you a certificate. What exists is the manufacturer's service procedure, industry standards for glass work, and in some cases state or insurer documentation requirements. In practice the record matters because it is the only evidence the procedure ran, and reputable shops produce one as a matter of course. Ask for it as a condition of the job.
How can I tell if a shop actually calibrated my car or just cleared the codes?
Clearing codes leaves a different footprint from calibrating. Look for a completion record from calibration equipment that names the procedure and result, timestamps on the pre-scan and post-scan that bracket the length of the job, and a module list rather than a summary line. A single page saying no faults found, produced in minutes, is a code clear.
My dashboard shows no warning lights. Do I still need the paperwork?
Yes. A camera can be aimed wrong and still report itself healthy, because the module checks that it received a plausible calibration, not that the aim matches the road. Absence of a light is the weakest evidence available. The scan reports and completion record are what you will need if a system is ever questioned after an incident.
Can I get the calibration documents from my insurance company?
Often yes, if the claim paid for the work. The calibration is billed as a line on the glass invoice and the supporting documentation frequently travels with it to the claim administrator. Call the claim number, ask for the complete invoice and any attached scan or calibration reports for your loss, and request them in writing.
What should I do if the paperwork arrives and something is wrong on it?
Compare three things first: the VIN, the date, and the list of systems. A mismatched VIN or a date that does not match your appointment is worth a phone call before anything else, since mixed up files are common. If the systems listed are fewer than the features your car has, ask specifically which procedures were run and which were skipped.