Do Your Building's HVAC Schedules Survive the Time Change?

Every fall, buildings around the region start heating an hour before anyone arrives and keep running an hour after everyone leaves, and it goes unnoticed because nothing is broken. Schedules are the least glamorous part of a mechanical system and the part with the most money sitting in it. An afternoon in the building automation system before the clocks change is the cheapest maintenance visit of the year, and unlike most efficiency work it requires buying nothing.

Why does the time change matter to HVAC schedules?

The time change matters because HVAC schedules are clock-driven, and a controller's clock is not automatically right. Equipment start and stop times, setback periods, optimum start calculations and holiday exceptions all key off the controller's internal date and time. If that clock shifts relative to actual local time, every one of those events moves with it. The building warms up an hour late on a Monday in November, or an hour early every day for five months. Nobody files a complaint about a building that was warm too early, which is why this survives so long.

Controllers still running an outdated daylight saving rule

Older controllers and standalone programmable thermostats frequently have daylight saving start and end dates hard-coded from an earlier rule set, and those dates have changed over the years. A controller that switches on the wrong weekend is off by an hour for however long it takes for someone to notice — often weeks. Newer systems handle it by synchronizing to a time source. Even then, the setting has to be enabled, the time zone still has to be correct, and a controller on an isolated network may have no time source at all.

The check is quick: read the date, time and time zone directly from the controller rather than from a front-end graphic that may be displaying your workstation's clock. Do this on every controller in the building, not just the main one. Mixed-vintage sites with a newer front end and older field panels are exactly where the hour goes missing.

Why does a dead clock battery scramble a building schedule?

Most controllers keep their clock running through a power interruption with a small onboard battery, and that battery has a finite life. When it dies, a power outage leaves the controller with a default date and time — and with schedules that now run on the wrong day of the week entirely. A building that starts its occupied cycle on Saturday and sits in setback on Tuesday morning usually traces back to exactly this. In rural areas with more frequent outages, like the areas around Meadowlands and Kerrick, it comes up more often than in town.

The related item is what the controller does when it loses its program entirely. Knowing whether your schedules and setpoints are backed up somewhere other than in the panel — and whether anyone has the backup file — is the difference between a fifteen-minute restore and a day of reprogramming from memory.

Holiday calendars from last year

Holiday schedules are usually entered as specific calendar dates, which means they expire. A calendar loaded two years ago with that year's dates has been silently doing nothing since. The building runs its normal occupied schedule on Thanksgiving, on the day after, and through the week between Christmas and New Year's. That means heating and ventilating an empty building at the coldest, most expensive time of the year. In a school, a church or a seasonal operation, the same mechanism runs whole unoccupied weeks at occupied setpoints.

Load the coming year's dates while you are in the system, and note which zones the holiday calendar actually applies to. It is common to find the calendar assigned to some air handlers and not others, so half the building observes the holiday and half does not.

Overrides nobody released

Overrides are the largest single source of wasted runtime in most small commercial buildings, because they are easy to set and invisible afterward. A timed override set to permanent during a cold snap two winters ago is still holding a zone at occupied setpoint. A tenant override button that latches. A point commanded in a service visit and never released. A damper left in hand position on a rooftop unit. None of these produce a complaint; they produce a bill.

What the building is doing and what to check in the controller

Symptom in the building	Likely cause in the controls
Warm an hour before anyone arrives, all season	Clock or daylight saving rule off by an hour
Occupied setpoints on a Sunday	Dead clock battery, wrong day of week after an outage
Full heat over a holiday week	Expired holiday calendar, or calendar not assigned to that unit
One zone always comfortable, others swinging	Permanent override on that zone
Building cold at open on the coldest mornings only	Optimum start disabled, fixed start time too late
Heating and cooling in the same hour	Overlapping setpoints or a stuck damper in hand
Ventilation running in an empty building	Fan schedule not tied to the occupancy schedule

Optimum start, and what it does when it is switched off

Optimum start is the routine that calculates how early to begin warming the building so it reaches setpoint exactly at occupancy, based on indoor temperature, outdoor temperature and how the building performed on previous mornings. With it enabled, a mild morning gets a short warm-up and a −17°F to −21°F morning gets a long one. With it disabled — and it often gets disabled during a complaint call and never restored — the building falls back to a fixed start time. That fixed time is set early enough to cover the worst morning of the year, so for the other several hundred mornings the building starts heating long before it needs to.

While you are in that part of the program, check the unoccupied setpoints themselves and the deadband between heating and cooling. A deep setback saves money right up until the point where the morning recovery takes so long that the fixed start time gets moved earlier. In a building with hydronic heat and significant mass it is easy to set back further than the system can recover from.

A short fall controls audit

1. Read the date, time, time zone and daylight saving setting at every controller, not just the front end.
2. Verify the clock battery status, and confirm where the program backup lives.
3. Load the coming year's holiday dates, and check which units the calendar is assigned to.
4. List every active override, find out why each exists, and release the ones that have outlived their reason.
5. Confirm optimum start is enabled and that the occupied and unoccupied setpoints and deadbands are what you intend.
6. Compare the schedule to how the building is actually used now, including any tenants whose hours have changed.
7. Pull a week of trend data afterward and confirm that equipment starts and stops when the schedule says it should.

Why controls work is the cheapest efficiency project in a building

Controls corrections cost less than any equipment measure because nothing gets purchased or installed — you are buying labor to stop a building from running when it does not need to. In a 9,000 to 10,000 heating-degree-day climate, hours of unnecessary runtime accumulate faster than almost anywhere else in the country, so the same schedule error costs more here than it would downstate. The same logic applies to the outside air side of the system, which is why a correctly configured economizer matters; our guide to economizer savings in a cold climate covers the changeover settings that get left wrong.

Fall is the natural time to do it because the rest of the heating season depends on it. It also pairs with the other pre-winter items: combustion service, getting a commercial boiler ready for inspection, and in high-bay spaces, checking that destratification fans are on a schedule that matches the heating equipment. Buildings without a full automation system are not exempt; a warehouse near Iron River running unit heaters on individual thermostats and timers has the same problems in a simpler form.

If nobody on staff has the software, the training or the time, this is straightforward work to hand off. It fits naturally into a commercial preventive maintenance visit, and where the system is older or partly abandoned, building automation and controls work usually pays for itself faster than any equipment upgrade on the list.