A useful diagnostic record lets another technician see why a repair was recommended. It connects the customer's concern to observations, a test that can distinguish possible causes, and evidence that the agreed repair addressed the concern.
This guide is for technicians and shop managers organizing work. It provides a case-record structure, not a substitute for the vehicle manufacturer's procedures, equipment requirements or training. Tool selection is covered in Automotive Diagnostic Equipment.
Write a concern that can be investigated
Separate the customer's words from the shop's observations. “Sometimes hesitates” needs conditions: when it began, whether the engine was cold or warm, frequency, road situation, recent work and any messages. Record what remains unknown without improving the story to fit an early theory.
Then identify the vehicle and relevant configuration. Record VIN, mileage, powertrain, modifications and software information where applicable. Agree on the initial diagnostic scope and a contact point before further work. The service-advisor guide covers documenting that agreement.
ASE's 2026 Advanced Engine Performance study guide includes verifying a concern, distinguishing malfunction from normal operation, locating relevant service information, selecting procedures from the available evidence and verifying repair effectiveness. Those are useful checkpoints; the case form below is Yenra's organizational aid.
Preserve what the vehicle is telling you
Keep the original scan report with the job record. Distinguish a stored code from a current observation, and note which modules were reached. Save relevant freeze-frame data, readiness state, timestamps, conditions and tool identification before changes that could erase context.
EPA's 2001 OBD inspection guidance explains why codes and associated freeze-frame data matter to diagnosis. It also discusses readiness being reset by code clearing. This is background on preserving diagnostic evidence, not a statement of today's local inspection rules.
Name files so a colleague can find them: job identifier, vehicle identifier, date and whether the capture is before or after work. Keep customer identifiers inside the shop's controlled records. A scan screenshot forwarded without its vehicle or conditions is difficult to interpret later.
Make the next test answer a specific question
On a narrow screen, scroll the table sideways. Keyboard users can focus the table region and use the arrow keys.
| Record field | What belongs here | Useful review question |
|---|---|---|
| Observation | The symptom or data actually captured, with conditions. | Could another technician recognize the same event? |
| Working explanation | A possible cause and an alternative. | What evidence would make us reject it? |
| Test reference | The applicable manufacturer procedure and revision. | Does it match this system and vehicle? |
| Measurement | Value, units, conditions, equipment and specified limit. | Where did the comparison limit come from? |
| Decision | Supported finding, remaining uncertainty and next action. | Does the evidence justify the requested work? |
Use the vehicle maker's service information to establish the test method and applicable limits. Do not borrow a threshold from an unrelated model or confuse a plausible live-data value with an independent measurement. ASE's L1 task list specifically includes checking scan observations against actual system or circuit measurements.
If equipment, access, information or competence is missing, document the gap and arrange the appropriate resource. A clear referral or a request for more diagnostic time can be the correct result of the first appointment.
A fictional repair order, from concern to closure
This is a documentation example, not a diagnosis for a real vehicle. No numerical limit or repair operation is supplied because those depend on the exact system. If the concern cannot be reproduced, write that explicitly and agree on an evidence-gathering next step.
Close the case with evidence and remaining questions
Download the diagnostic case record. Attach the original and final reports, referenced procedure, approvals and verification notes. Record monitor status separately from the repair outcome; clearing a code alone does not demonstrate a repair.
Write the customer-facing explanation in ordinary language: what was reported, what was found, what was authorized, what changed and how it was checked. For an owner preparing information before the appointment, use the scan-data and symptom-record guide.
Explore Autos: vehicle guides, technology and design · Cars: buying, maintenance and ownership