Value Creation Plan Governance Charter Template

Executive summary

Value creation plan governance is the written set of rules for who decides what, how an initiative earns the right to be counted, how often results are reviewed, and what happens when a number slips. A value creation plan (VCP) without it is a list of initiatives and a target. With it, the plan is a system in which every initiative has an owner, a stage, a benefit definition and a date.

Governance fails in four common ways: decision rights overlap, so two people approve or nobody does; initiatives are called "done" when the project ends rather than when the benefit reaches the P&L; reviews are held but lack a fixed agenda; and misses are explained at the board meeting instead of escalated when they happen.

The first move is a two-page charter agreed by the sponsor, the CEO and the CFO in week one. The template below covers decision rights, stage-gates, cadence, benefit tracking and escalation, and is meant to be copied and edited.

When to use this

Use this charter when:

• A sponsor, board or lender has approved a VCP and the operating rhythm for delivering it is not yet written down.
• The plan has more than about ten initiatives across several functions, so informal coordination no longer works.
• Initiatives are reported "green" for months and then show no EBITDA effect.
• A new CEO or CFO is joining, and the question of who can approve what is unclear.
• A sale or refinancing is on the horizon and a buyer will ask how results were tracked.

Do not use a heavy charter for a small plan; five initiatives and one accountable executive need only a one-page version. Size the initiatives first, using the margin expansion playbook, then govern.

Why governance decides whether the plan delivers

A VCP combines revenue, margin, working capital and structural initiatives owned by different executives and funded from one budget. Without rules, initiatives enter on enthusiasm and leave on silence, and cross-functional decisions wait for a meeting with no authority to decide.

Governance answers five questions in writing: who decides, what evidence an initiative needs at each stage, how often results are reviewed, what counts as done, and when problems move up. It does not guarantee the plan is right. It makes sure that when the plan is wrong, you learn quickly and a named person decides what to change.

The framework: five parts of the charter

Diagnostic questions

1. Is there a single list of every initiative in the VCP, with an owner, a stage and a benefit number?
2. Who can approve a new initiative, and who can approve a change in an existing initiative's target or date?
3. What definition of "done" does the team use today, and does it include the benefit reaching the P&L?
4. For initiatives closed in the last 12 months, can you trace each claimed benefit to a ledger line?
5. Does a miss reach the sponsor in days or at the next scheduled board meeting?
6. Is there a defined baseline for each benefit, agreed before the initiative started?

If the questions on done, ledger tracing or baselines are answered no, start with part 4 of the charter. A benefit with no agreed baseline cannot be realized, only claimed.

Part 1: Decision rights

Decision rights are the most often skipped part, and the cause of most delays. The goal is to make every recurring decision belong to one role, and to make the exceptions explicit.

A simple model uses four roles for each decision type:

• Decides (D): the one person who makes the call. Exactly one per decision.
• Recommends (R): prepares the proposal and evidence.
• Consulted (C): must be asked before the decision, but does not decide.
• Informed (I): told after the decision.

Set thresholds in dollars or percentages that fit your plan; the ones in the template are placeholders, not recommendations. Keep one decider per decision (co-decisions are escalations), scale authority with size (a small shift is for the owner, a change to the plan target is for the sponsor), and record each decision with its date, decider, evidence and effect.

For a plan with a management team that is new or changing, test whether the people named are right for the role before you lock the charter. The management team assessment for the first 90 days helps with that.

Part 2: Initiative stage-gates

A stage-gate defines the evidence needed before an initiative moves to the next stage and gets more resources. Stage-gates protect the plan from two failures: spending on ideas that were never sized, and counting benefit before it exists.

Use five stages. Fewer is fine for small plans; avoid more.

A few rules make the gates useful:

• Gates are about evidence, not meetings. A gate can be passed by email if the evidence is in the file.
• No benefit counts before stage 2 in the committed plan. Stage 0 and 1 benefit belongs in a pipeline view, shown separately from the committed plan.
• Stage 4 is not stage 5. Implementation is operational; realization is financial. Report them separately.
• Gates run backward as well. If evidence deteriorates, move the initiative back, pause or stop it, and record why.

