Show Notes
The maintenance gap
A chiller failing on the hottest day of August is not just an equipment problem. It can be the result of months of deferred work, missed warning signs, or recurring failures treated as isolated events. In this episode, a senior property manager and a chief building engineer explain why buildings fall into reactive maintenance—and how teams can replace emergency spending with a more deliberate, evidence-based approach.
Reactive, preventive, and predictive maintenance
- Reactive maintenance starts after something breaks.
- Preventive maintenance schedules tasks such as belt and filter replacement or calibration checks.
- Predictive maintenance uses data such as vibration and temperature trends to identify deterioration before failure.
A calendar alone does not make a building preventive. When budgets tighten or teams are stretched, scheduled tasks can slip. A plan may exist on paper while the actual operating model remains reactive.
What deferred work really costs
One example involved air-handling-unit belts. A belt costing $100 could have been replaced during a planned shutdown. Instead, a belt snapped, wrapped around the shaft, and damaged the motor, creating a $5,000 repair and two days of downtime in summer. The cost included more than parts: tenants were left without normal service and had to deal with the disruption.
Another building lost cooling for three days after a pump failed on a holiday weekend. The part cost $12,000, while the total bill approached $40,000 after overtime and other costs. Maintenance logs showed the pump had been overheating for months. Sensors were installed, but nobody was monitoring them. The warning existed; the operating process failed to act on it.
Why prevention is deprioritized
Owners often focus on this year's operating expenses, while the risk created by deferred work accumulates over time. Property managers are caught between budget expectations and their knowledge that postponement can become a much larger operational problem. The discussion also points to a timing issue: teams may wait until equipment is already failing to request funds. At that point, the work is more likely to be treated as an urgent capital expense than planned maintenance.
The guests discuss both budget pressure and trust as obstacles. Prevention may not be prioritized, and leaders must make a convincing case before a crisis. Data can make that case more effectively than a general request for more maintenance funding.
Use failure patterns to find root causes
Work-order history can reveal repeated failures that should not be dismissed as bad luck. One pump was replaced more than once because it kept overheating. Reviewing the data revealed that the cooling coil was undersized. Correcting that underlying issue stopped the recurring problem. The lesson is to diagnose the system around a failed component, not just replace the component again.
When presenting work to ownership, frame the decision in terms of risk and lifecycle cost. The episode gives the example of explaining that a $10,000 investment now could avoid a likely $50,000 emergency next year, along with potential tenant disruption. Support the request with failure history and trends, rather than relying on abstract warnings.
A chiller turnaround built on evidence
A property faced recurring summer chiller trips and repeated manufacturer overtime calls. The team reviewed the data and identified dirty condenser coils, an incorrect refrigerant charge, and wrong control settings. They introduced quarterly maintenance. The following summer, the chiller ran without a hiccup. The owner had budgeted $30,000 for emergency repairs; preventive work cost $8,000.
That result changed the conversation. The team showed the evidence, explained the cost of doing nothing, and delivered on its commitment. Preventive maintenance became easier to view as an investment that protects the asset and reduces operational risk.
Practical steps for property and facilities teams
- Track repeat failures and investigate patterns; a problem occurring more than twice deserves attention beyond another repair.
- Ask vendors what they will do to prevent the next failure, rather than accepting a replacement recommendation without a prevention plan.
- Make the ownership case using risk, tenant impact, and lifecycle cost—not only the immediate repair price.
- Start with one problematic piece of equipment, implement a preventive plan, document the results, and use the success to expand the approach.
The maintenance gap is real, but it is not inevitable. Better use of work orders and sensor data, timely investment, and a focus on root causes can help teams move from paying for emergencies to preventing them. Listen to the full episode for more practical discussion of building operations.
The emergency repair is often the end of a longer story
A chiller stops on the hottest day of August. A pump fails over a holiday weekend. The building team finds a contractor, authorizes emergency work, and restores service as quickly as possible. Yet the failure itself may be only the final chapter in a chain of missed maintenance, ignored data, and delayed decisions.
That is the maintenance gap: the distance between knowing that equipment needs attention and consistently doing the work before it becomes urgent. In this episode, a senior property manager and a chief building engineer explain why reactive repairs are expensive not only because emergency labor and parts cost more, but because downtime affects tenants and operations.
A maintenance calendar is not enough
Reactive maintenance happens after a breakdown. Preventive maintenance schedules work—replacing belts and filters, checking calibration, and completing service at planned intervals. Predictive maintenance adds condition data, such as vibration and temperature trends, to identify developing problems before failure.
Many buildings believe they are preventive because they have a schedule. But when budgets are cut or teams are stretched, preventive tasks are often the first work to slip. A schedule that is routinely postponed can amount to reactive maintenance with a calendar attached.
Small parts can create large consequences
One example from the episode shows how quickly deferred work can compound. An air-handling-unit belt cost about $100 and could have been replaced during a scheduled shutdown. The replacement was pushed off because the unit appeared to be running fine. When the belt eventually snapped and wrapped around the shaft, it damaged the motor. The repair reached $5,000, and the unit was down for two days in the middle of summer.
For tenants, the problem was not an accounting line. It was an uncomfortable workplace and a service failure. The direct cost of a part or repair is only one piece of the cost of deferral.
A separate pump failure illustrates the same point at a larger scale. The building lost cooling for three days over a holiday weekend. The part alone cost $12,000, but the total bill approached $40,000 after overtime and related costs. A later review of maintenance logs showed months of overheating. Sensors were present, but no one was watching them. Having data available did not create value until someone monitored and acted on it.
Budgets and timing shape the outcome
Property teams operate under pressure to keep current-year operating expenses low. Owners may see a maintenance reduction as a saving, while the risk accumulates into a future emergency. Property managers know the work is needed but must also meet owner expectations.
The discussion adds an important nuance: teams sometimes wait too long to ask for funding. When equipment is already failing, the request arrives in crisis mode and may become a larger capital expense. The guests also point out that owners need more than general warnings about risk. They need evidence, clear costs, and confidence that the team will deliver.
Turn work-order history into a business case
Repeated failures are signals. If the same equipment keeps breaking, tracking work orders can help teams find the cause instead of paying for the same repair again. In one example, a pump continued to overheat despite replacement. Reviewing the data revealed an undersized cooling coil. Correcting that underlying condition resolved the recurring issue.
When presenting a request to ownership, translate maintenance into business terms: risk, potential emergency expense, tenant disruption, and lifecycle cost. The episode offers a sample framing: spending $10,000 now may avoid a high probability of spending $50,000 on emergency repairs the next year, in addition to possible disruption. Use the property's own evidence to support estimates. The important shift is from “we need maintenance money” to “here is the exposure this work can reduce.”
A chiller plan that changed the conversation
One property experienced chiller trips every summer and recurring overtime calls to the manufacturer. The team examined the data and found dirty condenser coils, an incorrect refrigerant charge, and control settings that were wrong. These were preventable conditions, not an unavoidable seasonal pattern.
The team implemented quarterly maintenance. The next summer, the chiller operated without a hiccup. The owner had budgeted $30,000 for emergency repairs, while the preventive maintenance cost $8,000. The outcome gave the team a concrete success story: the case for prevention was no longer theoretical. They had shown the data, delivered the work, and reduced the expected emergency burden.
Start with one system and prove the value
Facilities teams do not need to transform every building system at once. The episode recommends beginning with one problematic asset and making a focused plan. Track repeat failures. Ask vendors what they are doing to prevent the next one, not just how they will replace the failed component. Investigate root causes and document whether the intervention works.
Once a team can show results for one system, that evidence can support broader investment. This approach also builds trust: ownership sees a defined problem, a reasoned intervention, and a measurable outcome rather than an open-ended request.
Prevention protects operations
Preventive maintenance is not simply a line-item expense. It is a way to manage the risk of emergency bills, equipment downtime, and tenant frustration. The best operational outcome may be the one nobody notices because the system kept running.
For property managers, facility leaders, and building engineers, the useful first move is to start the conversation before failure makes the decision for you. Listen to the full episode for examples and practical questions that can help your team shift from reacting to preventing.
Frequently Asked Questions
How can a property team tell whether it is doing preventive maintenance?
A schedule alone does not prove that maintenance is preventive. The episode distinguishes scheduled tasks such as belt replacement and calibration checks from repairs made after breakdowns, and says that postponed scheduled work can leave a building reactive in practice. Predictive maintenance goes further by using condition data such as temperature trends.
What can repeated equipment failures tell a facilities manager?
Repeated failures may point to an unresolved root cause rather than bad luck. The guests describe a pump that continued overheating until the team reviewed the data and found an undersized cooling coil. Correcting that condition stopped the recurring problem, instead of simply replacing the pump again.
How should a property manager make the case for maintenance funding?
Present the request in terms of risk, evidence, and lifecycle cost rather than only the immediate maintenance bill. The episode recommends using repeat-failure records and trend data to explain the cost of doing nothing, including possible emergency repairs and tenant disruption. Starting with one asset can also create a success story.