KRAI CASEBOOK / FIELD GUIDE
A vehicle repair history that answers “what changed?”
A list of replaced parts rarely tells the whole story. A useful record connects the original problem, the evidence, the work, and what happened afterward.
What to record for each visit
- Vehicle and date: year, make, model, mileage, and when the concern appeared.
- Problem: the driver’s words, the conditions that triggered it, and what was observed.
- Evidence: code or measurement only when actually captured, with its source. Keep receipts or scan files separately if your tool cannot attach them.
- Action: tests, parts, and labor that actually happened; avoid rewriting a guess as a confirmed cause.
- Follow-up: the same symptom or test after the work, including how long or under what conditions the vehicle was checked.
Why the follow-up is worth keeping
When a concern returns months later, a chronological case helps you see which symptoms repeated, what was previously tried, and whether the earlier repair was ever verified. It also makes a handoff to a repair professional clearer. A record does not establish a diagnosis by itself; it makes the underlying observations easier to review.
Keep a backup. A record saved only in a browser can disappear when browser data is cleared or you change phones.
Start with one real case
Enter the current concern, then return after a test or repair to add the outcome. The free Casebook pilot stores the case in your browser and can export a JSON backup.
Open the free Casebook pilot