KRAI CASEBOOK / FIELD GUIDE
What should you record when a car problem comes and goes?
A problem that disappears before a shop visit can be difficult to reproduce. A short, factual record gives the technician a better starting point than a guessed part or a vague description.
Write down the event while it is fresh
- What happened? Describe what you saw, heard, smelled, or felt. “Engine stumbled for two seconds at a stop” is clearer than “bad fuel pump.”
- When and under what conditions? Note the date, odometer, whether the engine was cold or warm, approximate speed, idle or acceleration, weather if relevant, and how long it lasted. Mark anything you do not know as unknown.
- How often? Record each occurrence, including days when it did not happen under similar conditions. Do not recreate a dangerous event just to make a better note.
- What evidence exists? Copy the exact warning text or code only if you actually saw or read it. Identify whether it came from the dashboard, a scan tool, or someone’s observation. Keep photos or scan files separately if useful.
- What changed recently? List recent service, parts, fueling, or battery work as context, without claiming it caused the problem.
A note a shop can use
Example: “2006 minivan, 181,000 miles. On two mornings this week, the engine hesitated for about three seconds while accelerating from a stop. Both times the engine had been running under five minutes. No warning light noticed. It did not happen on the warm drive home. No scan performed. Spark plugs were replaced last month.”
This example documents the pattern and its limits. It does not establish a cause. If the symptom changes, add a new dated observation instead of editing the old one into a diagnosis.
At the shop
Give the technician the record and ask them to note whether they could reproduce the concern, what conditions they tested, and what further check they recommend if it does not appear. Keep the written estimate and any test results with your own records. A “could not reproduce” result is useful information about that visit, not proof the concern never happened.
Start a free vehicle case
Enter the concern and observations in KRAI Casebook before the visit. After a test or repair, add what was actually done and what happened next. The pilot stores cases in your browser and offers a JSON backup. It does not scan the vehicle, diagnose the fault, attach photos, or verify that a repair worked.
Open the free Casebook pilotIf steering, braking, overheating, stalling in traffic, or another safety concern is involved, avoid driving to collect more observations and seek qualified help. This is a recordkeeping guide, not a repair procedure.