Small manual overrides raise energy bills because they stay in place long after the reason for them has passed. A room setpoint lowered ahead of a large delivery, a condensing pressure raised during a cold snap, or an extra defrost added to clear one frosted coil can each make equipment work harder for months. Because the system keeps running and no alarm fires, the only symptom is a higher bill. Catching these changes takes a record of every override, a regular review of what is still active, and continuous fault detection that flags drift as it happens.
Most of these changes are perfectly reasonable when they are made. Operators adjust settings to protect products and keep equipment running, and those adjustments often work exactly as intended at the moment. The problem is the missing second step, the moment when someone puts the system back.
How a Temporary Change Becomes Permanent
Operators make adjustments for good reasons: a product receiving window, a temporary equipment issue, a complaint from a customer, or an unusual weather pattern. The adjustment solves the immediate problem, the shift ends, and the change rolls into the next week without anyone noting that it was meant to be temporary.
Shift handovers make the problem worse. A note about a temporary change may sit in a logbook that the next crew never reads, or it may never be written at all. After a few rotations, nobody on site remembers that the setting was supposed to change back.
The costs build slowly. A colder room target or a higher pressure limit adds a small amount of compressor work every hour, and that work continues through nights, weekends, and holidays when nobody is watching the energy profile. Multi-site operators face the same issue at greater scale, since each facility accumulates its own collection of local adjustments that headquarters cannot see.
A closed loop system does exactly what its setpoint tells it to do. If an operator lowers a room target ahead of a large inbound load, the controller will hold that lower temperature indefinitely, measuring, comparing, and correcting with perfect discipline toward a target nobody intended to keep. From the control system’s point of view, everything is working, so nothing raises a flag.
That is what makes forgotten overrides so persistent. Equipment failures produce alarms; setpoint drift produces only higher consumption, spread evenly across every hour of operation.
The Evidence That Control Faults Linger
Research from commercial buildings shows how common and durable these faults are. A Lawrence Berkeley National Laboratory study of HVAC fault prevalence in commercial buildings analyzed multi-year monitoring data for over 60,000 pieces of HVAC equipment across more than 90 fault types. The researchers found that 21 air handling unit faults were reported on 20% or more of the units in the dataset, and 18 of those faults persisted for more than 20% of the time period covered.
On any given day in that dataset, 40% of air handling units and 30% of air terminal units had a reported fault of some kind. Commercial HVAC differs from industrial refrigeration, but the pattern carries over: control faults accumulate quietly and stay in place until someone looks for them. The same tendency appears wherever control settings can be changed faster than they are documented.
Why Refrigeration Pays a Higher Price
Refrigerated facilities are especially sensitive to small control changes because their compressors run for long hours against demanding loads. A study on energy management in cold chain food storage, published in Frontiers in Sustainable Food Systems, reports that for every 1°C increase in condensing temperature, the compressor uses between 2 and 4% more energy. The same study notes that actively managing defrost frequency and duration can reduce annual system energy use by approximately 3%.
Those percentages look modest until they are multiplied across a large load. Research presented at the IBPSA Building Simulation 2023 conference on refrigerated warehouse energy, with co-authors from Lawrence Berkeley National Laboratory, states that the electricity demand from refrigerated warehouses accounts for approximately 16% of the electricity consumption of the food industry.
| Small change, steady cost For every 1°C increase in condensing temperature, a refrigeration compressor uses between 2 and 4% more energy, according to research published in Frontiers in Sustainable Food Systems. |
| Common override | Why it gets made | How it raises energy use |
| Room setpoint lowered | Pre-cooling for a large inbound load | Compressors run longer to hold a colder target |
| Condensing pressure raised | Stabilizing operation during cold weather | Higher condensing temperature increases compressor energy |
| Extra defrost cycles added | Clearing ice on one problem coil | Added heat load and compressor recovery time |
| Equipment forced to manual | Troubleshooting a fault | Automatic staging and optimization stop working |
| Alarm limits widened | Silencing nuisance alarms | Real drift goes unnoticed for longer |
Overrides also interact. A lower room setpoint increases the load on the system and can lead to more frequent defrost needs, which add heat for the compressors to remove. Widened alarm limits deserve special scrutiny, because they remove the safety net that would otherwise catch other drift.
Finding the Overrides Nobody Remembers
Some facilities find forgotten overrides only during an energy audit or a commissioning project every few years. By then, the waste has already accumulated. Continuous detection shortens that window considerably.
The American Council for an Energy-Efficient Economy’s topic brief on building energy management control systems describes fault detection and diagnostics as a continuous commissioning tool that allows systems to be fine-tuned on a more regular basis. It cites a study of 26 organizations using fault detection across 550 buildings that reported 8% median savings, and it describes a facilities team being alerted when a component drifted and operated outside its programmed parameters.
Industrial operators can apply the same discipline with a few practical habits. The register matters most when it includes an expiration date, because a change with a built-in end point prompts a decision, while a change without one simply persists:
- Keep an override register. Log every manual change with the reason, the person responsible, and an expiration date.
- Review active overrides on a fixed schedule. A short weekly check catches most changes before they become permanent.
- Compare live setpoints with an approved baseline. Any difference should have a documented reason.
- Trend the variables that drive energy. Condensing temperature, suction pressure, defrost counts, and compressor run hours reveal drift quickly.
- Use automated fault detection rules. Let software flag setpoints and equipment states that have moved outside their normal range.
Small Changes Deserve Systematic Attention
No single forgotten override will break an energy budget. The cost comes from many small changes, each reasonable when made, adding up across rooms, compressors, and sites over months and years.
Facilities that treat setpoints as controlled settings, with an owner, a record, and a review date, recover much of that waste. The tools are straightforward: a register, a baseline, a regular review, and fault detection that watches continuously. Over time, the same discipline makes genuine equipment problems easier to spot, because the remaining deviations stand out clearly. The payoff is an energy bill that reflects how the facility is meant to run.
