Commercial HVAC systems rarely stay the way they were commissioned. Setpoints get overridden during a hot week and never reset, sensors drift, dampers stick, and schedules stop matching how the building is used. The plant still runs, so nobody complains, yet energy use and comfort slowly slide away from design intent. Retrocommissioning is a structured way to find and fix those problems in an existing building. This guide walks through a 90-day approach and shows how a maintenance management platform helps the fixes last.
HVAC Retrocommissioning: Get the Building Back to Design in 90 Days
Tune what you already own before buying anything new. A disciplined retro-cx process finds operational faults, fixes them, and builds the habits that stop them returning.
Why Buildings Drift From Design
Drift is gradual and usually invisible. These are the faults retrocommissioning teams look for first.
| Common fault | What it looks like | Operational effect |
|---|---|---|
| Overridden setpoints | Manual overrides left in the control system | Equipment runs outside intended conditions |
| Schedule mismatch | Systems start early or run after occupants leave | Energy used for empty spaces |
| Sensor drift | Temperature, pressure, or CO2 readings no longer accurate | Controls respond to wrong information |
| Simultaneous heating and cooling | Reheat and cooling coils fighting each other | Wasted energy and unstable comfort |
| Economizer faults | Dampers stuck or linkages disconnected | Free cooling lost, ventilation off target |
| Static pressure and flow resets disabled | Fans and pumps held at fixed high output | Excess fan and pump energy |
| Valve leakage | Valves passing when commanded closed | Unwanted heating or cooling |
The Four Phases Behind the 90 Days
ASHRAE Guideline 0.2 describes commissioning of existing systems in phases. The sequence below follows that logic in a quarter.
Planning
Set goals, select systems, gather drawings and control sequences, and agree who owns each task.
Investigation
Review trend data, test equipment, and list every finding with its likely cause.
Implementation
Fix findings, verify results, and record what changed.
Hand-off
Update documentation, train staff, and set monitoring so improvements persist.
A Week-by-Week 90-Day Timeline
Treat this as a template. Larger or older buildings may need longer investigation time.
- Weeks 1 to 2Scope and baseline. Pick the systems that matter most, collect utility history, and document current operating schedules and setpoints.
- Weeks 3 to 5Data review. Pull control system trends for air handlers, chillers, boilers, and pumps. Look for stuck signals, hunting loops, and odd schedules.
- Weeks 6 to 7Functional testing. Verify the suspicious items on site. Confirm sensors against calibrated instruments and stroke dampers and valves.
- Weeks 8 to 11Fix and verify. Repair mechanical faults, correct control programming, and recheck trends after each change.
- Weeks 12 to 13Document and hand off. Update sequences, record savings assumptions, train operators, and schedule follow-up reviews.
Track Every Finding Through to a Verified Fix
Turn the retro-cx findings list into assigned work orders with history. Start free or review your approach with our team.
Sorting Findings: Operational Fix or Capital Project
Retrocommissioning focuses on operations and low-cost repairs. Larger items are logged for planning rather than forced into the quarter.
Fix during the project
- Reset schedules to match occupancy
- Correct setpoints and reset strategies
- Recalibrate or replace failed sensors
- Repair linkages, actuators, and dampers
- Restore disabled control sequences
Log for capital planning
- Equipment past useful life
- Undersized or oversized plant
- Controls platform upgrades
- Envelope or ventilation redesign
What Data You Need Before Starting
Preparation is where many projects win or lose time.
- Utility bills. Electricity, gas, and water history for a baseline.
- Control system trends. Temperatures, valve and damper positions, fan speeds, and pressures at a useful interval.
- Control sequences. The intended operating logic, even if it is only partly documented.
- Equipment list. Make, model, age, and service history for each major unit.
- Occupancy patterns. Actual hours of use, not the hours printed on the lease.
- Complaint and work order history. Recurring comfort issues often point to root causes.
Why Savings Fade, and How to Prevent It
Retrocommissioning gains can erode when no one owns the follow-up.
- Lock in schedules and setpoints with a change record, so overrides are visible.
- Add sensor calibration and actuator checks to preventive maintenance.
- Review energy trends on a set cycle and reopen the findings list when drift returns.
Where a CMMS Fits in Retrocommissioning
The control system shows the fault. The maintenance system makes sure someone fixes it and checks it again.
| Retro-cx need | Oxmaint capability |
|---|---|
| Track each finding to closure | Work orders with priority, owner, and verification notes |
| Keep equipment context | Asset records with service history and documents |
| Prevent repeat drift | Preventive maintenance for sensor, damper, and valve checks |
| Field data capture | Mobile inspections with photos and readings |
| Show progress to management | Reports and dashboards on open and closed findings |
| Act on conditions | Condition-based workflows from monitored readings |
Frequently Asked Questions
How is retrocommissioning different from regular maintenance?
It looks at how systems operate against design intent, not just whether equipment runs.
Will it guarantee a specific energy saving?
No. Results depend on the building and its faults, so set expectations from your own baseline data.
Do we need new equipment first?
Usually not. The process aims at operational fixes, with capital needs logged separately.
How do we keep the results?
Assign owners and schedule checks. You can set up preventive tasks for the items that drift.
Can we see this workflow in practice?
Yes. Book a demo to walk through a findings-to-work-order flow.
Bring Your Building Back to Design and Keep It There
Give your team one place to log findings, schedule fixes, and prove the work was done.
