Data & Insightsby Stratlens

Example solution · Budget & forecast control

Which costs need a closer look?

A forecast is more useful when leaders can see what changed, where the pressure sits and which decisions are still open. Bring those views together before approving more spend.

Illustrative example. All data is fictional. This demonstration shows a reporting approach, not a client engagement or an achieved result.

One total is not enough for an approval decision.

Imagine a digital-modernisation programme with six workstreams. At review cycle 04, the latest forecast is above the approved budget and another scope request is waiting for a decision. The programme sponsor needs to know which assumptions to challenge first.

This example separates the original budget, recorded spend and forecast cost at completion. It also keeps the unapproved scope request visible without adding it to the current forecast. That gives finance and delivery leads a consistent basis for their review.

Fictional report · Review cycle 04

Find the pressure before approving more.

Synthetic data
Forecast above budgetA$420k

5.25% above A$8.00m

Change since prior forecast+A$270k

A$8.15m → A$8.42m

Scope awaiting approvalA$360k

Excluded from current forecast

Cost at completion · A$ millions · all bars start at zero
Approved budgetA$8.00m
Current forecastA$8.42m
If pending scope is approvedA$8.78m

On smaller screens, scroll the table sideways to compare all measures. Amounts below are A$000. A positive budget gap means forecast cost exceeds budget.

Workstream review · recorded spend is included in forecast cost at completion
WorkstreamBudgetRecorded spendCurrent forecastBudget gapChange since prior forecast
Service portal1,8001,1502,040+240+120
Data migration1,4007601,660+260+180
System integration1,6009001,500−100−60
Identity and access900450860−40−20
Workflow automation1,3007201,270−30−40
Adoption and training1,0004101,090+90+90
Total8,0004,3908,420+420+270

Two workstreams account for A$500k of pressure.

Service portal and data migration are forecast above budget by a combined A$500k. The other workstreams provide a net A$80k offset, leaving an A$420k programme gap. Start the review with the assumptions behind those two highlighted workstreams.

Current forecast = A$4.39m recorded spend + A$4.03m remaining forecast. Recorded spend is not a measure of physical completion. The A$360k scope scenario assumes approval without other changes; it is not included in the A$8.42m current forecast.

Make the next review about decisions.

A single overall variance can hide where the forecast is moving. The workstream view gives the sponsor a smaller set of questions to resolve with accountable owners.

Challenge the remaining cost

Ask the service portal and data migration leads what changed in effort, rates, dependencies or scope. Check that the remaining forecast covers the agreed work and is supported by current assumptions.

Check the apparent offsets

Validate the lower forecasts elsewhere before relying on them. A delayed cost, missing commitment or incomplete estimate can look like a saving in a summary report.

Decide on the open scope

Assess the A$360k request separately, including its benefits, dependencies and funding. If approved, the illustrated forecast becomes A$8.78m: A$780k above the original budget.

The report supports these conversations. It does not validate the underlying estimates, approve expenditure or demonstrate that an overrun has been avoided.

A clearer view for finance and programme teams.

This approach may help when budgets, actual costs and forecasts sit in separate spreadsheets, or when a steering group can see the total but cannot trace the movement. The same reporting principles can apply to a portfolio of projects with agreed cost definitions and owners.

A scoped reporting project could include a consistent workstream structure, budget and forecast comparisons, a change log, and a documented update process. The first checks would cover reporting dates, cost categories, approved changes and reconciliation to the source totals.

Tell Sam how many projects you report on, who maintains the forecast and which decision is difficult today. A Power BI reporting project can be scoped around that need; the appropriate tool and level of detail depend on your sources and audience.

For a sales and margin question, explore the commercial performance example.

Sam Lim, founder of Stratlens

Your partner in the work

Work directly with Sam Lim.

Sam is the Founder & Principal Consultant of Stratlens. He combines strategy, analytics and consulting experience with hands-on Power BI, SQL and Excel work.

Start with the reporting question, then agree the sources, measures and checks the report needs. Consulting is available remotely worldwide.

Meet Sam and explore Data & Insights

Can you explain what changed in your forecast?

Tell Sam about your reporting process and the decision it needs to support. We can discuss a practical scope for a clearer view.

Discuss your reporting project