Pre-Repair Diagnostic Scan Documentation Form

Complete it before any teardown, part replacement, or calibration work begins. The goal is to capture the vehicle's baseline condition while the damage state is still intact. If the scan is done after repairs start, it becomes harder to distinguish collision-related faults from pre-existing issues.

A technician or estimator familiar with diagnostic scan tools should complete it, with the scan tied to the repair order. In shops with multiple handoffs, the person performing the scan should record the tool used, the scan date, and any notes about incomplete module communication. That creates a clear audit trail for later review.

It works for collision repair and other pre-repair inspections where diagnostic trouble codes and ADAS status matter. It is especially useful for vehicles with multiple control modules, safety systems, or suspected electrical faults. If the repair does not involve diagnostics or module verification, a lighter inspection form may be enough.

Use it for each repair order where diagnostic evidence could affect the repair plan, estimate, or liability discussion. For vehicles with visible collision damage, a scan before teardown is the safest default. If new symptoms appear later, a follow-up scan can be attached to the same repair record as a separate entry.

List the modules checked, whether each module responded normally, and any DTCs or communication issues found. The baseline should make it clear which faults appear present before repair and which are likely tied to the collision event. Avoid vague wording like "scan completed" without identifying the actual results.

It creates a place to note whether the vehicle is ADAS-equipped, which systems were observed, and whether calibration may be needed after repair. That helps prevent missed steps on cameras, radar, lane-keeping, airbag, or other safety-related systems. It also supports clearer handoff to calibration or alignment work.

Common mistakes include scanning too late, leaving out the scan tool version, and failing to classify faults as collision-related or pre-existing. Another frequent issue is documenting ADAS observations without noting whether calibration is needed. The form works best when the technician records specific findings, not just a yes/no summary.

Yes. You can add fields for insurer notes, sublet calibration vendor, photo requirements, or a second technician review if your process needs it. You can also use conditional logic so ADAS questions appear only when the vehicle is equipped with those systems. Keep the form focused on the data you actually use.

It can be used alongside repair order systems, document storage, and diagnostic scan exports. The scan report file field and supporting photos make it easier to attach evidence to the job record. If your workflow supports it, link the form to the repair order number so the documentation stays traceable.