Spring Recommissioning Checklist: Preparing Your Buildings for Cooling Season

Spring is a natural reset point for building operations. Heating season winds down, cooling loads begin climbing, and the systems you haven't touched since last fall are about to carry a lot of weight. For most commercial portfolios, that transition happens fast. The window between "we probably should check the chillers" and "we're getting tenant complaints about temperature" is often shorter than teams might realize.

This checklist is designed to help facilities managers and energy teams move through that window systematically, catching the issues that quietly erode cooling efficiency before peak demand arrives.

Why spring recommissioning matters

Cooling isn't a secondary concern in commercial buildings. According to the U.S. Energy Information Administration's 2018 Commercial Buildings Energy Consumption Survey, electricity used for cooling accounts for roughly 14% of total commercial building electricity consumption — about 170 billion kWh annually. Add ventilation (which largely exists to move cooled air) and that share climbs considerably.

The case for recommissioning before cooling season starts is also well-established. A meta-analysis of 163 existing building commissioning projects found median energy savings of 10% of whole-building consumption, with a median simple payback time of 1.7 years. A separate analysis found that recommissioning typically delivers improved comfort and energy savings in the range of 5 to 15%. Critically, these aren't retrofit numbers — they're achievable through operational improvements and controls tuning alone.

The most common culprit: drift. Setpoints change, overrides accumulate, schedules go stale. Systems that were optimized last fall are rarely still operating as configured by the time spring arrives.

The checklist

1. Review and reset heating-season schedules and setpoints

Before anything else, audit what your BMS is actually running. Winter schedules — extended heating windows, elevated setpoint bands, manual overrides from cold snaps — have a way of persisting well into spring. Common findings at this stage:

• Heating setpoints still elevated from February
• Overnight "warm-up" sequences running into occupied hours
• Manual overrides applied during the last cold spell, never removed

What to do: Pull current schedules and compare against your approved seasonal templates. Identify and clear any active overrides. Document what changed and why, so you're not rebuilding context in July.

2. Inspect and start up cooling equipment

Chillers, cooling towers, condenser water systems, and DX units all need attention before first use. Equipment that sat idle for months will surface issues that weren't visible in fall shutdown, and it's better to surface them in April than during a heat event in July.

Key checks:

• Chiller oil levels, refrigerant charge, and leak inspection
• Cooling tower basin condition, fill media, and water treatment startup
• Condenser water pump and valve operation
• DX unit coil condition and refrigerant inspection
• Vibration and noise checks on startup

If your building uses economizer operation, verify the changeover sequence is configured for cooling season; economizer controls left in winter mode can inadvertently bring in warm outdoor air and fight your cooling plant.

3. Verify air handling unit and terminal unit performance

AHUs are where a lot of cooling season waste originates. Dirty coils, failed sensors, and misconfigured sequences mean units work harder and longer than they need to.

What to check:

• Cooling coil condition — fouling on the coil surface directly degrades heat transfer efficiency
• Mixed air and supply air temperature sensors — calibration drift is common after a season of heavy use
• Minimum outdoor air damper positions and economizer control sequences
• Terminal unit (VAV box) operation — stroke each actuator and verify airflow calibration
• Static pressure reset schedules — many buildings still run fixed static pressure setpoints year-round, leaving energy on the table during mild weather

4. Audit cooling-season control sequences

Controls drift is one of the most underdiagnosed sources of cooling inefficiency. Sequences that looked correct in the BMS were often modified during last year's cooling season to address a complaint or a temporary condition and were never reverted.

Common issues to look for:

• Chilled water supply temperature reset schedules disabled or overridden
• Cooling lockout temperatures set too high or too low for current conditions
• Zone-level simultaneous heating and cooling — a persistent waste source in buildings with reheat
• Demand-limiting controls disabled after a manual override last summer

Pay particular attention to any sequence that interacts with a setpoint reset strategy. These are frequently the first things operators disable when a comfort complaint comes in, and rarely the first things they re-enable.

