Map impact area, structural/body work, removed/replaced components and customer concerns before choosing tests.
17.6 · Repair Planning, Post-Repair Scanning & Calibration Links
Build a complete repair plan from damage evidence, OEM procedures, system dependencies, scan results and calibration prerequisites—then prove the repaired vehicle is ready for release.
Service boundary: This is a planning and evidence-training environment. Actual repair, programming, aiming, calibration, restraint and ADAS procedures must follow current vehicle-specific OEM information, tooling, facility and qualification requirements.
7 Mini-Lessons
Retrieve procedures, position statements, measurements, one-time-use parts, setup requirements and related operations.
Use scan/status evidence to document what the vehicle reports before work and separate pre-existing from collision-related concerns.
Connect structural geometry, alignment, glass/brackets, ride height, tire condition, power/network health and configuration to downstream functions.
Compare pre/post evidence, confirm communication, DTC status and affected-system operation rather than merely clearing codes.
Determine which repairs trigger aiming, initialization, relearn, programming or static/dynamic calibration and prove prerequisites first.
Document procedures used, measurements, scan evidence, calibrations, results and unresolved/escalated items for a defensible release record.
8-Part Repair-Plan Explorer
Damage map
Trace this domain from damage evidence through required operation, prerequisite and release proof.
OEM procedures
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Pre-scan baseline
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Structural/alignment prerequisites
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Electrical/network/configuration
Trace this domain from damage evidence through required operation, prerequisite and release proof.
ADAS/restraint dependencies
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Calibration/relearn actions
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Release documentation
Trace this domain from damage evidence through required operation, prerequisite and release proof.
Repair Plan → Verification Lab
Select a normalized teaching state. Values are reasoning indices—not OEM tolerances, calibration specifications or scan-tool limits.
Plan completeness
—
Prerequisite evidence
—
Scan/function evidence
—
Release confidence
—
Choose a state.
6-Step Repair Planning & Release Workflow
- Document damage, prior condition, repair scope and affected systems
- Retrieve current OEM repair procedures and identify required related operations
- Capture baseline/pre-repair scan and measurement evidence where applicable
- Complete repair prerequisites: structure, alignment, mounting, power/network, configuration and environmental/setup conditions
- Perform required post-repair scans, function checks, programming/relearns/calibrations using approved procedures
- Compare before/after evidence, resolve exceptions, and document release or escalation
4 Evidence-Gated Cases
Case 1: Camera calibration will not start
Windshield and front-end work are complete, but the calibration routine reports prerequisites not satisfied.
Best branch: prerequisite branch. Verify glass/bracket, alignment/ride-height/tire/setup and OEM conditions before condemning the camera.
Case 2: Post-scan shows a new network DTC
Pre-scan did not show the fault. A repaired-area module now intermittently drops communication.
Best branch: repair-created electrical/network evidence. Resolve the new fault before release rather than clearing it as history.
Case 3: No DTCs after structural repair
The scan is clean, but a radar bracket and suspension hard point were in the repair area.
Best branch: procedure/dependency branch. A clean scan does not prove geometry, mounting or required calibration is complete.
Case 4: Calibration completed, complaint remains
The scan tool reports calibration success, but the original driver-assistance complaint is still reproducible.
Best branch: functional verification/root-cause branch. Calibration completion is one piece of evidence, not proof the whole repair succeeded.
Randomized 10-Question Knowledge Check
Instructor Practical Rubric · 6 Dimensions
OEM information use
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Damage/repair-scope mapping
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Scan & measurement evidence
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Dependency/prerequisite reasoning
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Calibration/relearn planning
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Release verification & documentation
Rate 1–4 using observed evidence. Online completion does not equal practical competency.
Depth profile: Foundation = identify why scans, procedures and calibrations belong in the repair plan. Technician = correlate damage, scan data, geometry and calibration prerequisites. Deep = defend a complete repair/release plan with vehicle-specific evidence and explain unresolved exceptions.
Preserved supporting routes: ADAS OEM Research · ADAS Alignment Considerations · Structural Measurement · Complaint Intake & Test Planning