The first HVAC optimization pitch most facility managers hear goes something like this: "We'll raise your cooling setpoint by 2°F during non-peak hours and save you 5-8% on your electricity bill." It sounds reasonable. It's also about the lowest-leverage move in the optimization toolkit — and it crowds out the discussion about what actually moves the needle.
We spend a lot of time in early conversations with facilities teams explaining why we're not primarily a setpoint controller. That framing requires unpacking the fundamental difference between two categories of HVAC optimization: continuous setpoint adjustment and schedule-level restructuring. They operate on different timescales, they unlock different savings, and they have very different relationships to occupant experience.
What Setpoint Control Actually Does
Setpoint-based optimization adjusts the target temperature for a zone — typically within a dead band — in response to current conditions. The most common implementations: raise the cooling setpoint by 1–2°F during hours with low occupancy, lower the heating setpoint during the same windows, and execute small nudges during demand response events.
These are real savings. A 1°F setpoint increase on cooling reduces chiller energy by roughly 2–3%, depending on the COP of your equipment and ambient conditions. If you're doing this consistently across thousands of hours per year, it adds up. We're not dismissing setpoint control — it's a valid baseline move.
The ceiling, however, is low. Most well-run facilities have already set their dead bands appropriately. Getting from a 72°F cooling setpoint to 74°F is 4–6% savings. Going further risks comfort complaints. The practical optimization range from setpoint adjustment in an occupied commercial building is roughly 5–8% on cooling energy — not on total electricity consumption, just cooling. If cooling is 35% of your bill, you're talking about 1.5–3% of total.
What Schedule-Level Optimization Does Differently
Schedule restructuring is a different category of intervention entirely. Instead of adjusting what temperature you're targeting, you're changing when systems run, for how long, and how they sequence relative to each other. The savings potential is categorically larger because you're addressing the structural pattern of energy use, not trimming around its edges.
The three main levers here are: pre-conditioning timing, occupancy-synchronized shutdowns, and equipment startup sequencing.
Pre-conditioning timing means shifting the morning warm-up or cool-down cycle to start earlier, using the building's thermal mass to carry conditioning credit from cheaper off-peak hours into the occupied period. If your AHUs currently start at 6 AM to condition the building for an 8 AM occupancy load, but your load forecast shows a high-humidity day coming, starting at 4 AM at a lower intensity often costs less than starting at 6 AM and having the system run hard all morning. The total energy consumed can be similar, but the demand profile is flatter and the rate-sensitive peak load is lower.
Occupancy-synchronized shutdown is the inverse problem — most buildings run HVAC considerably longer into unoccupied periods than they need to. A building that closes at 6 PM but runs HVAC until 10 PM "just in case someone stays late" is wasting 4 hours of conditioning daily. With real occupancy data or reliable schedule data, you can track when the building actually empties and set shutdown to follow occupancy rather than precede it by an arbitrary buffer.
Equipment startup sequencing addresses a specific cost driver: the demand spike that occurs when large HVAC systems restart after an overnight setback. If you have three 200-ton chillers that all start within a 15-minute window, your interval peak at 6 AM can be your highest of the entire month — and it's entirely artificial. Staggering those starts by 20 minutes each costs nothing in comfort terms and can drop your monthly peak demand by 10–15% depending on your equipment mix.
Why the Savings Gap Exists
The rough comparison we use internally: well-executed setpoint optimization typically delivers 5–8% reduction in HVAC energy consumption. Well-executed schedule optimization typically delivers 15–25%. Why the gap?
Setpoint changes adjust the operating point within an already-running system. You're trimming efficiency at the margins of a machine that's already doing work. Schedule changes determine whether the machine does work at all during certain periods, and how much demand it places on the grid during the most cost-sensitive windows. The latter is structurally more impactful because your electricity bill is not linear — it's shaped by tariff structure, demand charges, and time-of-use pricing that all reward load shaping, not just load reduction.
Demand charges are the clearest illustration. If your facility pays a demand charge based on your highest 15-minute interval per month, a small improvement in peak profile is worth more per kWh saved than any amount of base-load reduction during off-peak hours. Schedule-level optimization directly targets peak profile. Setpoint adjustments have minimal impact on it.
The Feature Engineering Problem
Building effective schedule optimization is harder than building effective setpoint control, which is probably why the market has more setpoint products than scheduling products. To optimize schedules, you need to predict load accurately enough to make decisions hours in advance — which requires good weather data, occupancy signals, and equipment state awareness. You can implement a setpoint controller with fairly simple rule-based logic and see reasonable results. Schedule optimization requires a real forecasting layer underneath it.
This is why Voltpathio's core architecture is built around the forecast first, with schedule generation as the output layer. The prediction pipeline — weather normalization, occupancy modeling, equipment state tracking — needs to be solid before schedule recommendations have any credibility. We ran into early versions of our system where the schedule recommendations were technically correct given the forecast but the forecast itself was wrong, and the resulting recommendations wasted energy. Getting the forecasting right took longer than we expected.
These Two Approaches Are Not Mutually Exclusive
We're not arguing you should ignore setpoint control. The highest-performing facility energy programs use both: schedule-level optimization to reshape the load profile and reduce peak demand, and intelligent setpoint management to trim efficiency during the periods when systems are running. They operate at different timescales and address different cost drivers.
The practical sequencing we'd recommend: fix your schedule structure first. If your startup sequencing is creating artificial demand spikes, no amount of setpoint tuning will offset that cost. If your building is conditioning empty space for hours every night, that's the first thing to address. Once those structural patterns are corrected, setpoint optimization on top of a well-structured schedule delivers clean incremental gains without the risk of creating new problems.
Where we see facilities go wrong is when they implement setpoint optimization as the main initiative — because it's lower-friction to deploy — and then wonder why their bills aren't improving as much as projected. Setpoint optimization is easy to sell because it requires no schedule disruption, no advance forecasting, and minimal operator involvement. Schedule optimization requires all three. But the 3x savings multiple is real, and it comes directly from addressing the right problem.
What This Looks Like in a Real Deployment
Take a mid-size distribution warehouse in the Southeast — roughly 180,000 square feet, operating two daily shifts with HVAC that runs continuously on a fixed timer schedule. Before any optimization, the facility's highest-cost period is typically the 90 minutes following the overnight setback recovery: all the rooftop units pulling hard simultaneously, plus lighting and dock equipment coming back online, creates a demand interval that sets the monthly rate for the whole billing period.
Addressing this with setpoint control alone — raising the morning setpoint slightly — does almost nothing to the demand peak timing. The equipment is still all starting simultaneously. The right fix is staggering the rooftop unit startup sequence and using the building's overnight thermal retention (which is substantial in a well-insulated distribution structure) to reduce how aggressively the system has to pull during the first occupied hour. That's a schedule change, not a setpoint change. The demand charge impact is typically larger in one month than setpoint optimization would achieve in six.