Start with decisions, not a spreadsheet
A five-year plan should help leadership decide what to fund, when to fund it, and what risk remains if the work moves. A list of assets, ages, and estimated costs is useful source data, but it is not yet a capital strategy.
The plan becomes useful when it explains why each project matters, what it depends on, how ready it is, and what operating consequence it addresses.
Build a complete project record
Each proposed project should have enough information to survive budget review and remain understandable when team members change. Keep the record concise, but make the assumptions visible.
- Asset, system, building, and operating context
- Observed condition and supporting evidence
- Risk or opportunity addressed
- Recommended scope and important exclusions
- Planning estimate, escalation basis, and confidence level
- Target year, dependencies, and project-readiness actions
Sequence projects realistically
Funding is only one constraint. Design lead time, permitting, shutdown windows, procurement, enabling work, occupant coordination, and internal capacity can all change the appropriate year for a project.
The strongest plans show those dependencies early, making the near-term budget more executable and reducing last-minute scope changes.
Show what is not being funded
A capital plan should make deferred risk visible. When a project moves, record the consequence, interim controls, and next review point. That creates a more transparent conversation than simply removing the item from the funded list.