A scanner finds a fault code, and the next button offers to erase it. Before pressing that button, save the information your mechanic may need. Clearing a warning is a different action from finding and correcting the problem that caused it.

On the Innova 5210, for example, the erase function removes diagnostic trouble codes and freeze-frame information and resets the status of the emissions monitors. A photo of one code can therefore leave out useful details that were available a moment earlier. The better first task is to make a complete record.

Start with what happened on the road

Before worrying about scanner menus, write down what you noticed. Was the warning steady or flashing while the engine was running? Did the car shake, lose power or make an unfamiliar noise? Record when it happened and any other messages on the dashboard.

Take photos only once you are safely parked. Follow your vehicle’s warning instructions, and do not restart an engine just to recreate a worrying symptom. Smoke, a strong fuel smell or a suspected leak is a reason to stop troubleshooting and seek assistance, not to connect a scanner and carry on.

If the car cannot be used safely, arrange recovery. A scan result does not override a serious symptom or your owner’s manual’s instruction to stop.

Record which car and tool produced the result

Begin your notes with the car’s year, make, model, engine and mileage. For an imported vehicle, include its original sales market if you know it. Add the date of the scan and the scanner or adapter model; for a phone-based tool, record the app you used too.

Check the tool manufacturer’s coverage information for that exact vehicle. Capabilities can vary between cars even when the same reader is used. Innova says its tools use North American OBD protocols, and that the 5210’s features vary by vehicle. Drivers elsewhere should confirm coverage for their local vehicle before choosing a reader.

An engine-code result does not automatically describe the airbag, braking or other systems. Write down which systems were actually selected or reached. If someone else performs the scan, ask for the complete report and the name of the tool rather than just a verbal description of the first code.

Keep the full code and its status together

Save the complete code, including its letter and every digit. Keep the displayed description and status beside it, and photograph any continuation screen if the wording does not fit on one display.

Labels such as stored, pending and permanent are part of the record. If the same code appears with two different labels, keep both entries instead of deleting what looks like a duplicate. You can leave the interpretation to the technician while preserving exactly what the reader showed.

For a practical example of capturing that record, TunedDrive’s guide to using an OBD2 scanner walks through the process with an Innova 5210, including connection checks and saving the screens. Follow your own scanner and vehicle instructions if you use different equipment.

Avoid renaming a result to match an internet search. A screenshot of the original display is more useful than a note that says only “sensor problem.” If the reader provides no definition, keep the code and that message together.

Save the freeze frame separately

Freeze-frame data is a stored snapshot of engine conditions when a fault was recorded. Depending on the vehicle and tool, it can include readings such as engine speed, coolant temperature and vehicle speed. Those values need their labels and units to make sense.

Innova’s 5210 documentation explains that its freeze frame belongs to the priority code displayed as code 01. There may not be a separate snapshot for every code. Keep the data with the code the tool associates it with, rather than copying the same readings underneath each result.

Photograph all the available pages or retain the exported report. If a snapshot is unavailable, write that down. Live data shows current readings, so a screen captured later is not a replacement for the stored conditions when the fault occurred. Do not drive around trying to reproduce the problem to fill a gap in your notes.

Keep readiness results and no-code messages

Save the emissions-readiness screen as well as the fault-code list. Readiness reports whether the supported monitors have completed their checks. New York’s DMV explains that a disconnected or replaced battery, or erased codes, can leave monitors incomplete.

Tell the mechanic about recent battery work or any earlier clearing attempt. Do not invent an explanation for a monitor marked incomplete; give them the displayed result and the history you know.

Also preserve a result that says no codes were found. It describes what the tool retrieved from the systems it accessed, rather than proving that every part of the car is healthy. On the 5210, a yellow indicator can refer to a pending code or unfinished monitors, so capture the screen instead of relying on the light’s color alone.

Record connection problems without forcing a workaround

A failed scan is still worth documenting. Photograph the exact error and note whether the tool powered on, whether the app connected to its adapter, and which vehicle was selected. Those are different stages of the connection.

Follow the manufacturer’s troubleshooting for your equipment. OBDLink, for example, says its adapters connect to one app at a time, so another running diagnostic app can interfere. That specific check is useful for OBDLink equipment; it is not a universal explanation for every communication error.

If the normal instructions do not resolve it, contact the tool’s support team or a diagnostic technician. Do not bridge connector pins or bypass vehicle security controls to force access.

Hand over the record before buying parts

Send the original screenshots or report with your symptom notes. Keep them in a dated folder so an earlier scan is not confused with a later one. Mention any recent service, battery replacement or code clearing, even if you are unsure whether it matters.

Innova’s code-retrieval instructions specifically caution against replacing a part solely because of a code’s description. Vehicle-specific testing is needed to confirm the fault.

Leave clearing decisions to the repair process. On vehicles that support permanent diagnostic codes, those codes have a separate clearing mechanism; a scanner’s erase command cannot simply remove them. California’s Bureau of Automotive Repair explains that the vehicle’s diagnostic system must verify that the fault is no longer present. A useful handover preserves the evidence your technician needs for that next step.