Tag: financial presentation

Tomás was ninety seconds into his project status update when the CFO held up one hand and said, “Skip to the number.”

The number was £1.4 million over the approved budget — a 22 per cent overrun on a digital transformation programme that had been running for nine months. Tomás had prepared twelve slides explaining the circumstances: regulatory changes, vendor delays, scope additions requested by the business. All of it true. All of it irrelevant to what happened next.

The CFO looked at the COO. The COO looked at the programme sponsor. Somebody asked whether the project should be paused. Tomás spent the next forty minutes defending a project he had originally been asked to update on. By the time the meeting ended, the overrun was no longer the problem. The problem was that nobody in the room trusted the forecast anymore.

That meeting could have gone differently. Not because the numbers were wrong, but because the presentation was built to explain the overrun rather than to manage it.

Why Budget Overruns Destroy Trust Faster Than Missed Deadlines

A missed deadline is a schedule problem. A budget overrun is a judgement problem. That distinction matters because it changes how executives interpret everything else you say.

When a project runs late, the typical assumption is that something took longer than expected — complexity, dependencies, resource availability. Most senior leaders have seen this before and can contextualise it. When a project runs over budget, the assumption is different: somebody either underestimated the costs, failed to control spending, or didn’t flag the issue early enough. All three are judgement failures, and judgement failures erode trust in the person presenting — not just the project.

This is why budget overrun presentations require a fundamentally different approach from standard project updates. A project update says “here is what’s happening.” A budget overrun briefing says “here is what went wrong, here is why I didn’t catch it sooner, and here is exactly what I’m going to do about it.” The order of those three elements matters more than most presenters realise.

The second complication is that budget overruns compound. An executive hearing about a £1.4 million overrun is not just thinking about £1.4 million. They are thinking: “Is this the final number, or is there more coming?” If your presentation doesn’t explicitly address forecast reliability — why they should believe the new number — you will face that question regardless. Better to answer it before it’s asked.

Understanding how to handle budget variance presentations is useful context here, but a variance and an overrun are not the same conversation. A variance is expected movement. An overrun is a breach of the approved envelope. The stakes are higher, and the presentation needs to reflect that.

The Three-Part Structure for Overrun Briefings

Every effective budget overrun presentation follows the same logic, regardless of the size of the overrun or the industry. It answers three questions in a specific order, and the order is non-negotiable.

Part 1: The current position — exactly how much and exactly why

Open with the number. Not the background, not the context, not the history of the project — the number. State the approved budget, the current forecast, and the variance in both absolute and percentage terms. Then explain the cause in no more than three clear categories. For example: “The overrun is driven by three factors. Regulatory requirements added to the scope accounted for £620,000. Vendor repricing after the contract mid-point accounted for £480,000. Internal resource reallocation from a parallel programme accounted for the remaining £300,000.”

Notice what this does not include: excuses, qualifications, or phrases like “due to unforeseen circumstances.” Every circumstance was unforeseen until it happened. What executives need is specificity, not apology.

Part 2: Forecast reliability — why they should believe this number

This is the part most presenters skip, and it is the part that determines whether the room trusts you or not. After presenting the current variance, explicitly address the question: “Is this the final number?” Explain the methodology behind your revised forecast. Show which cost categories are now fixed (contracted, committed, or delivered) and which still carry variance risk. If you are 85 per cent through the project with 90 per cent of costs committed, say so — that is a materially different risk profile from being 60 per cent through with significant uncommitted spend.

The best presenters I have worked with include a simple confidence indicator on their forecast slide: a three-tier assessment showing which cost lines are firm, which are estimated, and which carry identified risk. This gives the CFO what they actually want — not certainty, but a clear view of where uncertainty remains.

Part 3: The recovery plan — what you are going to do about it

End with a specific, time-bound recovery or completion plan. This is not a list of good intentions. It is a slide that shows: revised completion timeline, remaining cost envelope, specific cost controls you have already implemented, and the decision you need from the room (additional funding approval, scope reduction, or a hybrid approach). If the project can be de-scoped to bring costs back within the original budget, show what that looks like alongside the full-scope option. Let executives choose — do not choose for them.

The Recovery Slide That Restores Executive Confidence

If the overrun slide breaks trust, the recovery slide rebuilds it. And the difference between a weak recovery slide and a strong one is specificity.

A weak recovery slide says: “We will implement tighter cost controls and review the project plan to identify savings.” This tells executives nothing. It reads like a response drafted by someone who has not yet worked out what to do.

A strong recovery slide shows four things:

1. What has already changed

List the cost controls you have already implemented — not the ones you plan to implement. This signals competence and urgency. For example: “Weekly spend reviews introduced from 1 April. Vendor change request approval now requires programme director sign-off. Non-essential scope items paused pending revised business case.”

2. Revised cost forecast with committed versus estimated split

Show the remaining budget in two columns: committed costs (contracted, invoiced, or in progress) and estimated costs (subject to change). This gives the CFO the risk transparency they need without pretending you have perfect information.

