A cooler that starts, stops and starts again is reporting a sequence problem. A useful work order captures enough evidence for the technician, dispatcher and manager to see the same event.
Start with operating conditions
Record the complaint in the customer's words, ambient temperature, box temperature, product load, door activity and when the behavior began. These facts separate a control problem from a load or airflow problem.
Preserve the sequence
Record the call for cooling, contactor state, compressor start, pressure or temperature response, stop condition and time between cycles. Do not write only “short cycling.” Write what opened the circuit and what happened immediately before it.
Attach readings to the moment
Voltage, current, pressure and temperature are useful only when the ticket says where and when they were measured. Include the instrument, test point and operating state. A photograph can preserve the control setting, nameplate and wiring condition.
Close with proof
The closeout should state the confirmed cause, work performed and observed result after a full operating cycle. In EcoService OS, those fields stay with the work order so a later callback begins with evidence instead of memory.
See how the same workflow supports HVAC and refrigeration service teams.