- Keep the pre-repair record.
- Document exact work and identifiers.
- Repeat the failure conditions safely.
- Check pending and permanent codes plus readiness.
- State what was not tested.
Define the success criteria before repair
Use the original complaint, code status, freeze-frame scene, measurement failure, or control discrepancy to define what must change. “Light off” is too weak when the controller has not rerun its monitor.
Record what changed
Capture part brand and number, software or calibration identifiers, wiring or mechanical repair details, fluids, torque or setup procedure, coding, registration, relearn, and who performed the work. This makes later regression analysis possible.
Repeat a comparable test
Compare the same signal set under similar temperature, load, speed, state of charge, or soak condition. Confirm no relevant pending code or symptom returns. For an intermittent complaint, one short drive may not establish confidence; document the observation window.
Close with limits
List completed and incomplete monitors, permanent-code state, unavailable modules, remaining codes, deferred work, and safety restrictions. A clean verification report should make its coverage and unknowns obvious.
Is clearing codes part of repair verification?
Clearing may be required by a procedure, but it is not verification. The vehicle must operate, rerun relevant tests, and remain free of the original evidence.
When is a repair verified?
When the defined failure no longer occurs under an adequate comparable test, required self-tests pass, and remaining limitations are documented.
This is general educational material designed to improve questions and evidence capture. Definitions, thresholds, enabling conditions, wiring, service steps, and safety requirements can differ by vehicle application. Use current official manufacturer information and qualified judgment for the actual repair.