Bonham field notes · 01 / 10
Build a vehicle file in which every document has a job.
A VIN decoder, a vehicle-history report, a recall lookup and a pre-purchase inspection answer different questions. Use them together, match the vehicle identity across the file and record what each source leaves unknown. One reassuring result does not complete the investigation.
- Identity
- Reported history
- Open recalls
- Present condition
Start with the question behind the document
A listing gives you a candidate. Your next task is to establish which records describe that candidate and what those records actually mean. A decoder can help identify encoded vehicle information. A report about recorded history cannot tell you everything that is happening mechanically today.
Write the complete VIN at the top of your notes, then compare it with the vehicle and every document supplied. Check the date on each record. If a report belongs to a similar truck or predates a change you are asking about, stop and resolve that mismatch before relying on it.
Give each evidence source a defined role
NHTSA describes its decoder as a way to identify information encoded in a VIN, including manufacturing information. That is different from a physical inspection of installed equipment or a complete account of a vehicle’s past.
NMVTIS explains that its vehicle-history product focuses on title, brand, odometer, total-loss and salvage information. Other history products have their own coverage. Ask which product you received and read its scope instead of assuming all reports contain the same records.
A recall lookup addresses a different question again. NHTSA identifies limitations in VIN recall results, including certain recently announced or older recalls and repaired recalls. A result does not certify mechanical condition. An independent inspection supplies another type of evidence, with a scope and exclusions you should discuss with the inspector.
Create a short “question, evidence, gap” file
Instead of saving a folder of screenshots without context, give every item a one-line purpose. For example: “This record helps identify the truck; it does not confirm that the pictured towing equipment is installed.” That sentence makes a later conversation much more productive.
Keep conflicting information visible. A discrepancy is a question to resolve, not a reason to silently select the more convenient answer. Request an explanation, the relevant supporting document and an appropriate inspection when the issue calls for one. Redact previous owners’ personal information; it is unnecessary for your comparison.
Use the same file when arranging a visit
Bring your evidence and the unanswered questions to the appointment. Compare the actual vehicle with the listing and records. For a remote purchase, the photo-request packet can help make your request specific before you travel.
This guide does not provide a vehicle-history service or certify a particular vehicle. Its purpose is to help you recognize which answer you have, which answer you still need and who can provide the relevant evidence.
The four-question evidence file
Copy these prompts into your notes or print this section and write on the lines. This page has no form fields and does not store your answers. Keep personal account and financial details in your own records.
- Identity
- Which VIN and configuration does this record identify?
- Reported history
- Which product, reporting scope and report date am I using?
- Recalls
- What does the result cover, and which limitations remain?
- Condition
- Who inspected the vehicle, when, and what was excluded?
- Unresolved differences
- What conflicting information still needs an explanation?
Questions worth asking
Does a VIN decoder replace a vehicle-history report?
No. Encoded identification information and reported historical records are different evidence. Neither replaces an inspection of the actual vehicle.
Does a report without a listed problem prove the vehicle has none?
No. Review the source’s coverage and limitations, identify missing information and obtain an appropriate independent inspection.
Continue with the question that comes next
- A Better Test Drive: Bring Your Real Life Along
- Flood History: Questions to Resolve Before Buying a Used Vehicle
- Buying a Modified Used Truck? Ask for the Build File.
From our existing guides: Buying a Used Truck From Far Away? Ask for This Evidence Packet First · Buying a Used Truck in Bonham: A Practical Inspection Plan.
Research behind this guide
- NHTSA VIN Decoder
- NHTSA Recall Lookup: coverage and limitations
- U.S. Department of Justice / NMVTIS: Understanding a Vehicle History Report
- FTC: Buying a Used Car From a Dealer
By Bonham Chrysler · Prepared with AI assistance · Published November 1, 2026. This guide offers an original question-and-record framework; it does not report a hands-on vehicle test. Source references are shown as names so you can continue your visit on our site.