3. Completion timeline — realistic, not optimistic

An overly optimistic revised timeline after a budget overrun is worse than an honest one. If the project will take three additional months, say so. Executives would rather hear a credible timeline once than an optimistic timeline twice.

4. The decision required

End the recovery slide with a clear ask. “We are requesting approval for an additional £1.4 million to complete the full scope, with revised completion in Q4. Alternative: reduce scope to phase one only, completing within the original budget by Q3.” Give the committee options and the information to choose between them. This is what presenting bad news to senior leadership actually looks like when done well — not minimising the problem, but framing the decision.

If you need templates for structuring these recovery conversations, the Executive Slide System includes frameworks for financial variance briefings and executive decision slides that separate the problem from the recommendation.

Language That Backfires When Presenting Bad Financial News

The words you use in a budget overrun presentation matter as much as the numbers. Certain phrases — often used with good intentions — consistently make the conversation harder, not easier.

“Due to unforeseen circumstances”

This phrase raises a question it was intended to answer: if the circumstances were foreseeable, why didn’t you foresee them? And if they genuinely weren’t foreseeable, then what does that say about the original budgeting process? Replace it with specificity. “Regulatory changes published in February added £620,000 to the compliance workstream” is a fact. “Due to unforeseen circumstances” is a defence.

“The project is slightly over budget”

Minimising language is the fastest way to lose credibility in these conversations. If the overrun is 22 per cent, it is not “slight.” Executives can read a spreadsheet. When the language doesn’t match the numbers, they stop trusting the language — and by extension, everything else in the presentation. State the variance clearly, without qualification. The CFO will form their own view on whether it’s significant.

“We’re confident the revised forecast will hold”

Confidence claims without evidence are meaningless after a budget overrun — because the original budget was presumably also presented with confidence. Replace the claim with the basis for it: “Ninety-one per cent of remaining costs are committed or contracted, leaving £180,000 of estimated spend still subject to variance.” That is a reason for confidence. The word “confident” on its own is not.

This kind of precise, honest communication is also central to effective cost reduction presentations — the same executives who need transparency about overruns also need it when you’re proposing cuts.

Handling the Hardest Questions in a Budget Overrun Q&A

The Q&A after a budget overrun presentation is where trust is either rebuilt or permanently damaged. Preparation is everything.

“Why didn’t we know about this sooner?”

This is the most common question, and the only honest answer addresses the reporting cycle directly. If the overrun materialised gradually and was identified at the most recent forecast review, say so. If the overrun was identifiable earlier but was not escalated, acknowledge that and explain what has changed in the reporting process. The worst response is to imply that the overrun only just happened when the data suggests otherwise. Executives who discover a delayed escalation after the fact will never trust the project team’s reporting again.

“What’s the worst case from here?”

Always have a worst-case number prepared. If the revised forecast is £1.4 million over, what is the maximum credible exposure? If the answer is £1.8 million under a specific set of adverse conditions, say so, and explain what those conditions would need to be. A presenter who can articulate the worst case calmly and specifically signals that they understand the risk landscape. A presenter who hesitates signals that they haven’t thought about it.

“Should we stop the project?”

This question often sounds more aggressive than it is. In most cases, the person asking wants to hear a clear case for continuation — they want to be persuaded. Respond with the sunk cost reality, the cost of stopping versus completing, and the business value that still justifies the investment. If the honest answer is that stopping should be considered, say that too. A recommendation to pause or descope is more credible than a recommendation to continue at all costs.

See also how today’s related articles tackle adjacent challenges: adapting executive presentations for cross-cultural audiences, the career cost of avoiding presentations at work, and building the structured system for boardroom credibility.

Frequently Asked Questions

How do you open a budget overrun presentation?

Open with the number. State the approved budget, the current forecast, and the variance in both absolute and percentage terms. Do not start with background, context, or a project timeline — these delay the conversation the room actually needs to have. Once the number is on the table, explain the cause in three clear categories and then move to the recovery plan. Executives facing a budget overrun want to understand the scale of the problem before anything else.

Should you present a budget overrun before the full picture is clear?

Yes, with appropriate caveats. A delayed escalation is always worse than an early one with acknowledged uncertainty. Present what you know, flag what you don’t, and commit to a specific date for the revised forecast. The phrase “the current estimated overrun is £X, with a further £Y still under review — we will have the full picture by [date]” is far more effective than waiting until you have perfect numbers. Executives consistently prefer incomplete but timely information over complete but late information.

What should the recovery plan slide include?

Four elements: actions already taken to control costs, the revised cost forecast split between committed and estimated spend, a realistic completion timeline, and the specific decision you need from the room. The recovery plan is not a list of intentions — it is a concrete proposal with options. Always present at least two options (full scope with additional funding, or reduced scope within the original budget) so executives can make a choice rather than simply react to a problem.

Not ready for the full system? Start here instead: download the free Executive Presentation Checklist — a one-page reference covering the structure, opening, and critical elements every executive financial briefing needs.