The Squeaky Wheel Isn’t a Roof Strategy

You’ve got 40 roofs. Maybe 100. One of them just dumped water into a gymnasium during a storm, so that’s the one getting replaced this year. Not necessarily because it was the worst roof in your portfolio, but because it was the one that got too problematic to ignore.

Sound familiar? If you’re managing a roof portfolio reactively, where whichever one rebels the most and leads to the loudest complaints gets fixed next, you don’t really have a roof program. Unfortunately for you, you’re really just the de facto facilitator of a very (very) expensive game of whack-a-mole.

Squeaky Wheel Isn’t a Prioritization Method (Sorry)

Occupant complaints just tell you a roof is currently annoying somebody. In reality, a leak doesn’t automatically mean that the offending roof is unfixable, nor does it mean it’s the most urgent need in your portfolio. Sometimes a leaking roof can be addressed with simple maintenance. Meanwhile, the roof two buildings over with no complaints yet might be a lot closer to actual failure and serious problems. It just hasn’t found its way into your inbox.

Think of it like an ER. A good doctor doesn’t treat patients in the order they showed up, nor by how loud they are yelling. They sort by who’s actually at risk. Roof portfolios need the same logic. Otherwise, you’re spending your capital budget on whichever patient gave the most ear-piercing squeal last winter, while a roof with genuinely higher risk sits quietly two buildings over, patiently racking up hidden damage and the bajillions of dollars in future repairs to go with it.

What “Which Roof First?” Actually Requires…

To prioritize strategically, you need to know some basic things about every roof in your portfolio:

• Age and remaining useful life. Not just install date, but actual conditions relative to expected service life for that system.
• Current conditions. Active leaks, deterioration, and membrane/sealant/flashing failures scored consistently.
• Consequence of failure. A leak over a server room, a clean room, or a lobby full of prospective tenants is not the same risk as a leak over a storage closet. Same roof condition, very different urgency.
• Warranty status. A roof still under warranty should be prioritized differently than one that’s been on borrowed time for a decade.
• Interdependencies with other capital work. If HVAC replacement, solar installation, or adjacent roof work is already on the books, sequencing matters. Replacing a roof and then cutting it open six months later for equipment is money burned twice.
• Funding pathway and lead time. A capital-reserve-funded replacement, a warranty-claim-driven replacement, and a lender-mandated replacement all move on different clocks. Know which clock each roof is on before you need the money.

Notice what’s missing from that list: “How many angry emails did facilities get?” Also missing: “How ugly does this roof look from the Dean’s corner office?” We’ve seen plenty of roofs jump the queue for that exact reason. Condition score be damned, nobody wants their boss’ boss staring at a sketchy-looking roof over their morning coffee. Funny? Sure. A defensible prioritization strategy? Not so much.

Turning a List Into a Program

Once you’ve got consistent data across your whole portfolio, prioritization stops being guesswork and starts being a plan. That’s the difference between a roof list and a roof program.

A real program does a few things a reactive approach never will:

• Smooths the budget. Instead of surprise emergency capital requests every time something fails, you’re forecasting a repair and replacement plan up to 20 years out and building it into your long-term capital plan.
• Bundles work for efficiency. Replacing three similar roofs in one bid cycle gets you better contractor pricing than three separate emergency scrambles, and for less work.
• Standardizes systems where it makes sense. Fewer roof types across the portfolio means simpler and better maintenance, and easier warranty tracking.
• Keeps the roofs not on this year’s list alive longer. A proper program should also include interim inspections and maintenance for everything still waiting its turn.

The Part Everyone Skips: Keeping the Data Alive

A condition assessment is a snapshot. A program is a living thing. The owners who get the most out of this approach treat the roof database the way they’d treat any other capital asset register, updated annually, not filed away and forgotten the week after the report gets delivered (or after the MVP facilities guy retires).

A living database is also what makes next year’s capital plan easier to build than this year’s. You’re not starting from zero each cycle. You’re improving on your asset knowledge and management year after year.

That’s the big difference between “we do the occasional roof looksies” and “we know exactly which roof needs attention next, and why.” The first approach may still yield solid information, but if every condition assessment is treated as a one-off by a different engineer or contractor each year, it’s difficult to get any real comparison of true relative needs across your portfolio. Sure, building X’s roof is looking gnarly based on engineer-of-the-month’s opinion, but that doesn’t necessarily mean that many others aren’t worse (or complete ticking time bombs).

Bottom line: Prioritizing roof replacements by who complains loudest isn’t a strategy and could be sucking the life out of your capital budget. A real program scores every roof the same way, plans years ahead, lines up with your capital cycles, and lets you say no to the squeaky wheels with data to back you up.

---