5. Check metering and monitoring coverage

Spring is a useful moment to confirm that your data infrastructure is ready for cooling season. Gaps in metering, submetering, or sensor coverage that were tolerable in winter can become tricky blind spots, particularly if you're trying to manage demand charges or respond to a tenant complaint with actual data.

What to verify:

• Chiller and cooling plant interval metering is reading accurately
• Zone temperature sensors are functional and correctly mapped
• Any BMS alarms disabled over winter are re-enabled and routed appropriately
• Utility rate schedules in your energy management platform are updated for the current year

If you use a building analytics platform (like Noda), review the last 30 days of data before cooling startup and look for anomalies — sensors reading zero, stuck values, or points that haven't updated. Better to find those now than when you're diagnosing a comfort complaint in August.

6. Benchmark last cooling season before this one starts

In a similar vein to the above: before the new season's data starts accumulating, lock in your baseline from last year. This gives you a clean reference point for measuring whether this year's recommissioning effort actually moved the needle.

Useful benchmarks to pull now:

• Peak cooling demand (kW) by building, by month
• Chiller plant efficiency (kW/ton) at various load points
• Cooling degree days vs. cooling energy — does the relationship look reasonable?
• Any months last year where cooling EUI was materially higher than expected

This step is easy to skip – but just as easy to miss if you do. If a tenant raises concerns about comfort or energy costs, having a documented pre-season baseline can turn a contentious argument into a productive conversation.

Beyond the checklist: the case for continuous commissioning

Spring recommissioning is valuable precisely because drift is real and cumulative. But a point-in-time tune-up — however thorough — only corrects the drift that's already happened. The moment the season starts, new overrides get applied, sequences get adjusted, and the process begins again.

That's the core argument for continuous commissioning (CCx): rather than catching drift once a year (or once every few years), you're catching it continuously. Where a traditional retro-commissioning event is a scheduled intervention, CCx is an ongoing practice, using live data trends and analytics to detect deviations from intended performance as they emerge, not months later.

The distinction matters operationally. A BMS is designed to execute control logic and surface alarms; it isn't designed to detect the kind of slow, persistent waste that accumulates between alarm thresholds. Simultaneous heating and cooling in a zone with a stuck reheat valve. A chilled water pump running at fixed speed when VFDs are available. A chiller staged incorrectly for current load. These are issues the BMS won't flag — but that show up clearly in historical trend data when you're looking for them.

Building analytics platforms that support CCx (like Noda!) close that gap. They track temperatures, pressures, valve positions, pump speeds, setpoints, and plant efficiency over time, and surface patterns that indicate drift, inefficiency, or deviations from design intent. When an issue is detected, the insight goes directly to the engineering team with enough context to act. The on-site team doesn't need to go hunting; the system tells them where to look and what to fix.

The practical impact is that buildings under continuous commissioning tend to hold their efficiency gains better than those relying on periodic tune-ups alone. Spring recommissioning remains important — it's the right time to do a structured physical inspection, clear overrides, and verify startup — but it becomes less of a recovery exercise and more of a confirmation that the system is already in good shape.

For portfolio operators managing multiple properties with lean engineering teams, that shift matters. It means less time diagnosing problems reactively, and more time for teams to act on insights proactively.

Final Thoughts

On the whole, the goal of spring recommissioning isn't to find problems — it's to find them before they find you. Most of the issues on this list are fixable in an afternoon. The ones you don't catch until July rarely are.

About Noda

Noda is a data and analytics company on a mission to make every building smarter, more efficient, and more sustainable. Recently ranked in the top 10 tech companies leading the charge on climate action, its AI-powered suite of products surface unique insights that empower real estate teams to reduce costs, decrease time spent on routine work, and find and act on opportunities to save energy and carbon. Discover how Noda's solutions can unlock the potential of your assets and accelerate the transition to net zero. Visit us at noda.ai to learn more.