What to report
Describe when the symptom began, whether it happens hot or cold, under acceleration or at idle, and whether fuel, repair or battery work happened recently. A flashing engine warning, severe misfire, oil-pressure warning or overheating can require stopping immediately.
Confirming the cause
Depending on the symptom, testing may involve power supply, ignition, air and fuel delivery, cooling, mechanical condition, sensors or exhaust-related systems. The goal is to confirm the fault path before recommending parts.
Freeze-frame data and symptom history
Stored diagnostic information can include the conditions present when a fault was detected. Clearing it before inspection may remove useful clues. Record fuel level, temperature, road speed, load and recent work when the symptom appears.
Misfire, power loss or poor idle can involve ignition, fuel, air, mechanical condition, control inputs or multiple interacting faults. The test plan should follow evidence rather than a list of commonly replaced parts.
Mechanical condition still matters
Electronic data cannot rule out compression, valve timing, leakage, restricted flow or other physical problems. Where evidence points in that direction, mechanical measurements may be required before sensors or modules are condemned.
Fluid condition, overheating history and maintenance records can materially change the diagnosis. Provide accurate history even when the event occurred months earlier.
Confirming the repair
After the identified cause is addressed, the workshop should check that the symptom no longer occurs, live values are reasonable and relevant readiness or monitor requirements are explained. Some faults need an appropriate drive cycle before a final conclusion.