Untitled AI art by @Squortsoff

Service history is part of **diagnosis**, not paperwork. ‘Sensor replaced’ does not explain the bus fault, why the sensor was blamed or whether replacement fixed it. Record the conditions, codes, readings, decision and follow-up result so the next shift can continue without repetition. Identify the VIN, model, component and, if needed, control unit. Describe when the fault occurs: cold or warm, load, running time, temperature and frequency. Before clearing codes or switching off power, save DTCs, status, related codes, freeze-frame data and test parameters. Record measured values, conditions and connection points; document power, earth and signal tests rather than ‘wiring OK’. After repairs, record parts, fluid specifications and software versions before/after. Reproduce the fault conditions and log the result to distinguish recurrence from a new fault. Visual: ‘sensor replacement’ vs a record of readings, action and test result.