OBD-II Reports: Codes, Findings, and Repair Approval

Imagine a customer arriving with a free scan that reports a cylinder-two misfire. They ask for an ignition-coil price. The code points to a detected condition; it does not establish whether the cause is ignition, fuel, wiring, or a mechanical problem.

An OBD-II report should explain three things first: what the vehicle reported, what the technician established, and what the customer needs to approve. Keep the detailed scan as evidence behind that summary.

Give the scan a clear scope

OBD-II means second-generation on-board diagnostics. Diagnostic trouble codes, or DTCs, are part of the evidence. SAE J2012's published scope describes standardized codes and manufacturer-specific ranges; the full definition and vehicle service information matter.

Record vehicle identity, mileage, complaint, scan date, tool and software, ignition/engine condition, modules requested, and communication limits. A generic emissions scan does not inspect every control module or mechanical safety system.

Use the automotive inspection report for findings and reference the retained raw scan. The multi-point inspection guide explains why a scan alone is not a completed vehicle inspection.

Save evidence before changing it

Preserve exact codes, reporting modules, displayed statuses, lamp command, readiness results, and available freeze-frame data before a reset when safe. Freeze-frame data are selected operating readings captured with certain faults, not a complete recording of the event.

EPA's OBD inspection guidance explains the usefulness of fault information and associated data before repair. It is a technical reference, not the current eligibility rule for every state inspection program.

Record any clearing, battery disconnection, programming, or other step that could change the evidence. Incomplete readiness can be consistent with a reset; it does not establish who cleared anything or why.

Explain status without inventing a diagnosis

Keep the tool's actual labels and explain them within the relevant system:

California BAR's OBD reference explains permanent codes and California inspection criteria. Ordinary code clearing or battery disconnection cannot erase a permanent code; the onboard system must meet its clearing conditions. Explain any remaining code alongside the actual retest results.

Use vehicle-specific criteria for diagnostic values and monitor completion. Do not prescribe a universal number of driving miles, especially when the vehicle is unsafe to operate.

Price the testing that is still needed

Connect the initial finding to an automotive estimate for a defined diagnostic stage. State included tests, access, price or cap, exclusions, and the stop point. The estimate-authorization guide explains the approval record.

California's Write It Right guidance includes specific teardown-estimate and reassembly disclosures before diagnostic disassembly. A vague “diagnose it” approval does not replace applicable requirements.

Obtain the required repair authorization before replacing parts or adding testing. Keep approved work separate from recommendations on the automotive work order.

Write the finding in ordinary language

Illustrative summary after actual testing might read:

We reproduced the reported rough idle. The tests in worksheet D-18 support a fault in the identified ignition coil. The initial code identified the affected cylinder; the recorded tests support the replacement recommendation. The attached repair price is awaiting approval.

If testing is inconclusive, say so instead. The repair-order guide connects the complaint, evidence, approval, and performed work.

Check relevant manufacturer information and potential recall coverage. The NHTSA recall lookup has scope limitations, including certain completed, older, newly announced, and non-safety campaigns. Record the source, date, and result and confirm applicable remedies with the manufacturer or dealer. A service bulletin is not automatically a recall or free repair.

Close with what the retest showed

Record the performed repair, tests repeated, symptom result, remaining codes, readiness, and follow-up. Address immediate hazards before routine scanning; use the actual vehicle's warning instructions and appropriate assistance when operation is unsafe.

“Light cleared” is not a verified repair. Make the invoice describe the authorized work, while the report describes what was and was not established. Official emissions-test eligibility remains a separate conclusion under the current program rules.