Heat Where Nobody Looks: Auditing Frost Protection Circuits Before the First Freeze

Frost protection is one of those building services that earns its keep by doing nothing visible. A trace-heated pipe runs, a frost stat in a plant room, a heater battery on an external louvre — all installed for good reason and then, quite reasonably, left alone. The difficulty is that "left alone" often becomes "left on". By the time the first sustained cold spell arrives, circuits that should operate for a few hours on the coldest nights can be running continuously, adding a quiet but persistent load to the winter baseload.

For cost-conscious organisations, the risk is not that frost protection exists. It is that nobody knows how much energy it uses, when it operates, or whether the controls still do what the commissioning sheet said they would. A disciplined audit before the cold snap is far easier than explaining a January baseload variance after the fact.

Why frost protection becomes a hidden cost

Frost protection load rarely appears as a named line on a budget. It is absorbed into the general power line of a half-hourly supply, or into a landlord's service charge, or into a facilities maintenance contract where the only test is whether the pipework survived. That invisibility has consequences. Thermostats drift, sensors are relocated during refurbishment, local isolators are left in the "hand" position after a maintenance visit, and control interlocks are bypassed because a contactor tripped on a cold Friday afternoon.

The result is a load that behaves less like a safety system and more like a permanent small heater. Across a site with substantial external pipework, tank rooms, air-handling units and standby generator enclosures, the aggregate effect can be material. It is not unusual for a plant-heavy site to find that winter baseload is 10–20% above the summer equivalent, with a meaningful share attributable to circuits that were never meant to run flat out.

Start with the half-hourly profile

Before touching a single thermostat, establish what the data says. Pull half-hourly consumption for the previous winter and the preceding summer, and compare the overnight baseload — the period between roughly midnight and 05:00, when production and occupancy loads are at their lowest. If the winter overnight baseline is consistently higher, and the gap cannot be explained by extended shifts, lighting or process work, frost protection should be on the shortlist.

A useful next step is to normalise against heating degree days. Frost protection load should correlate with cold weather, not with the calendar. A circuit that draws the same power in a mild October night as in a hard February frost is not being controlled by temperature; it is being controlled by a switch that somebody left closed.

Look also at the shape of the profile. True thermostatic control produces a stepped or modulated load as the outdoor temperature falls. A flat, unvarying overnight block is the signature of a manual override or a failed thermostat.

Sub-meter the protected circuits

Whole-site data can only take you so far. The next stage is to identify the circuits themselves. Trace heating is usually supplied from dedicated distribution boards, often labelled with a reference to the pipe run or the external area served. Those labels may be out of date, so a physical trace from the board to the circuit is worthwhile.

Temporary logging is often the most practical approach. Clamp-on current loggers on the outgoing ways of the relevant board, left in place for two to four weeks, will show exactly when each circuit operates and how much it draws. Permanent sub-metering is the better long-term answer where circuits are numerous or where the site intends to include frost protection in its energy baseline, but a temporary exercise is usually enough to establish the facts.

Record what you find in a simple register: circuit reference, area served, rated load, control type, observed run hours and condition. That register becomes the basis for both the savings case and the maintenance schedule.

Check setpoints, sensors and interlocks

The controls are where most of the money is won or lost. Frost stats should be set to the temperature the pipework actually needs — commonly around 5°C for water services, with a suitable deadband to prevent short cycling. Setpoints that have crept up to 10°C or higher, often in an attempt to cure a nuisance trip, will increase run hours significantly.

Sensor placement matters as much as the setpoint. A frost stat mounted next to a warm plant-room door, or a pipe sensor that has come loose from the pipe surface, will read the wrong temperature and call for heat when none is needed. Check that sensors are fixed, insulated where appropriate, and located in the coldest part of the protected run.

Interlocks deserve particular attention. Frost protection should usually be enabled by an outdoor thermostat or a building management system schedule, and inhibited when the plant it protects is isolated or the space is above a threshold temperature. Look for local switches left in "on", contactors held closed by manual test buttons, and BMS overrides that were applied for a one-off event and never removed.

Quantify before you act

The savings case need not be elaborate. Take the measured load of each circuit, multiply by the run hours observed in the previous winter, and compare that with a realistic controlled regime. A single 3 kW trace-heated run operating continuously for 2,000 hours consumes 6,000 kWh; the same run under thermostatic control might operate for 600 hours, saving 4,200 kWh. Across several circuits the figures add up quickly, and they can be presented alongside the capital cost of thermostats, contactors or metering.

Where a circuit has failed entirely, the calculation runs the other way: the cost of repair against the risk of a burst pipe, water damage and business interruption. Frost protection is not an area for false economies, but it is an area where correct control and a functioning thermostat are almost always cheaper than constant operation.

A pre-winter routine

The practical sequence is straightforward. Review the previous winter's overnight baseload against summer. Identify and label the protected circuits. Log them for two to four weeks. Test each thermostat and sensor. Confirm interlocks and BMS schedules. Correct setpoints, replace failed components and remove overrides. Then re-log to confirm the new operating pattern and update the energy baseline accordingly.

Done once, this work establishes a register that can be revisited each autumn. Done well, it keeps a necessary safety system from becoming an unnecessary standing charge — and ensures that when the cold weather does arrive, the heat is going only where it is needed.