Key takeaways
Lead with consequence, not just asset age.
Show the difference between planned spend and emergency spend.
Ask for one clear decision instead of a vague placeholder request.
Start with the decision, not the backlog
Leadership rarely approves a project because a facilities team says an asset is old. They approve when the request is framed as a decision with a clear tradeoff: replace now, defer one cycle, or keep absorbing a growing risk.
That means the first job of a capital request is not to list every system that feels urgent. It is to show which request deserves attention before the others on the table.
Translate technical urgency into consequence
Facilities teams usually understand which systems are aging into trouble. The missing piece is a narrative that finance and leadership can compare across multiple requests.
The request gets stronger when technical detail is translated into consequence that non-operators can weigh alongside cost.
What service or operation is exposed if the asset fails
How the consequence changes during weather, occupancy, or peak-use periods
What temporary workarounds become necessary if the team waits
Show the cost of waiting
A board-ready request does not stop at replacement cost. It explains what becomes more expensive when the team loses the ability to act on its own timeline.
That is where planned capital starts to look materially different from emergency spend. Rush labor, expedited procurement, downtime, and temporary systems often matter more than the replacement invoice itself.
Package the request so it can be compared quickly
Good capital requests are easier to approve because they are easier to compare. They make the timing question visible, the consequence legible, and the ask concrete.
One-page executive summary
Clear recommendation and alternate path
Modeled impact of delay
Short explanation of the drivers behind the request