The Maintenance Myth: When Preventive Schedules Miss the Real Failure Mode

The PM illusion: completed tasks do not guarantee reliability

A chiller can fail on a hot July afternoon even when every preventive maintenance task has been completed on schedule. The episode opens with this scenario to highlight the gap between a clean maintenance record and a system that is actually dependable. A logbook documents work performed; it does not prove that the work addressed the conditions causing failure.

James Rogers describes this as the “PM illusion”: treating a full schedule of completed tasks as evidence that equipment is healthy. Michael Harrington adds the property manager’s perspective. When cooling fails, tenants are concerned about comfort and disruption, not whether the maintenance records are up to date. Confidence is difficult to restore when a system fails despite apparently perfect records.

• Preventive maintenance schedules are useful starting points, not guarantees.
• Manufacturer recommendations reflect average conditions and typical usage; individual buildings are not necessarily average.
• A task’s timing does not explain which failure mode it is meant to prevent.

When the checklist misses the failure mode

James recalls a rooftop unit that received quarterly checks of refrigerant pressures and coil cleaning. The maintenance list was followed, but the drain line was not part of the inspection. A subtle slope issue allowed water to back up, corrode the drain pan, and leak into the ceiling. The leak shorted a control board, and the unit failed on a hot day.

The repair was straightforward: improve the slope and add a cleanout. The harder problem was that the drain line was invisible to a process focused only on listed tasks. The example illustrates why a checklist can be completed correctly while a consequential weakness remains untouched. A reliability review asks not only whether a task was done, but whether the relevant parts of the system and their likely failure paths were considered.

Buildings change, and maintenance assumptions can fall behind

Michael describes a tenant who added a small server room without notifying the property team. The HVAC system had been sized for the original layout, but the new equipment increased the cooling load. The system began running harder and breakdowns increased, while the preventive schedule remained unchanged.

The schedule assumed a static environment. In reality, people can change how space is used, move walls, or add equipment. If operators and property teams do not hear about those changes, maintenance decisions are made with incomplete information. The episode frames the information gap—not the maintenance team—as the underlying issue.

• Ask whether space use or equipment has changed since the last review.
• Establish a simple way for tenants to report planned additions or operational changes.
• Connect observations from tenants, operators, contractors, and maintenance staff.

Move from compliance to reliability

The guests recommend a practical shift: treat preventive maintenance as one part of understanding the system, rather than the end of the process. A completed checklist may support compliance, but reliability depends on recognizing what can fail under the building’s actual conditions.

• Ask what each task prevents. If the failure mode is unknown, the task may be happening by habit rather than as part of a clear reliability strategy.
• Build feedback loops. Talk with operators, tenants, and contractors. They may notice changes and symptoms that a standard list does not capture.
• Audit for blind spots. Review what is absent from the maintenance list and ask why. Consider the equipment as well as the space around it and how that space is being used.

Use recurring symptoms as a reason to investigate

The server-room change was discovered after the system kept tripping and a specialist was brought in. The specialist observed that the load profile did not match the original design. That finding led to a new tenant notification process: if tenants plan to add equipment, they should let the property team know. The stated purpose is awareness, not control.

Repeated symptoms can reveal that assumptions about the building no longer match reality. In this example, bringing in a specialist helped identify the difference between the original design and the current load. A notification process then gave the team a way to learn about future changes sooner.

A practical first step for building teams

Start with one critical system and ask: “What failure mode am I not preventing?” If the team cannot answer, investigate further. Share the question with colleagues so that people who interact with the system can contribute what they have observed.

The episode’s central point is direct: do not stop at following the schedule. Understand what the schedule is intended to prevent, keep information flowing as buildings change, and look for the blind spots the checklist leaves behind. Those habits can help teams focus on reliability rather than simply recording completed work.

In this episode

• Why manufacturer schedules are starting points rather than guarantees.
• How an overlooked condensate drain issue led to water damage and a control-board failure.
• How an unreported server-room addition changed an HVAC system’s cooling load.
• Why tenant and operator feedback belongs in maintenance planning.
• Three steps for examining a preventive maintenance program for reliability gaps.

Why preventive maintenance can miss the real failure

A maintenance log can show that every scheduled task was completed and still fail to tell you whether a building system is ready for the conditions it faces. That is the maintenance myth at the center of this episode: the belief that following the manufacturer’s preventive schedule is enough to make equipment reliable.

