Most university HVAC temperature policies look simple: a few occupied setpoints, defined hours, and a line about “energy efficiency.”
But when we compare real campus policies side-by-side, a pattern jumps out:
The biggest savings rarely come from tweaking occupied setpoints. They come from what we do when no one is there.
That’s the power of the wide band: it widens the temperature range during unoccupied hours to reduce runtime, reduce cycling, and protect equipment.
The hidden consensus: occupied is narrow… unoccupied is wide
Across peer institutions, occupied comfort generally clusters around:
- Heating: ~66–72°F
- Cooling: ~72–80°F
But after hours, many campuses allow much wider limits:
- Heating setback: ~50–55°F
- Cooling setup: ~80–85°F
That’s where the budget moves.
Why the DMV is different (Zone 4A)
In the DMV (DC–Maryland–Virginia), we’re a mixed-humid climate. That means:
- Humidity control matters as much as temperature
- Shoulder seasons (spring/fall) are where energy gets wasted
- Aggressive setbacks work—only with guardrails
If we widen the band without humidity and freeze logic, we can “save energy” and end up with mold risk, comfort complaints, and rework.
A DMV-optimized setpoint strategy (simple, operational)
Here’s the tiered approach that aligns policy intent with how BAS actually runs:
- Occupied: 68–70°F heat / 74–76°F cool
- Standby (after-hours): 62–64°F heat / 78–80°F cool
- Unoccupied: 55–58°F heat / 82–85°F cool
Two non-negotiables:
- Deadband discipline: minimum ≥ 4°F to prevent heating/cooling overlap and hunting
- Humidity guardrail: keep RH ≤ 60% (and respond when RH climbs)
Here’s the part most policies miss: proof
A campus can publish excellent targets and still waste energy if the BAS doesn’t execute them reliably.
That’s why we treat setpoint behavior as a commissioning deliverable, not a “looks good” assumption.
Our “Verify Set-Point Behavior” approach requires:
- verifying Occupied / Standby / Unoccupied transitions
- confirming the active setpoints match intended targets
- checking timed overrides + auto-revert
- catching hidden priority locks
- proving freeze + humidity safeties override setbacks when needed
- trending critical points at 1–5 minute intervals during transitions
The bottom line
The thermostat isn’t the strategy. Verified behavior is.
The wide band is the engine of campus savings, but commissioning is the steering wheel that ensures our policy intent becomes operational reality.
If your campus has a temperature policy, here’s the real question:
Can we prove the building actually follows it, after hours, on weekends, and during breaks?
