From customer complaint to testable evidence
Treat the complaint as a starting hypothesis, not proof of a faulty sensor or a required calibration.
Warning lamp, driver complaint, stored DTC and an unsuccessful calibration report can describe different things. An intermittent feature may be operating within its documented limitations; it may also require fault diagnosis. Never infer “sensor needs calibration” from the complaint alone.
Complaint triage · choose an investigation
Pre-scan and diagnostic evidence
A scan records electronic evidence within the limits of the tool and the vehicle; it is not a physical inspection.
Preserve applicable pre-scan results and relevant freeze-frame or status information as available. Record scan time and vehicle identifiers.
Understand current, history, communication and enabling-condition information as described by the manufacturer and tool.
Check supply voltage, related vehicle systems, recent repairs and visible sensor condition as required by the diagnostic path.
Evidence sorter
Select a record to reveal what it establishes—and what it does not.
Visual, mechanical and system-level checks
ADAS diagnosis crosses electrical, mechanical, optical, software and vehicle-network boundaries.
Before repeating a routine, consider the physical installation and the required prerequisites: camera sight line, glass and mount condition, radar bracket/cover, wiring/connectors, vehicle geometry, relevant sensor data and any manufacturer-defined setup checks. Not every check applies to every vehicle.
Fault-domain challenge
When a calibration attempt does not complete
An unsuccessful attempt is diagnostic information—not permission to improvise target positions or repeatedly retry unchanged conditions.
Capture the exact message, timestamp, routine, vehicle state, equipment/software identification and applicable setup conditions. Determine whether the OEM procedure requires resolving DTCs, completing prerequisites, inspecting mounts, correcting environment, updating configuration, or using a different specified method.
Failed-routine decisions
Service documentation and traceability
A defensible work record separates what was specified, attempted, completed, observed and still unresolved.
Capture the relevant OEM information identifier/revision when available; vehicle/VIN/options; complaint and work performed; baseline and final diagnostic evidence; setup and equipment used; relevant measurements and photos where permitted; procedure result; required post-checks; and any deviation, deferral or referral. Protect customer identifiers and access to records.
Evidence builder · fictional training example
Choose what belongs in a coherent service record, then generate an illustrative template. No real customer or vehicle data is collected.
Choose evidence items, then build a fictional training record.
Post-calibration verification is not one single event
A “routine complete” message, a clear scan and an OEM-required functional check are different evidence.
Record precisely what the tool reported and which operation it refers to.
Complete and interpret manufacturer-required checks, including remaining faults and conditions.
Perform only the OEM-prescribed safe validation and road checks when applicable, lawful and achievable.
Communicate unresolved problems, unperformed required checks and any required escalation.
Verification gate simulator · fictional job
Handoff, unresolved conditions and technician responsibility
Communicate what the evidence shows and what remains unverified, without overstating capability or completion.
At handoff, distinguish completed operations from unperformed or unsuccessful required steps. Use an appropriate shop policy and OEM guidance to determine whether a vehicle can be released, needs further diagnosis or should be referred; do not make a universal release decision from this course. Explain feature limitations without suggesting that assistance replaces driver attention.
Choose the accurate customer statement
05.7 knowledge check
Apply diagnostic reasoning, documentation discipline and verification boundaries to fictional ADAS service scenarios.
Answer all 10 questions to receive a score and explanations. Results are browser-local conceptual knowledge records, not customer service records.