Lead a Budget Overrun Review With Facts and Decisions

Budget pressure needs a review built from figures every participant recognizes. Bring approved budget, recorded spend, committed cost, remaining work forecast, and total forecast into one page. Put a reporting date and source beside each figure.

Define each number before discussing causes. Recorded spend covers costs entered through an agreed reporting date. Committed cost covers known obligations, such as approved specialist time or a requested purchase. Remaining work forecast covers expected cost for open activities. Total forecast adds recorded spend, commitments, and remaining work. A review loses value when those categories merge. The sponsor then sees one large figure without knowing how much already happened or how much depends on future work.

Pair money with delivery progress. Describe finished work in terms the sponsor recognizes. Discovery finished. One analysis package reached acceptance. A decision on final analysis still waits. A completion percentage needs a stated basis because one person might count a draft as finished while another expects approved material. A short record of finished and open activities exposes differing views of progress before a financial conversation becomes an argument.

Create a dated record for every forecast movement. Capture the affected activity, request or condition behind added work, cost recorded so far, expected effect, source, and person due to refresh the figure. The record exists to explain how delivery reached today’s position. Avoid turning a financial record into a case against an individual.

Consider timing. Suppose a new request arrived on Tuesday. Establish when related work started, when finance first recorded associated cost, and when the forecast changed. A revised estimate differs from spend entered before a decision point. Without dates, an overrun reads like a single failure rather than a sequence of events with different response options.

Separate confirmed drivers from assumptions. An approved scope request supported by meeting notes belongs in the confirmed group. Extra analysis requested during a workshop belongs there after recorded approval or direction. Delayed source data might affect remaining effort, though a workstream lead still needs to test the estimate. Label such an amount as an assumption. Place certainty only beside evidence already available.

Prepare the page with finance and the project manager. Ask finance which date recorded spend includes and whether entries are final for the reporting period. Ask the project manager about contractor commitments, travel, and scheduled support. Ask workstream leads which activities remain, which dependency affects each estimate, and when a refreshed view will arrive. Two figures sometimes differ for a sound reason. Show both figures, label each source, and explain the difference rather than selecting a convenient amount.

In a fictional steering meeting, sponsor Claire asks, “Why did delivery go over budget?” Delivery director Marcus replies, “Recorded spend equals 140 units from a 200 unit approval through last Friday. Commitments plus work left produce a total forecast of 230 units. Two approved analysis requests add 20 units. Delayed source data contributes a 10 unit assumption. I brought dates, evidence, and a choice for remaining work.”

Marcus shows a compact page rather than recounting every meeting. Approval equals 200 units. Recorded spend equals 140 units. Commitments equal 25 units. Remaining work forecast equals 65 units. Those figures total 230 units. A note beside the final two figures says source data validation finishes next week. Claire sees both arithmetic and the condition behind part of the estimate. Marcus does not ask her to accept an unexplained total.

Claire asks how 140 units relates to delivery. Marcus says, “The team finished discovery and one analysis package. Final analysis, sponsor decisions, and preparation for review remain open. We count a package as finished after your review gives approval. Our forecast assumes validation ends next Tuesday.” The answer supplies a usable progress measure. Marcus avoids a broad claim about effort.

Next, Marcus shows two confirmed drivers. The first approved request added customer segment analysis. The second added a comparison of two operating approaches. Each entry shows meeting date and estimate. Source data arrived three weeks after the planned date, leaving specialists without material for planned sessions. Marcus says, “I am not assigning every extra hour to delayed data. Ten units sit in forecast as an assumption. Priya will refresh this amount after validation.” Claire sees the difference between evidence and an estimate still under review.

Claire asks whether a smaller scope solves the position. Marcus answers, “Leaving the second comparison outside current work removes its remaining effort. Your planned review would proceed with one operating approach. Under this path, forecast returns within 200 units. You need to decide whether your review audience accepts a narrower question.” Reduced scope becomes a visible tradeoff, not a quiet default hidden inside an updated plan.

Marcus places a funding path beside reduced scope. “Keeping present scope leaves total forecast at 230 units. Finance confirmed 140 units already recorded. The 10 unit estimate for delayed data still needs validation. Additional funding follows your existing approval route. I will prepare figures, work effect, and assumptions for review.” Naming an amount does not create approval. Marcus gives Claire enough information to choose whether a funding request deserves consideration.

A timing path also belongs on the page. Moving the review date gives the team time to resolve the data dependency, yet a later review might affect participant availability and later decisions. Marcus describes each changed activity, the proposed date, and dependent work. Claire needs enough detail to compare a moved date against reduced scope or a funding review. “We will manage this” offers no basis for choice.

Test every number before the meeting. Add recorded spend, commitments, and remaining forecast. Confirm the sum matches the total forecast on the decision page. Check source dates against the reporting period. Read meeting notes beside each confirmed driver. Ask a colleague to act as sponsor and identify any unclear label. Fix uncertain wording before the live discussion, where a basic definition dispute consumes meeting time.

Use an order built for a decision. State the purpose: choose a path for remaining work. Show budget, spend, forecast, and progress. Explain drivers and assumptions. Place each option beside work effect, cost outlook, dependency, decision date, and approving owner. Pause for questions. If Claire asks for stronger evidence on delayed data, Marcus names Priya and next Tuesday for an update instead of filling a gap with confidence.

After Claire chooses, record details while everyone remembers them. Include selected path, owner, due date, affected work, forecast assumption, and next review point. A reduced scope decision needs a named activity leaving current work. A funding review needs figures intended for the existing route. A revised date needs an updated plan for participants affected by the change. Keep decision records close to the financial page so later readers see both choice and underlying figures.

For a fictional practice, set approval at 200 units and recorded spend at 140 units after discovery and one accepted analysis package. Set total forecast at 230 units, including 20 units from approved requests and a 10 unit delayed data assumption. Claire selects reduced scope. Marcus writes, “Second comparison leaves current work by Wednesday. Claire confirms the narrower review question by Friday.” He places the record beside the forecast and books a financial check for next Tuesday.