The episode begins with a chiller failing during a hot July afternoon, despite months of on-time preventive maintenance. The point is not that the team neglected its work. The point is that the work recorded on paper did not necessarily address the failure mode developing inside the system. James Rogers calls this the “PM illusion”: a completed logbook can look reassuring even when it says little about what is actually happening.

For a commercial property manager, that distinction is tangible. When cooling stops, tenants experience discomfort and disruption. They are not reassured by a record showing that maintenance was performed if the system they depend on is down. Reliability has to mean more than a schedule kept current.

A schedule is a starting point, not a guarantee

Manufacturer maintenance recommendations are based on average conditions and typical usage. But individual buildings have their own operating conditions, patterns of use, and changes over time. A schedule tells a team when to perform certain tasks; it may not explain which specific failure mode each task is intended to prevent.

That leaves an important question for facilities and property teams: what problem does each task actually address? Changing filters or checking pressures may be useful, but those actions do not automatically cover every component or condition that could bring a system down. A thorough-looking checklist can still have blind spots.

The episode’s rooftop-unit example shows how that can happen. The unit received quarterly checks of refrigerant pressures and coil cleaning. The team followed the list, but the condensate drain line was not on it. A subtle slope issue allowed water to back up. The water corroded the drain pan, leaked into the ceiling, and shorted a control board. The unit then failed on a hot day.

The eventual fix—improving the slope and adding a cleanout—was simple. The missing piece was attention to the drain line. Because the checklist did not include it, the issue remained outside the routine inspection. The example does not make checklists useless; it shows why teams should not mistake a checklist for a complete understanding of the system.

Building use changes, too

Maintenance planning can also fall behind when the building itself changes. Michael Harrington shares an example of a tenant who added a small server room without informing the property team. The HVAC system had been sized for the original layout. With additional equipment in the space, its cooling load increased. The system ran harder, and breakdowns became more frequent, while the preventive maintenance schedule stayed the same.

The maintenance plan was operating on an old assumption: that the environment was static. Commercial spaces are not always static. Tenants may add equipment, change usage patterns, or move walls. If those changes are not communicated, the people responsible for maintaining the building may not know the conditions the equipment is now expected to handle.

In the server-room example, the team caught the issue after the system kept tripping and a specialist was brought in. The specialist saw that the load profile did not match the original design. That diagnosis led to a simple notification process: tenants should let the property team know if they plan to add equipment. The stated goal is not to control tenants; it is to make sure the people responsible for the building have the information they need.

Close the information gap

The episode describes the information gap as the problem—not the maintenance team. Operators, tenants, and contractors may each see different details. A tenant knows when their space is changing. An operator may notice a developing symptom. A contractor may identify an issue during service. Without a way to share those observations, maintenance teams may keep following a plan based on incomplete assumptions.

Feedback loops give those observations somewhere to go. Talking with operators, tenants, and contractors can reveal changes and warning signs that a standard checklist does not capture. A notification process for planned equipment additions is one example. Asking what has changed in a space since the last review is another.

That approach makes maintenance more than a recurring ritual. It connects scheduled work to the actual environment in which the equipment operates. The result is a better chance of identifying a mismatch before it becomes an unexpected interruption.

Three questions for a reliability-focused PM program

The guests recommend practical steps for moving from a compliance mindset toward a reliability mindset:

• What failure mode are we preventing with this task? If the answer is unclear, the team may be performing work without understanding its purpose.
• Who sees changes or symptoms that the checklist misses? Build ways to hear from operators, tenants, and contractors, and make it easy to report relevant changes.
• What is not on the list, and why? Audit the maintenance program for blind spots. Look beyond the equipment itself to the surrounding space and how it is being used.

These questions do not require a team to discard its existing schedule. They help teams test whether the schedule reflects their building’s real conditions and whether important failure paths are left out.

Start with one critical system

A practical starting point is to choose one critical system and ask: “What failure mode am I not preventing?” If the team cannot answer, dig deeper. Share the question with colleagues so that people who work with or around the system can add what they have observed.

Preventive maintenance records matter, but they are not the same as reliability. A system can have a clean record and still be exposed to a failure mode outside the checklist or to operating conditions that have changed since the last review. Understanding those gaps means looking at the system, listening to the people around it, and checking whether the maintenance plan still fits the building as it is used now.

For more on the maintenance illusion, hidden failure modes, and practical ways to make maintenance more reliability-focused, listen to the episode of Built, Wired & Secured.