A fault code is a clue. Build the diagnosis around it.

A diagnostic trouble code is the beginning of an investigation. It records a condition detected by a control unit; it does not, by itself, establish which part should be replaced.

Record before you reset

Save the exact code, the reporting module, whether it is current or stored, the warning lamps and the symptoms. If the tool and vehicle support freeze-frame or live data, record that context too. Clearing codes first can remove information useful to the next person investigating the fault.

Check the tool and the vehicle

Confirm that the scanner supports the vehicle, system and protocol being investigated. A connector that physically fits is not evidence of full diagnostic coverage. For an older project car, verify compatibility for its exact year, market and control system rather than assuming a generic reader can access everything.

Give each claim a next test

Write down what was observed, your possible explanation, the test needed to distinguish it from alternatives, and the result. Use the vehicle's applicable service information and someone qualified to carry out the test. A change in symptoms after replacing a part is worth recording alongside the other changes made that day.

Keep the evidence together

A useful repair record joins the original symptom, scan information, test findings, intervention and follow-up. Bosch describes code reading as a starting point and notes that wiring or other system issues can underlie a code. This article is a reporting framework, not a vehicle-specific repair instruction.