Sizing in stage 1 should use a formula with an explicit haircut, not a target. The EBITDA bridge continuous tracking guide describes how to keep each initiative tied to the bridge as it moves through the stages.

Part 3: Cadence

Cadence is the calendar of reviews. The principle: each meeting has one purpose, a fixed agenda, a set of required inputs, and a decision it can make.

Monthly steering pack

Contents: a one-page summary of committed, realized and pipeline benefit; the bridge from baseline EBITDA to forecast by lever, with run-rate and in-year columns (see the margin expansion playbook); the initiative table with stage, owner, next gate and reason for any change; open risks and escalations; decisions required; and one-time cost versus budget.

Keep the agenda the same every time, require the tracker to be updated before the pre-read (an initiative with no update is reported as unknown, not green), reforecast with realized numbers as in rolling forecast versus annual budget, and record decisions, not discussion.

Part 4: Completion and benefit-realization tracking

A project can be finished and the benefit still be zero. The charter should define, for each initiative, two events: completion and realization.

Definitions

• Completion is a set of operational criteria agreed at stage 2: the system is live, the contract is signed, the process is running, the people are trained, the previous way of working is switched off.
• Realization is a financial test: the benefit has appeared in the ledger against a baseline agreed at stage 1, for a defined period.
• Baseline is the pre-initiative level of the measure (price realization, scrap rate, spend, cost center budget) frozen at stage 1.
• Benefit run-rate is the annualized effect when fully in place. In-year benefit is the portion that has occurred in the current fiscal year. These are not the same, and the tracker keeps both.
• Leakage is the difference between the benefit claimed at implementation and the benefit traced to the ledger.

The benefit funnel

Track each initiative through four values:

Identified run-rate  →  Approved run-rate  →  Implemented run-rate  →  Realized run-rate
Realization rate = Realized run-rate ÷ Identified run-rate

Worked example (illustrative)

The numbers below are made up to show the method. They are not benchmarks.

A supplier re-bid initiative, in $ thousands:

Implemented as a share of approved: 600 ÷ 720 = 83.3%. Realized as a share of identified: 450 ÷ 720 = 62.5%. In-year benefit as a share of run-rate identified: 180 ÷ 720 = 25.0%.

What this tells the sponsor:

• The gap from 720 to 600 is scope that was not contracted, and should have been raised at a review.
• The gap from 600 to 450 is leakage after signing, such as volume moving to non-contract suppliers. It needs a named cause.
• The in-year number is lower because contracts started part-way through the year.

Rules for tracking

1. Freeze the baseline at stage 1 and change it only by a recorded decision.
2. Finance validates realization. The owner reports implementation; finance traces the dollars.
3. Define the measurement window, for example three consecutive months at the new level.
4. Count each benefit once where initiatives overlap, and record the dependency.
5. Report leakage by cause, and track one-time cost to achieve with payback.

Completion checklist (copy per initiative)

Part 5: Escalation

Escalation defines when a problem leaves its owner, who receives it, and how fast they must respond.

Triggers

Set triggers on objective conditions. Examples of types, with placeholders for you to set:

Rules

Escalate on the trigger, not on the feeling: the owner does not have to be sure it is a problem. State the ask: problem, evidence, options with EBITDA and timing effect, a recommendation and a decision date. If the decider cannot decide within the response time, it moves up one level. Record the decision and check later whether it worked.

The copyable charter template

Copy the following into a document. Replace each bracket and delete rows that do not apply. The thresholds are placeholders: set them to your plan size and risk appetite.

1. Purpose and scope

2. Decision rights (D = decides, R = recommends, C = consulted, I = informed)

3. Stage-gates

4. Escalation

5. Records and change control

Keep one initiative register (owner, stage, lever, run-rate, in-year, one-time cost, baseline, next gate, date) and one decision log (date, decision, decider, evidence, effect). Changes to this charter are proposed by the CFO or CEO and approved by the sponsor, with version and date recorded.

