Asset Management Plan
An asset management plan template for a whole asset base over its life, rather than a maintenance program for next year. It states the service the assets have to deliver, what sustaining that costs annually, what is actually funded, and then shows the difference between those two numbers twice: once in money, and once in what it does to the condition of the buildings over the plan period.
- The funding gap shown in money and in condition index
- Levels of service, so the plan is about value not cost
- A deferral column against every renewal in the forecast
- What would be formally stopped at current funding
Asset Management Plan
Whole life, not next year
| # | LEVELS OF SERVICE | NOW | TARGET | AGREED |
|---|---|---|---|---|
| 1 | Buildings available when needed | |||
| 2 | Safe and compliant premises | |||
| 3 | Reliable critical systems |
The document you will get. Download for the full, editable file.
Who this asset management plan is for
One asset base, four readers, and only one of them starts at the gap.
The asset custodian
Named in section one, because a plan without somebody accountable for keeping it current is a document rather than a plan.
The finance director
Annual need as a share of replacement value, and the funding gap. Both are comparable against other organizations in a way an absolute budget never is.
The executive who endorses it
Section eight. What declines first, what becomes unreliable, and what the organization would formally stop doing at current funding.
Whoever maintains the assets
Lifecycle strategy per class, including which assets are deliberately run to failure so that it stops happening by accident everywhere else.
Where the asset base outlives the budget cycle
The structure suits any organization holding long-lived assets it has to fund across decades rather than years. What changes is the planning horizon and who endorses the gap. If you run one of these, the sector page goes further than the template does.
- Education
Campuses and school districts, where the estate is old, the horizon is long and the funding case is made annually to a board.
Campus maintenance software - Commercial real estate
Property portfolios, where renewal liability is a valuation question as much as a maintenance one.
Portfolio maintenance software - Healthcare
Healthcare estates, where deferred renewal becomes a clinical risk rather than only a cost.
Healthcare maintenance software - Corporate facilities
Corporate estates, where a consolidation decision changes which assets are worth renewing at all.
Corporate facilities software - FM service providers
Service providers advising an owner, where the plan is the deliverable and the gap is the client's decision.
FM service provider software - Data centers
Data centers, where the replacement cycle is short, the consequence of failure is immediate, and the plan is mostly about redundancy.
Data center maintenance software
What an asset management plan template should contain
An asset management plan sets out how an organization will sustain its assets over their whole life. It records what is owned and its replacement value, the levels of service those assets must deliver, the lifecycle strategy and renewal forecast per asset class, and the gap between what sustaining the portfolio costs annually and what is actually funded.
A. What we own, what it must deliver, what it costs
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Plan details | Portfolio, horizon, plan custodian, and the organizational objectives it supports | Ten years minimum, twenty where assets are long lived. The link to objectives is what makes this an asset management plan rather than a spending request. |
| Asset portfolio | Ten classes with quantity, replacement value, age, expected life, condition and share beyond life | Replacement value is the figure every other number is measured against. Estimate it rather than leaving it blank, and say that it is an estimate. |
| Levels of service | Eight, each with a performance measure, current, target and the cost to improve | Written in terms of what users experience rather than what maintenance does, which is what makes the plan decidable by somebody outside the function. |
| Demand and change | Headcount, usage, regulation, decarbonization commitments | Assets renewed to serve demand that will not exist in ten years is the commonest waste in a long-range plan. |
| Lifecycle strategy by class | Maintain and renew, Run to failure, Replace early, Refurbish or Dispose | Spelled exactly that way. Run to failure is a deliberate strategy for short-lived low-consequence assets, and naming it stops it happening by accident everywhere else. |
| Renewal forecast | Period, what is due, estimated cost, whether it can be deferred and for how long | The deferral column is the one that protects the plan. Without it the program gets cut from the bottom, and the bottom is where the cheap preventive items sit. |
| Annual need as a share of replacement value | Total annual need against portfolio replacement value | The one figure in this plan that can be compared with another organization, because it is independent of how large the estate happens to be. |
| The funding gap | Annual need, annual funding, the gap, and the cumulative gap over the period | Stated as a share of need as well as in money, because a gap of a given size means something different against a large portfolio than a small one. |
| Condition index, now and projected | Facility condition index today and at the end of the plan | The whole argument. The money figure asks for budget; the projected condition figure explains a consequence, and the two together are what change a decision. |
| What happens at current funding | Which classes decline first, and what would be formally stopped | The honest section. If the funding will not stretch, something has to be stopped deliberately rather than quietly under-delivered. |
| Asset risks and treatment | Impact and likelihood scored one to five, with a treatment and an accountable person | Includes funding and capability risks, not only asset failure risks, because a plan depending on people the organization does not employ is itself a risk. |
| Improvement actions by capability area | Where we are now, where we need to be, and the action | Register completeness, condition data, criticality, lifecycle costing, risk and data quality. Most organizations cannot answer the funding question accurately because the data will not support it. |
The reason most asset management plans fail to change anything is that they present the funding gap as a number, and a number is easy to decline. An annual need of two hundred and fifty four thousand against a hundred and ninety eight thousand of funding is a fifty six thousand gap, and everybody in the room already knows what happens to a request for fifty six thousand in a difficult year. It gets halved, or deferred, or absorbed, and none of those responses feel consequential at the time because nothing visible happens in the following twelve months. Assets are forgiving in the short run and unforgiving over a decade, which is exactly the mismatch that makes them hard to fund. What section seven does differently is express the same shortfall twice. The second expression, what the gap does to the facility condition index by the end of the plan period, converts an annual budget line into a trajectory, and a trajectory is much harder to wave through. It turns the question from whether to approve fifty six thousand into whether the organization is content for its buildings to be measurably worse in twenty years, which is a question an executive can only answer deliberately. The second structural decision worth protecting is levels of service. Without them a plan is a list of costs, and a list of costs invites line-by-line negotiation by people who cannot see what each line buys. With them, every cost is attached to something a user experiences: buildings available when needed, comfortable internal conditions, responsive repairs, reliable critical systems. Reducing the funding then has a stated consequence in the same terms, which is what moves the conversation from what maintenance costs to what the organization gets, and those are genuinely different meetings with different outcomes.
B. What it looks like filled in
One estate at annual review. Seventy eight percent of what the portfolio needs is funded.
| Line | Value |
|---|---|
| Portfolio replacement value | 6,800,000 |
| Total annual need | 254,000, which is 3.74 percent of replacement value |
| Annual funding available | 198,000, so 78 percent funded |
| Annual funding gap | 56,000, which is 22 percent of need |
| Renewal delivered, backlog carried | 162,000 delivered, 840,000 backlog |
| Condition index, unplanned failures, confidence | 6.8, four failures, Medium |
Seventy eight percent funded sounds survivable, and the eight hundred and forty thousand of backlog underneath it is what that figure has already cost. A twenty two percent annual shortfall does not present as a crisis in any single year; it presents as a slightly tighter program, a few renewals moved to next year, and a plan that still broadly happens. Accumulated across the years it has already been running, it is a backlog more than three times the size of the annual gap, which is the number that actually describes the position. Three lines here deserve to be read together rather than separately. Annual need at three point seven four percent of replacement value is the figure that can be compared with another organization, because it is independent of portfolio size, and it is within the range a well-run estate would expect rather than evidence of extravagance. The backlog says the funding has been short for some time. And the confidence rating of Medium is the one most plans omit: it says plainly that the underlying data supports this answer only approximately, which is more useful to an executive than a precise figure that quietly is not. Four unplanned failures in the year is the leading indicator to watch, because that is the number that rises first when renewal slips, long before the condition index moves visibly. What this example cannot show is the projected condition index at the end of the plan, which is the other half of section seven and the half that changes decisions. The register that supplies the asset data is the asset register, the survey that supplies the condition and the backlog figure is the facility condition assessment, and the routine work this plan assumes will happen is scheduled on the preventive maintenance plan.
An asset management template in three formats. Word for the version that goes to a board, Excel for the one that works out the gap, the share of replacement value and a Plan Review tab tracking condition against cumulative shortfall, and PDF for the endorsed copy. Free, and yours to rebrand.
How do you write an asset management plan?
Objectives first, then what the assets must deliver, then the gap. Six steps.
State the organizational objectives the plan supports
An asset management plan that does not connect assets to what the organization is trying to achieve is a spending request, and it will be read as one.
Record the portfolio and its replacement value
Ten classes with age, expected life, condition and the share already beyond life. Estimate the value rather than leaving it blank, and label it an estimate.
Define levels of service in terms of what users experience
Buildings available when needed, comfortable conditions, responsive repairs. Each with a current figure, a target and the cost to close the difference.
Set a lifecycle approach for every asset class
Including which classes are deliberately run to failure. Naming that strategy is what stops it happening by accident everywhere else.
Build the renewal forecast with a deferral column
Whether each item can be deferred and for how long. Without it the program gets cut from the bottom, where the cheap preventive items sit.
Show the gap twice, in money and in condition
Then say what would be formally stopped to live within current funding. That sentence is what forces the decision upward.
An asset management policy versus an asset management plan
Two documents ISO 55001 keeps separate, and most organizations merge. One says what we believe; the other says what we will do about it.
| Aspect | Asset management policy | Asset management plan |
|---|---|---|
| What it states | Principles and intent | Actions, costs and timing |
| Length | A page or two | A document with a forecast in it |
| Changes | Rarely | Reviewed annually |
| Endorsed by | The governing body | The executive, against a funding position |
| Contains money | No | The whole point of it |
| Answers | Why we manage assets this way | What it costs and what is funded |
Merging the policy into the plan is the commonest structural mistake here, and it weakens both. A policy is a short governance document stating the principles by which an organization manages its assets: the horizon it plans over, how it balances cost, risk and performance, who holds accountability, and what it will not do. It changes rarely, it is endorsed by the governing body, and its value lies in being stable enough to settle arguments. A plan is the opposite in every respect: specific, costed, time-bound and revised annually against a funding position that moves. Fold the policy into the plan and the principles get renegotiated every time the budget does, which is precisely when they are most needed and least likely to hold. Keep them apart and the annual plan review becomes a conversation about delivery against agreed principles rather than a rediscussion of first principles. The practical test is simple: anything in the document that would still be true if the funding doubled belongs in the policy, and anything that would change belongs in the plan. Two further boundaries are worth stating, because this document is frequently asked to be things it is not. The preventive maintenance program, what gets done to which asset at what frequency next year, is a different document and sits on the preventive maintenance plan. How facilities services are delivered, scoped and measured is the facility management plan. This plan is upstream of both: it decides what the asset base should be and what sustaining it costs, and the other two decide how the work is organized once that is settled. The metrics by which delivery is judged afterward are on the maintenance KPI template.
When the template starts to feel limiting
The file makes the case once a year, and the asset base changes continuously. Four things get difficult.
Condition data ages between surveys
The condition index is as old as the last assessment, and the plan is built on it as though it were current.
The trajectory needs several reviews
Condition against cumulative shortfall is the persuasive table, and it only exists once there are years of reviews to put in it.
The renewal forecast drifts from reality
What was actually delivered against what was forecast is the test of the plan, and on paper those two live in different documents.
Deferrals are not tracked after the decision
An item deferred two years has a date attached to it in the forecast, and nothing brings that date back round.
What running this in Facilio looks like
The plan does not change. What changes is that the data underneath it is current when the case is made.
Asset Intelligence
Condition stays current
Condition updated from work and inspections rather than from a survey two years ago, so the index behind the case is not quietly out of date.
Ops Performance Intelligence
The trajectory builds itself
Condition against cumulative funding gap accumulating year on year, which is the table that makes the case rather than the plan document itself.
Work Order Intelligence
Deferrals come back round
A renewal deferred two years carries a date, and the date arrives as a decision rather than as a surprise.
Audit Report Intelligence
Delivery is evidenced against forecast
Renewal delivered against renewal planned, which is the only honest test of whether last year's plan meant anything.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is an asset management plan?
It sets out how an organization will sustain its assets over their whole life: what is owned and its replacement value, the levels of service those assets must deliver, the lifecycle strategy and renewal forecast per class, and the funding gap.
It is a whole-life document with a ten or twenty year horizon, not a maintenance program for next year.
What is the difference between an asset management policy and a plan?
Under ISO 55001 they are separate documents. The policy states principles and intent, changes rarely, and is endorsed by the governing body. The plan is specific, costed, time-bound and reviewed annually.
The practical test: anything that would still be true if the funding doubled belongs in the policy, and anything that would change belongs in the plan.
Why show the funding gap in condition as well as money?
Because a gap expressed in money is a budget request, and a budget request can be declined without anything visible happening in the following year.
Expressed as what it does to the condition index over the plan period it becomes a trajectory, which an executive can only wave through deliberately.
What are levels of service and why do they matter?
They describe what users actually experience: buildings available when needed, comfortable internal conditions, responsive repairs, reliable critical systems, each with a measure and a target.
Without them the meeting is about what maintenance costs. With them it is about what the organization gets for the money, and those are different conversations.
How long should the planning horizon be?
Ten years minimum, and twenty where the assets are long lived, because building fabric and major plant operate on cycles that a five year view cannot see.
A horizon shorter than the renewal cycle of the main asset classes will always understate the liability.
What share of replacement value should a portfolio need annually?
Expressing annual need as a percentage of replacement value is the point, rather than any single benchmark, because it is the one figure comparable between organizations of different sizes.
The worked example runs at 3.74 percent of replacement value with 78 percent of that funded, which is a recognizable position rather than an alarming one.
What does run to failure mean here?
It is a deliberate lifecycle strategy for short-lived, low-consequence assets where planned renewal costs more than letting the item fail and replacing it.
Naming it explicitly for the classes where it applies is what stops it quietly becoming the strategy everywhere else by default.
Does this cover the preventive maintenance program?
No. This plan decides what the asset base should be and what sustaining it costs over its life. What gets done to which asset at what frequency is a separate document.
How facilities services are scoped and delivered is different again, and belongs on a facility management plan rather than here.
In one paragraph
An asset management plan works when the funding gap appears twice, in money and in what it does to building condition over the plan period, because the money figure asks for budget and only the condition figure explains a consequence. Define levels of service so every cost is attached to something a user experiences, set a lifecycle approach for every asset class including the ones deliberately run to failure, record whether each renewal can be deferred and for how long, and say plainly what would be formally stopped to live within current funding.
The gap, and what the gap does
State the objectives, price the portfolio, define the service levels and show the shortfall both ways. Once the condition data is older than the decision it supports, or the trajectory needs years of reviews assembled by hand, the document version has reached its limit.