HVAC Emergency Service SOP: Build a Clear Call-to-Completion Process

A workable HVAC emergency service SOP assigns a call priority within 10 minutes, records the facts needed for dispatch, gives the caller a realistic update time, and closes with documented work and a follow-up task. Write the procedure around decisions a dispatcher and technician must make under pressure, not around broad promises to provide fast service.

Start by listing the equipment and failure types that create genuine urgency for the properties you serve: a no-cooling call with an indoor temperature above 85°F, a no-heat call with occupied space falling below 55°F, a burning odor, active water leaking through a ceiling, repeated breaker trips, or a carbon monoxide alarm. The asset ages, expected replacement dates, and recurring failures captured in HVAC equipment replacement planning can help distinguish a one-off repair from equipment that needs a planned replacement discussion after the immediate issue is stabilized.

Set emergency levels before the phone rings

Use three or four priority levels with written response targets. For example, Priority 1 can cover immediate safety hazards, major water release, loss of heating or cooling in a critical occupied area, and electrical burning smells; require dispatcher action within 10 minutes and technician contact within 30 minutes. Priority 2 can cover total loss of heating or cooling in a standard occupied area, with a same-day target, while Priority 3 covers reduced capacity, unusual noises, and non-critical comfort complaints scheduled in the next available service window.

Avoid letting the word emergency decide the priority by itself. The dispatcher should ask what system is affected, when it stopped working, current indoor temperature, whether there is water on the floor, whether an odor or smoke is present, whether breakers have tripped, and whether the building is occupied. Record the thermostat set point and displayed room temperature, not just a report that the system is "not working."

Include a short caller safety script. If there is smoke, sparking, a strong burning smell, or water reaching electrical equipment, the script can direct the caller to stop using the system and keep clear of the affected equipment. A caller can also check one useful fact without tools today: confirm that the thermostat is set to Heat or Cool rather than Off, that the set point is at least 3°F beyond the displayed room temperature, and that the display has power.

Write the HVAC emergency service SOP for dispatch and field handoff

Make the dispatch form the backbone of the procedure. Require the dispatcher to capture the caller’s name and callback number, site address, access instructions, equipment type, unit location, reported symptom, priority level, and time the call was received. For larger sites, add unit identifiers such as RTU-3, AHU-2, or Boiler-1 so the technician is not sent to a roof, mechanical room, or suite with only a vague description.

The handoff should tell the technician what is known, what has already been checked, and what expectation was given to the caller. A dispatch note such as "Priority 1, RTU-3; cooling off since 2:15 p.m.; 88°F in occupied room; ceiling leak below unit; technician to call site contact before arrival" is more useful than "no AC emergency." Set a rule for status updates, such as a technician acceptance notice within 15 minutes and a revised arrival estimate whenever travel or a prior call changes the schedule by more than 30 minutes.

Use required photo and reading fields only where they help later decisions. For instance, the technician may need photos of a failed dual run capacitor, a split condensate drain line, a scorched contactor, or an iced evaporator coil, along with supply and return air temperatures. Those fields can later feed a digital HVAC inspection checklist without requiring staff to reconstruct the call from memory.

Give technicians a repeatable on-site sequence

The technician’s first task is to make the area safe and verify the complaint, then document the equipment condition before replacing parts. A simple sequence is: check for visible water, overheating, damaged wiring, or abnormal odor; identify the unit and serial information; verify thermostat demand; inspect disconnects and breakers; then test components appropriate to the equipment. The SOP should leave room for judgment, but it should require notes on what was observed and what was ruled out.

Specify the readings that must appear on an emergency ticket when applicable. For cooling equipment, that may include indoor return and supply temperatures, outdoor air temperature, thermostat setting, voltage at the contactor, condensate condition, and refrigerant readings interpreted against the unit’s refrigerant type and manufacturer data. For heating equipment, record thermostat demand, fuel or electrical supply status, ignition sequence observations, filter condition, blower operation, and any fault code displayed on the control board.

Set authorization limits in writing so the technician knows when a repair can proceed and when approval is needed. One operation might allow repair parts and labor up to $250 for an occupied-space restoration, require approval from $250 to $750, and require a separate estimate above $750 or when a compressor, heat exchanger, blower motor, or control board is implicated. The exact amounts can be changed, but the decision path should not be invented during an overnight call.

Close the call with records, communication, and a next action

Do not treat restored operation as the final step. The closing record should state arrival and departure times, diagnosis, parts used, measurements taken, repairs completed, equipment operating status, temporary measures, unresolved risks, and recommended next action. If a system is running after a temporary repair, write what makes it temporary: for example, a patched condensate line, a capacitor replacement on a 14-year-old condensing unit, or a coil that needs cleaning during a scheduled visit.

Review completed emergency calls once a month for missed response targets, repeat calls within 30 days, parts that were unavailable, and equipment that repeatedly receives temporary repairs. Revise the call script, truck stock list, authorization thresholds, and priority definitions when those records expose a recurring delay. A procedure becomes dependable when each emergency call leaves information that makes the next one clearer.