Your First OBD Scan: What to Record Before Clearing Codes

By AutoXpert UK · Practical buying guidance · Published 17 October 2026

Try the diagnostic scanner buying helper →

A diagnostic reader can help you collect information about a fault. The useful outcome of a first scan is a clear record, not a list of parts to buy. This guide explains how to prepare that record and recognise when you need professional help.

Start with the warning, not the shopping list

Read your vehicle handbook for the warning displayed and the action it requires. A scanner is not permission to continue driving against that guidance. If the vehicle is behaving unsafely, stop somewhere safe and seek assistance.

Before connecting anything, write down what happened: the warning message, whether the engine was cold or warm, and any change in performance or unusual noise. Do not attempt to recreate a dangerous symptom just to capture it.

Check that the tool supports your task

RAC explains that diagnostic trouble codes are stored by the vehicle and read through diagnostic equipment, with both generic and manufacturer-specific codes. Check the tool maker’s coverage for your exact car and intended system; “works with this brand” does not establish support for every function.

Keep a simple vehicle note with the model, year, engine and market. Check the scanner’s phone requirements, app access and instructions. For comparing packages, use our diagnostic tool cost checklist and scanner buying guide.

Make a record before changing anything

Follow the vehicle and scanner instructions for connection and operating conditions. If a scan is supported, save or export the report before making changes. Use this record sheet:

Vehicle details and scan date.
Exact code, including every letter and number.
System or control unit named by the tool.
Status and description shown in the app.
Warnings and symptoms you noticed.
Any recent repair or battery work you know about.

Keep private reports somewhere secure, particularly if they contain vehicle identifiers. If you share a screenshot publicly, check it for personal details first.

A code is a clue, not a confirmed failed part

Use the report to discuss the problem with a qualified technician. A code description alone is not a sufficient basis for replacing the component whose name appears in it. Avoid paying for parts until the cause has been investigated.

Clearing a warning does not repair its cause. Keep the original report and do not experiment with coding, adaptations or safety-related settings to make a warning disappear. If you cannot establish what a function does, leave it unchanged.

What to take to the garage

Bring the saved report, your symptom notes and relevant recent repair information. Ask what checks establish the cause, what the proposed repair covers and whether a follow-up test is included. That turns your scan into useful background for diagnosis.

Source and further reading: RAC guide to diagnostic trouble codes. This is a general workflow, not a diagnosis or hands-on scanner review. Published 17 October 2026.

Plan your next step

Plan your first diagnostic scanner →Check the scanner buying helper →Find diagnostic specialists →

Choose equipment for tasks within your ability, or contact a suitable specialist about your vehicle. Review sources and current business details before booking.