Why Maintenance Budget Proposals Fail (And a Template That Fixes It)

Most maintenance improvement proposals get knocked back before they get a fair hearing.

Not because the work isn't needed. Not because the numbers don't stack up. Because the proposal lands on the wrong desk, framed the wrong way, asking for too much too early.

After working through maintenance assessments across mining, utilities, and heavy industry, the pattern is consistent. A maintenance manager builds a proposal. It's detailed. It's honest. It reflects months of frustration with equipment failures, reactive work, and a team running to stand still. Then it goes upstairs and the answer is no.

Here's why, and here's what to do about it.

The mistake most proposals make

The typical maintenance improvement proposal leads with what's wrong and follows with what it'll cost to fix it. New technology. New systems. More headcount. Better training.

The CFO reads it and sees a cost centre request.

The problem isn't the ask. It's the sequence. You've handed someone an unfamiliar problem and an expensive solution in the same breath. You haven't yet established credibility, demonstrated execution capability, or made the case that improvement is achievable before the spend.

There's a better structure. It involves two conversations, not one.

The two-conversation approach

The first conversation is internal. It starts with your own data, your own site, your own crews.

In almost every maintenance assessment we run, the performance gap between the best and worst crews on the same site is larger than anyone expects. Planning compliance ranges from 45% to 85% across two shifts. Repeat failure rates on the same equipment differ by a factor of three. PM task effectiveness varies not because the procedures are different, but because the disciplines around them are.

The internal case starts here. It says: we already have proof that better is possible. Our best crew is doing it right now, with the same budget and the same resources as everyone else. The improvement we're proposing isn't a theoretical outcome. It's a capability transfer.

This is a fundamentally different conversation. No new capital required. No external benchmarks to argue with. The objection "our site is different" doesn't apply when you're comparing your own crews to each other.

Get runs on the board here first.

The second conversation is external. Once you've demonstrated that internal improvement is achievable and you have early results to point to, you bring in the industry benchmark. You show that even your best crew has headroom against the GFMAM Maintenance Management Landscape or ISO 55001 maturity criteria. Now the case for broader investment has credibility behind it, because you've already shown you can execute.

Two conversations. The first gets the quick win approved. The second gets the strategic investment approved. In that order.

What the numbers actually need to show

The financial case for maintenance investment trips people up because they try to quantify everything precisely before they have the data to do it.

In practice, you don't need precision. You need a defensible range.

That's where PERT analysis is useful. Rather than committing to a single cost figure, you estimate the cost of reactive versus planned maintenance under three scenarios: optimistic, typical, and pessimistic. The calculation weights these scenarios and produces a probability distribution. You choose the confidence level that's appropriate for the conversation you're having.

A P50 estimate says: there's a 50% chance the actual cost is at or below this number. A P90 estimate says: there's a 90% chance. Conservative for a first proposal. Defensible under scrutiny.

The point isn't to produce a precise forecast. It's to show that you've thought about variability, you've accounted for uncertainty, and the case holds up even in the middle of the range.

That's what a finance team actually wants to see.

What happens if nothing changes

Every business case needs a cost of inaction. Not a vague statement about reliability risk. A specific, quantified estimate of what staying at current performance levels will cost over the next 12 months.

Unplanned downtime events per month, multiplied by average downtime cost. Reactive work as a percentage of total maintenance spend. Contractor premium costs. Deferred production or throughput impact. Asset life reduction from run-to-failure patterns.

These numbers are almost always available in the CMMS and maintenance cost reports. They're just not usually assembled in one place and presented to a decision-maker as a single figure.

The cost of doing nothing is the most persuasive line in any maintenance business case. It reframes the decision from "should we spend this?" to "can we afford not to?"

The ask

The ask should come in two stages.

Stage one is the internal capability transfer. No new capital. Defined scope. A specific budget and timeframe. Expected return based on the performance gap you've already documented. This is a low-risk, high-credibility request.

Stage two is the broader investment, contingent on Stage one results. This is where technology, systems, or an external maturity assessment enters the picture. You're asking for it from a position of credibility, with demonstrated execution, not as a leap of faith.

One proposal, two stages, one decision required.

Use the template

We've built an interactive Maintenance Business Case Template that structures this entire process. It walks you through the current state, internal case, PERT cost analysis, external maturity gap, risk of inaction, and the two-stage ask. Every section is editable directly in the browser. When you're done, you can export the completed case to PDF.

It's designed to be used with your own data in a working session, not as a document to fill in alone at your desk. Bring your maintenance planner, your CMMS reports, and an honest conversation about where your crews actually sit.

The template is free. You don't need a consultant to use it.