History and evidence

Seller denied a fault the vehicle had recorded

This focused guide translates a scenario from To Buy A Car into a practical evidence path. It explains what the scanner can contribute without treating a code or reading as a final diagnosis.

Diagnosed or resolved2019 Chevrolet Traverse, private sale
Scenario

What the evidence showed

Vehicle or setting

2019 Chevrolet Traverse, private sale

Story context

Sarah Nowak. Used minivan search, ending in a 2018 Honda Odyssey Touring.

How it was handled

Stored fault read at the viewing contradicted the seller's account. Vehicle rejected on the mismatch rather than on the fault itself

Five-step evidence habit

How to approach a similar situation

  1. Park safely and follow the vehicle instructions before connecting or reading anything.
  2. Record the warning, symptom, mileage, operating conditions, stored codes, pending codes, and readiness status.
  3. Preserve the evidence before clearing data or disconnecting power.
  4. Compare the record with vehicle-specific service information, maintenance history, and physical inspection.
  5. Use the combined evidence to monitor, ask a precise question, seek an independent inspection, or obtain qualified repair help.
Important boundary: An OBD2 result identifies a monitored condition. It does not prove that a named part failed, show every mechanical problem, or establish that the vehicle is safe to drive.
Continue the story

To Buy A Car

Read the book overview and its evidence-focused sample chapter for the complete story context.

Open the book page