Record and Preserve Details from an ADAS Calibration Report
How to read an ADAS calibration report PDF and build a traceable record of vehicle identifiers, dates, system labels, procedure references and outcomes, with open questions sent to the issuer.
Contents
- Key terms
- Opening and reading the PDF
- Step 1: Preserve the original file unchanged
- Step 2: Build an extraction worksheet
- Step 3: Copy labels as printed, not as interpreted
- Step 4: Handle conflicts, multiple dates and missing results
- Step 5: Keep a question log for the issuer
- What the record does and does not establish
- Filing it for later use
To get lasting value from an ADAS calibration report, keep the file exactly as you received it. Then build a separate worksheet that copies each detail as printed: who issued the report, the vehicle identifiers, every date and its label, the system names, the procedure references and the stated outcome. Note the page where each detail appears. Do not interpret the labels. Anything you cannot confirm from the document goes into a question log addressed to the issuer. You end up with a record that you, a later shop, an insurer or a buyer can trace back to the original page.
Key terms
ADAS stands for advanced driver assistance systems. These are features such as lane-keeping support, automatic emergency braking and adaptive cruise control, which rely on cameras, radar and other sensors. Calibration is the process of aligning those sensors so the system interprets its surroundings as designed. It is commonly performed after work that can disturb a sensor, such as windshield replacement, collision repair or suspension and alignment work. A calibration report is the document a shop or technician produces to show what was done. Its layout, terminology and level of detail vary by issuer and by the equipment or software used, so no single template applies to every report.
Opening and reading the PDF
Most calibration reports arrive as PDFs. You can open them with any standard PDF viewer, including the free readers built into common web browsers and operating systems. You do not need special software to read the report. Some reports reference separate attachments, such as screenshots, scan-tool printouts or photos. If they do, check whether those files came with the report or must be requested.
Step 1: Preserve the original file unchanged
- Save the report exactly as received, with its original filename. Do not annotate, re-save or edit that copy.
- Keep a second backup copy in a different location, such as cloud storage plus a local drive.
- Record the date you received the file and how it arrived, for example by email from the shop or as a download from a portal.
- Save any attachments the report references. If an attachment is referenced but missing, list it as missing rather than assuming it exists.
- Do all highlighting and note-taking in a separate worksheet, never in the original.
Step 2: Build an extraction worksheet
Create one row per detail, and link each entry to the page or section where it appears. Fill in only fields that are actually present on the report. Where a field is absent, write "not shown" instead of leaving it blank or guessing. That way a reader can tell a missing detail apart from one you forgot to copy.
| Field | What to record | Example entry |
| Report file and page | Filename and the page or section number | report.pdf, page 2 |
| Issuer | Business or technician named as producing the report | As printed on the header |
| Report or reference number | Any job, invoice or report number | As printed, or not shown |
| Vehicle identifiers | VIN, make, model, year, plate or mileage exactly as printed | Copy character by character |
| Dates | Each date plus the label printed beside it | 'Date performed: ...' or 'Printed: ...' |
| System label | Name of the system or sensor as written | 'Front camera' or 'System A' |
| Procedure or reference label | Procedure name, code or reference cited | 'Procedure P-12' |
| Reported outcome | Result wording exactly as printed | 'Complete', or not shown |
| Notes or attachments referenced | Any remarks, warnings or referenced files | 'See attached printout' |
| Issuer question | Anything unclear that only the issuer can answer | Added to question log |
If you prefer a plain-text template you can paste into a notes file or spreadsheet, the same structure looks like this:
Report file: ____________ Page/section: ____
Received on: ____________ Received via: ____________
Issuer: ____________
Report/reference no.: ____________ (or: not shown)
Vehicle identifiers: ____________ (as printed)
Date 1 + label: ____________
Date 2 + label: ____________
System label: ____________
Procedure/reference: ____________
Reported outcome: ____________ (or: not shown)
Notes/attachments: ____________
Question for issuer: ____________
Step 3: Copy labels as printed, not as interpreted
Keep the report's own wording. Do not expand abbreviations, translate codes or assign technical meanings, even when the meaning seems obvious. Abbreviations and outcome terms are not standardized across every issuer. A paraphrase can also quietly change what the record says.
Hypothetical example: a report lists "System A," "Procedure P-12" and "Complete" on page 3. Your worksheet should record those three labels word for word, with "page 3" as the location. It should not say "camera successfully calibrated" or "safe to drive." Instead, add two questions to the issuer's log: what "Complete" denotes, and which dated procedure or version P-12 refers to.
Step 4: Handle conflicts, multiple dates and missing results
- Conflicting identifiers: if the VIN, plate or model on one page differs from another, record both readings with their page locations. Then flag the vehicle association for the issuer to confirm. Do not pick the one you think is correct.
- Multiple dates: reports may show several dates, such as when work was performed, when the report was generated or when it was printed. Record each date with the label printed beside it. Treat a date with no label as "unlabeled" rather than assigning it a role.
- Absent outcome: if no result is stated for a system or procedure, write "outcome not shown." A missing result is itself a detail worth asking about.
- Unreadable sections: if part of the PDF is cut off, blurred or blank, note the page and request a clean copy from the issuer.
Step 5: Keep a question log for the issuer
Only the business or technician that issued the report can explain its labels, procedures and results. Keep each question tied to the field it concerns. Record the answer as a dated addition, separate from the original. That preserves the difference between what the report said and what was explained later.
| Field | Question for issuer | Response | Date of response | Supporting document |
| Reported outcome (page 3) | What does 'Complete' denote for System A? | (pending) | (pending) | (pending) |
| Procedure label (page 3) | Which dated procedure or version does P-12 reference? | (pending) | (pending) | (pending) |
| Vehicle identifier (pages 1 and 2) | Which VIN reading belongs to this vehicle? | (pending) | (pending) | (pending) |
Ask for answers in writing, such as an email or an updated report. That gives every response a supporting document you can file alongside the original.
What the record does and does not establish
A well-kept record shows what the report states and where it says it. It cannot by itself confirm that a driver assistance system works correctly. It also cannot confirm that the procedure matched the vehicle manufacturer's current requirements for that model year and equipment. Those points matter if you are relying on the report for an insurance claim, a warranty question, a resale or a concern about how a system is behaving. In those cases, get the confirmation from the issuer, and where relevant check the vehicle manufacturer's published service information for your specific vehicle.
Filing it for later use
- Store the untouched original, your worksheet, any attachments and the question log together in one folder named for the vehicle and the report date.
- Add the folder to your broader vehicle service records so the calibration can be matched to the related repair, such as a windshield or collision job.
- If the vehicle is sold, hand over the original report along with the worksheet. The next owner then has both the source and your traceable summary.
Related articles
Match and File a Vehicle Fluid Analysis Report
How to read a vehicle fluid analysis lab report PDF for record keeping: match it to the right vehicle, component and sample, record results exactly, and link earlier reports.
Identify and Transcribe Vehicle Emission Information Label Fields
How to find and read a VECI label: what the test group, engine family, evaporative family and other fields mean, and how to transcribe them accurately.
Identify Battery Test Report Values, Ratings and Reported Assessments
How to read a battery test report: tell measured voltage and ratings from the selected rating, keep units and test conditions, and record the tester's verdict.
Record Exact Dashboard Messages for a Service Visit
How to capture the exact wording of a dashboard message, plus the warning lights, sounds and driving conditions around it, so a service visit starts from an accurate record.
Verify Extracted Service Invoice Fields Against the Original Scan
A practical method for checking OCR-extracted vehicle service invoice fields against the original scan, reconciling line items and totals, and saving only verified data to your vehicle records.
Identify Wheel Positions, Columns and Units on an Alignment Report
How to read a wheel alignment printout: find each wheel position, separate before, after and specification columns, and record units and symbols correctly.
Find Candidate Technical Service Bulletins and Record Their Scope
How to look up technical service bulletins through NHTSA by year, make and model, why a VIN search shows recalls instead, and how to record each bulletin's number, date, revision and stated vehicle scope.
Identify Brake Inspection Positions, Measurements and Units
How to read brake inspection sheet labels such as LF, RF, LR and RR, tell brake-lining millimeters apart from tire tread and pressure entries, and transcribe each value with its source sheet.
Record Vehicle Parts Purchases, Identifiers and Installation Evidence
A practical template for recording car parts receipts, part numbers and installation evidence, keeping purchases separate from documented installation.
Read Service Paperwork and Record Completed Work
How to read car service paperwork, extract vehicle, date, mileage, work and charge details, and separate recommended work from completed work before updating your service log.