6. Sign-off

Metrics and KPIs

Setting targets without invented benchmarks. Use your own history: the realization rate and milestone on-time rate of your last initiatives, then set first-year targets as improvements on those. Published averages rarely define "realized" the way you do.

Common mistakes

1. Counting benefit at implementation. The symptom: the plan shows 100% delivered and EBITDA has not moved. Add stage 5 and a finance sign-off.
2. Letting baselines move. The symptom: every initiative reports a saving against a new baseline. Freeze the baseline at stage 1.
3. Two deciders. The symptom: the same decision sits on two agendas. Name one decider per row.
4. Committing the pipeline. The symptom: stage 0 ideas in the headline target. Keep pipeline separate from committed.

AI prompt assistance

AI is useful for drafting and for checking consistency. Decisions and numbers stay with named people. Provide your own data and verify results against the register and the ledger.

1. Prepare the monthly steering pack.

Given this month's register and ledger actuals (pasted), write the one-page summary: committed, implemented and realized run-rate, movement since last month, the three largest variances with the stated cause, and decisions required. Do not add any number that is not in the data.

Check: reconcile every figure to the register and the bridge before it is circulated.

Implementation guide

The sponsor approves the charter, the CEO owns the rhythm, the CFO owns gate standards and benefit validation, and the transformation lead owns the register and the pack.

What to expect: the register and decision rights can be in place in a month; the first realized benefit validations take a full measurement window. For the first quarter, see the 100-day plan template for private equity; later, the register becomes the evidence base for the exit readiness 24-month plan.

Downloadable assets

The charter tables, completion checklist and register headings above are designed to be copied into a document or spreadsheet. To size the plan that this charter governs, use the value creation calculator and the EBITDA improvement calculator.

Related resources

• Margin expansion playbook: sizing the six sources of margin before you govern them.
• 100-day plan template for private equity: the first quarter of the plan.
• EBITDA bridge and continuous tracking: keeping initiatives tied to the bridge.
• Rolling forecast versus annual budget: reforecasting with realized results.
• Management team assessment: first 90 days: checking that owners fit their roles.
• Exit readiness: a 24-month plan: what a buyer will ask about plan delivery.

Frequently asked questions

What is a value creation plan governance charter?

A value creation plan governance charter is a short document that sets decision rights, initiative stage-gates, meeting cadence, completion and benefit-tracking rules, and escalation triggers for a value creation plan. It is agreed by the sponsor, CEO and CFO at the start so that every initiative has an owner, a stage and a defined result.

What should decision rights cover in a VCP?

Decision rights should name one decider for each recurring decision: adding or approving initiatives, changing dates and targets, moving budget, pausing or stopping work, validating benefit, and changing the plan target. Set dollar or percentage thresholds so authority scales with size, and record every decision with its date, evidence and effect.

How do you track benefit realization?

Freeze a baseline when the initiative is sized, define completion separately from realization, and have finance trace the benefit to ledger lines over an agreed measurement window. Track identified, approved, implemented and realized run-rate, plus in-year benefit and leakage by cause. The initiative owner reports implementation; finance validates realization.

How often should a VCP be reviewed?

Review initiatives weekly at owner level, lever results weekly or fortnightly, the whole plan monthly in a steering committee, and progress quarterly with the board or sponsor. Each meeting should have a fixed agenda, required inputs and a decision it can make. Gate reviews happen when evidence is ready, not on a calendar.

When should a problem be escalated?

Escalate when an objective trigger is crossed, such as a milestone slipping past a set number of weeks, realized benefit falling below a set share of plan, spend exceeding approval, or a covenant or sale milestone coming under risk. Each trigger names who receives it and how fast they must decide. The owner does not need to be certain it is a problem.

How this works in a System of Performance

A charter works only if the register, the decisions and the ledger results stay linked. In most companies the initiative tracker, the decision log and the finance data live in separate files, so realization is reconstructed before each steering meeting. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want a view of where your own plan stands, bring it to us as a launch partner.