The compressor starts. You hear it pull in. Current draw looks right. Discharge pressure climbs. Suction stabilizes. The unit is running. Some techs pack up right there. Job done. Move to the next call.
The techs who build real reputations do not leave yet. They wait for three full cycles. They watch what happens when the system shuts off, how it behaves through the off period, and whether the next startup looks the same as the first. Then they make notes, close out the service record, and leave.
That waiting time, fifteen to thirty minutes depending on the equipment, is not wasted time. It is the most informative window in the entire service call. Here is what happens in those three cycles and why missing them is one of the most avoidable causes of callbacks in the trade.
A compressor that starts and runs normally on its first cycle after installation has proven almost nothing. Startup conditions are not representative of steady-state operation. The system just sat still while you worked on it. The refrigerant is distributed unevenly. The temperatures have not stabilized. The pressures will shift as the system reaches equilibrium. What you are seeing on that first cycle is the system waking up, not the system working.
Problems that will surface within 48 hours often announce themselves somewhere between the first and third cycle. A suction pressure that drops progressively across cycles suggests a restriction or a charge issue. Discharge pressure that climbs cycle over cycle suggests a condenser problem. A compressor that draws high amps on the second startup but not the first may have a weak start capacitor or a mechanical issue developing. An intermittent short cycling pattern that appears on the third cycle but not the first tells you the thermostat or the pressure controls are not calibrated correctly.
None of those things are visible on cycle one. They only become visible when the system has been running long enough for the underlying condition to reveal itself under real load.
The first cycle tells you the system starts. Three cycles tells you the system works. Those are different pieces of information and only one of them is worth driving away on.
There will be days when waiting for three cycles feels impossible. You have three more calls stacked behind you. The dispatcher is asking for an ETA. The customer is waiting to lock up. You know the feeling of standing next to a running unit watching the clock.
Here is the practical argument for waiting anyway. A callback on a major repair is going to cost you a minimum of ninety minutes in drive time, diagnostic time, and rework time. It is going to cost you the customer's confidence and potentially the account. It may cost you the warranty on the part you just installed if the compressor is damaged by a condition you could have caught during a proper verification period.
The three cycles you waited before leaving, fifteen to thirty minutes of actual time, is the insurance against all of that. Every tech who has ever been burned by a callback they could have prevented with a little more time on site knows this calculation exactly. The ones who have not been burned yet will learn it eventually.
⚠️ Leaving before the system proves itself under operating conditions is not efficiency. It is risk transfer. You are moving the risk of a problem off your schedule today and onto your customer's experience tomorrow. That is not a trade that works in your favor in the long run.
On a commercial bar fridge after a compressor swap, three cycles is particularly important because the system is designed to hold temperature within a narrow band. The cycling behavior tells you whether the refrigerant charge is correct, whether the thermostat is calibrated, and whether the compressor is moving the load it needs to move.
On the first cycle, watch how quickly the box temperature responds. After a compressor replacement, if the system has been down for any significant time, the box will be warm. It should pull down relatively quickly on the first cycle. If it is barely moving after ten minutes of running, you have a charge issue or an airflow issue that needs attention before you leave.
Watch the off cycles as well. A refrigeration system that short cycles off and then immediately kicks back on is telling you something. Either the thermostat differential is too tight, the charge is off, or there is a pressure control issue. Any of those findings surfaces between cycle one and cycle three and none of them are visible on startup alone.
On a five-ton rooftop unit after a compressor replacement, the cycles are longer because the system is larger and takes more time to reach steady state. Your observation points are the same, startup current, running amperage, discharge pressure, suction pressure, and discharge temperature, but you are also watching the building's response. Is airflow coming through the supply registers? Is the thermostat satisfied within a reasonable time at the setpoint? Is the outdoor unit cycling cleanly?
A rooftop unit that runs but does not satisfy the thermostat within a reasonable period after a compressor swap is flagging an undercharge, a metering device issue, or a duct restriction that existed before you arrived. Each of those is a finding. The first two are yours to address. The third is one you need to communicate to the customer before you leave so they understand what to expect going forward.
At the end of cycle three, write down what you saw. Discharge pressure at shutdown. Suction at shutdown. Amperage at steady state. Box temperature or space temperature at departure. Belt condition if applicable. Filter condition. Condenser condition. Any findings noted and communicated.
That record is your signature on the job. It says: I was here, I watched the system operate under real conditions, I measured what mattered, and I left with confidence that the system was working correctly. That is the standard that holds up in a warranty dispute, in a customer disagreement, and in your own professional conscience when you are driving to the next call.
Three cycles is not perfectionism. It is proof. And proof is worth thirty minutes of anyone's time.