The roof section you flagged in 2023 finally leaks into the sanctuary. Somebody asks how this happened.

You know exactly how it happened. You raised it, it wasn’t funded, you patched it twice, and here we are. But the conversation in the room isn’t about a funding decision from three years ago. It’s about a leak, right now, and you’re the facilities person standing next to it.

The default owner of an invisible backlog

Deferred maintenance is a legitimate management tool. Organizations have finite money. Choosing to defer a roof in order to fund something else can be entirely rational.

It only becomes a problem when nobody is holding the decision. And when the backlog exists only in your head, in scattered emails, and in a budget request that got trimmed, there’s no record of a decision — there’s just a condition. Conditions belong to whoever maintains them.

That’s the trap. Not that the work didn’t get funded, but that the choice not to fund it left no trace.

Give the backlog a permanent address

The fix is unglamorous: a standing, written list of identified-but-unfunded work that never gets deleted and never lives in a single annual budget cycle.

Each item carries five things:

• What it is and where. Specific enough that a stranger could find it.
• When it was identified. The date matters more than anything else on the list. “Identified March 2023” is the whole argument in three words.
• Estimated cost. A real number, refreshed annually. Escalation is part of the story — the roof that was $60,000 in 2023 is $78,000 now.
• Consequence of continued deferral. Written plainly. Not “may cause damage” — what fails, what it takes out with it, what it costs then.
• Interim spend. Every patch, every temporary fix, every callback charged against that item. This is the number nobody expects and it’s the most persuasive one on the list.

The interim spend column wins arguments

Nobody tracks what deferral costs while you’re deferring. So the roof repair looks like $78,000 versus $0, and $0 always wins.

It’s never $0. It’s four patch calls at $1,200, two ceiling tile replacements, a ruined projector, and eleven hours of your technician’s time. When that’s written down beside the item, the comparison changes from “spend money or don’t” to “spend it once or keep spending it forever.”

That reframe requires the tracking to have already been happening. Which means every patch job needs to be tied back to the deferred item, not filed as another routine repair.

Present it as a decision, every year

Put the list in front of leadership on a set schedule — budget season is natural — and frame it correctly. You are not asking for all of it. You’re presenting a set of choices and asking which ones they’d like to make.

Rank the items yourself and say why. Something like:

Here are 14 identified items totaling $340,000. My recommendation is that items 1 through 4 be funded this year — those are the ones where deferral is actively costing us money or creating risk. The remaining ten I’m comfortable carrying another year, and I’ll bring them back with updated pricing.

Two things happen. You’re the person managing a portfolio rather than the person always asking for money. And the deferral becomes an explicit, recorded decision made by the people with the authority to make it.

This is not about covering yourself

It reads that way, and that’s the wrong read. A documented backlog isn’t a file you pull out after a failure to prove you warned them. If that’s what it’s for, you’ve already lost.

It’s for making better decisions before the failure. Leadership generally isn’t reckless about buildings — they’re working from incomplete information, and the person holding the complete information is you. A visible backlog is how it gets transferred.

Most of the time, when the real number and the real consequence are on the table, things get funded. The failures that come as a surprise are usually the ones that were never really presented.

Start it this week

Write down every item you’re currently carrying in your head. Just the list, rough costs, identified dates as best you remember. It’ll take an hour and it will probably be longer than you expect.

That hour moves the backlog out of your head, where it’s your burden, and onto paper, where it’s the organization’s decision.