A fault-code number without its status loses useful context. A report may describe a code as pending, confirmed, current or historical. Those labels are not interchangeable, and manufacturer diagnostic systems can display additional status information that a basic reader leaves out.
Save the original report
Keep the complete code, any suffix, the module that recorded it and the wording used by the tool. Include the date and whether the warning was present during the scan. A screenshot cropped to the code number can hide the very information needed to decide which fault to investigate first.
Confirmation is not a parts instruction
A confirmed code does not automatically condemn the component named in its description. The circuit, operating conditions and associated systems still need assessment. Equally, a pending code should not be dismissed when it matches a repeatable customer complaint.
Tell the workshop whether codes were cleared before the latest scan and whether the same journey conditions have occurred since. Ask for the diagnosis to connect the reported symptom to test evidence. This is more useful than comparing the number of codes displayed by two different readers.
Related help
- Permanent Fault Code Remains After Repair: What to Ask Next
- Freeze-Frame Data and Live Data: Two Different Views of a Fault
Browse all fault guides or use the vehicle module finder to prepare your enquiry. Include the vehicle, symptoms, complete fault codes and any previous test results. Assessment scope and compatibility must be confirmed before booking or sending a unit.