Programme Budget and Financial Governance

Programme vs Project Financial Management

Programme financial management differs from project-level in several ways:

• Scale: Programme budgets are typically 5-50x larger than individual project budgets
• Complexity: Multiple cost centres, multiple vendors, multiple funding streams
• Flexibility: Need to reallocate between projects as priorities shift
• Governance: More stakeholders, more scrutiny, more formal reporting requirements
• Duration: Multi-year programmes require annual budget cycles and re-forecasting
• Benefits linkage: Budget must be justified against expected benefits (ROI)

Budget Structure

The Programme Budget Hierarchy

` Programme Budget (Total) ├── Project A Budget │ ├── Labour (internal) │ ├── Labour (external/vendor) │ ├── Infrastructure │ └── Other direct costs ├── Project B Budget │ └── [same structure] ├── Programme Management Costs │ ├── Programme team salaries │ ├── PMO costs │ └── Governance overhead ├── Contingency Reserve (10-20%) │ └── Tied to specific identified risks └── Management Reserve (5-10%) └── For unknown risks (sponsor-controlled) `

Funding Models

Annual allocation: Budget approved one year at a time. Programme must re-justify funding annually. Common in public sector and large enterprises.

Phase-gated funding: Budget released at phase gates (initiation, execution, deployment). Must demonstrate progress to unlock next tranche.

Full programme funding: Entire budget approved upfront. Most flexibility but highest risk for the organisation.

Outcome-based funding: Budget tied to benefit milestones. Funding continues as long as benefits are being realised.

Monthly Financial Cycle

Week 1: Actuals Collection

• Collect actual spend from all projects (labour, vendor, infrastructure)
• Reconcile with finance system (actuals must match the ledger)
• Identify any unplanned spend or coding errors

Week 2: Forecasting

• Each Project Manager provides their Estimate at Completion (EAC)
• Programme Manager aggregates and validates
• Identify variances >5% from budget and investigate root causes
• Update contingency utilisation and remaining balance

Week 3: Analysis and Recommendations

• Analyse programme-level financial health (aggregate CPI, burn rate, forecast)
• Identify reallocation opportunities (underspending projects → overspending projects)
• Prepare recommendations for steering (budget changes, contingency drawdowns, scope trade-offs)

Week 4: Reporting and Governance

• Present financial summary to steering committee
• Seek approval for any budget changes or reallocations
• Update the programme financial baseline if changes are approved
• Communicate financial decisions to project teams

Budget Reallocation

One of the Programme Manager's key authorities is reallocating budget between projects within the approved programme envelope:

When to reallocate:

• A project is underspending (scope reduced, efficiency gained, delayed start)
• Another project needs additional funding (scope increase, estimation error, risk materialised)
• Priorities have shifted (one project is more critical than another)

Governance for reallocation:

• Within delegated authority (e.g. <£50K): Programme Manager approves
• Above delegated authority: Steering committee approves
• Always documented with rationale and impact assessment
• Always communicated to affected Project Managers

The reallocation trap: Don't reallocate from a project that's underspending because it's behind schedule (they'll need the money later). Only reallocate genuine surplus — confirmed underspend that won't be needed.

Contingency Management

Contingency vs Management Reserve

Contingency (Programme Manager controls):

• Tied to specific identified risks
• Sized based on risk EMV (Expected Monetary Value)
• Drawn down when identified risks materialise
• Reported to steering with each drawdown

Management Reserve (Sponsor controls):

• For unknown risks (things we didn't anticipate)
• Typically 5-10% of total budget
• Only the sponsor can authorise drawdown
• Used when contingency is exhausted or for genuinely unforeseen events

Contingency Drawdown Process

1. Risk materialises (or is about to) 2. Programme Manager assesses the financial impact 3. Drawdown request submitted with: which risk, what impact, how much needed 4. If within authority: Programme Manager approves and reports to steering 5. If above authority: Steering committee approves 6. Remaining contingency balance updated and communicated

Contingency Adequacy Review

Monthly, assess whether remaining contingency is adequate:

• What risks remain open? What's their combined EMV?
• Is remaining contingency sufficient to cover them?
• If not: either close/mitigate risks to reduce EMV, or request additional contingency from management reserve

Financial Reporting for Steering

The one-page financial summary:

| Metric | Value | RAG | |---|---|---| | Approved Budget | £X.XM | — | | Actual to Date | £X.XM | — | | Forecast at Completion | £X.XM | 🟢/🟡/🔴 | | Variance | £XK (X%) | 🟢/🟡/🔴 | | Contingency Remaining | £XK (X%) | 🟢/🟡/🔴 | | CPI | X.XX | 🟢/🟡/🔴 |

RAG thresholds:

• Green: Forecast within 5% of budget
• Amber: Forecast 5-10% over budget
• Red: Forecast >10% over budget

Narrative: One paragraph explaining the variance and what's being done about it.

Financial Anti-Patterns

The optimistic forecast: Always forecasting "on budget" despite evidence of overspend. Fix: use EVM-based forecasting. CPI doesn't lie.

The hidden contingency: Padding every project estimate instead of maintaining visible contingency. Fix: estimate honestly, maintain explicit contingency with clear drawdown criteria.

The year-end rush: Spending remaining budget on unnecessary items to protect next year's allocation. Fix: return unused budget transparently. Build trust that honest forecasting won't be punished.

No reallocation authority: Every budget change requires steering approval, creating 2-week delays for routine adjustments. Fix: define clear delegated authority for the Programme Manager.

Benefits disconnection: Budget discussions never reference the benefits the investment is supposed to deliver. Fix: always frame financial decisions in terms of benefit impact.

---

Download the [Benefits Realisation Tracker template](/templates) to connect programme financial investment to business outcomes.