Preventative maintenance programs get started every year in school districts across the country. A new director comes in with energy. Or a failing HVAC system finally forces the conversation. Or someone reads a report about the $270 billion sitting in K-12 deferred maintenance backlogs and decides this year will be different. The program gets launched. And then, somewhere between October and December, it quietly stops.
The people involved aren't incompetent. The intentions are real. What fails isn't the team — it's the design of the program itself. Because most school PM programs are built for a version of a school that doesn't actually exist.
The steady-state assumption
Commercial CMMS platforms — the tools most facilities teams eventually adopt — were designed for office buildings, manufacturing plants, and property management firms. These environments run on a relatively predictable cadence. Buildings are occupied year-round. Staff is consistent. The maintenance rhythm can be structured around a steady operational baseline.
School buildings don't work that way. A school is a facility that operates at near-maximum intensity for nine to ten months, then drops to near-zero for six to ten weeks. It hosts 600 or 800 or 1,200 people every day from August to June, and then becomes a quiet building with a skeleton crew and a summer project list. The maintenance needs, the staffing, and the operational reality change dramatically across those cycles.
September brings the chaos of a new school year — students, new teachers, deferred issues from summer that didn't get fixed, HVAC systems running at full load for the first time in months. October starts to settle. And then November arrives with Thanksgiving break, December with winter break, January with the second semester ramp-up. A PM program that wasn't designed to account for these rhythms will encounter its first major scheduling collision by late October and its first real abandonment by December.
The four failure modes
In talking to facilities directors and operations leads at schools, the same failure patterns show up over and over. They're worth naming clearly.
1. PM work gets bumped for reactive work, permanently
The theory of preventative maintenance is sound: schedule proactive work before problems occur, which reduces the volume of reactive work over time. The practice fails because schools start with a backlog of deferred and reactive work that competes directly with PM tasks for the same technician time. In the early months of a PM program, the PM work will lose that competition almost every time. An emergency takes priority over a scheduled inspection. A broken heating unit in a classroom beats a filter change in a mechanical room. And once PM work starts getting pushed to "next week," next week never really comes.
The fix isn't discipline — it's separation. PM work needs to be scheduled in time windows where reactive work can't reach it. Summer break is the obvious window. But smart programs also carve out consistent weekly maintenance blocks during the school year that are protected from work order interruptions.
2. The program lives in one person's head
Most school PM programs get launched by one motivated person — usually the facilities director or a senior tech who believes in the work. That person knows the schedule, tracks the completion, manages the exceptions. When they take a week off, the program pauses. When they leave the district, the program ends.
This isn't a people problem — it's a structural one. The program needs to live in a system that any qualified person can pick up and execute. Documented schedules, completion records, escalation procedures, and institutional knowledge about each asset. The moment the program depends on tribal knowledge rather than structured documentation, it's one resignation away from collapse.
3. The intake problem
Reactive maintenance — the kind that comes in when something breaks — requires an intake mechanism. Someone needs to be able to report the problem. In most schools, that mechanism is informal: a teacher walks to the office, someone calls the facilities department, a text gets sent to whoever's number is in someone's phone. Problems fall through the cracks constantly. By the time a PM program is running, the team is already dealing with a backlog of problems that never got properly logged, routed, or addressed.
A PM program that doesn't also fix the work order intake system just adds scheduled work on top of chaotic reactive work. The result is more overload, more conflict, and faster abandonment.
4. No one can see what's happening
The fourth failure mode is visibility. PM programs require consistent execution across multiple people and multiple timelines. Without a clear view of what's been done, what's overdue, and what's coming up next, the program drifts. Individual tasks slip without anyone noticing until the slip has become a full backlog. There's no early warning system, no accountability mechanism, no dashboard that tells a director the program is falling behind before it falls apart entirely.
What changes things
The schools that maintain functioning PM programs — and they exist — share a few consistent characteristics. Their programs are built around the school calendar rather than a generic annual schedule. PM work is protected during high-demand periods rather than simply hoped to happen alongside reactive work. Their institutional knowledge is documented and accessible to the whole team, not held by the person who's been there the longest.
Schools with systematic preventative maintenance programs see 30–50% fewer unplanned equipment failures and reduce total maintenance costs by 25–40% over a three-year period. The payback period for a well-deployed maintenance system is typically 6–12 months. The barrier isn't cost — it's program design.
Most importantly, their programs run in systems — not in people's heads. Schedules are documented. Completions are logged. Exceptions are visible. Anyone on the team can pick up where someone else left off. The program is resilient to the normal disruptions of school life — staff turnover, unexpected repairs, weeks that don't go according to plan — because it was designed to handle those disruptions rather than assume they won't happen.
The rhythm question
The deeper issue with most school PM programs is that they treat maintenance as a list of tasks rather than as a rhythm. A list of tasks can be interrupted, deprioritized, and deferred indefinitely. A rhythm — a regular, structured cycle of preventative work that's tied to the actual operating cadence of the school — is much harder to break once established.
Building that rhythm requires designing a program around the school's actual operating reality: the academic calendar, the seasonal demands on building systems, the staffing patterns, the windows when disruptive work can actually happen. It requires treating the summer shutdown not as a vacation from maintenance but as the most valuable maintenance window of the year. It requires making the intake of reactive requests consistent and structured so they don't overwhelm the proactive schedule.
None of this is complicated. But it does require a system that was designed for schools specifically — not adapted from a commercial facilities management tool with a different set of assumptions built in.
Signs your PM program is at risk
- PM tasks are regularly pushed to accommodate reactive work orders
- The schedule lives in one person's calendar or spreadsheet
- You can't quickly answer: what PM work was completed last month?
- Staff turnover has caused program knowledge to reset
- The program doesn't account for summer vs. school-year staffing differences
- Work order intake relies on phone calls, texts, or hallway conversations
The $270 billion in deferred maintenance sitting in U.S. school facilities isn't the result of facilities teams not caring. It's the result of programs that weren't designed to survive the reality of a school year. The teams doing the work are capable. The tools need to catch up.