Why the VCP at close must be locked, not revised
The value-creation plan approved at close is a contract, not a living draft. It records what the investment committee underwrote: the levers, the baseline figures, the owners and the sources behind every number. The moment that document becomes editable, delivery stops being measurable, because the target moves with the result. A plan that quietly absorbs every miss is not a plan; it is a narrative that always looks on track. The version-lock principle is therefore simple: at sign-off, freeze the exact plan text, its baseline figures and its source set, and treat any later change as a separate, explicitly approved event rather than an edit. The same record-keeping discipline is what lets a team reproduce an AI strategy analysis months after sign-off, rather than reconstructing it from memory.
- The plan document as approved, with its initiative list and phasing intact
- The baseline figures for each lever, stated as they were underwritten
- The source set behind each figure, so every baseline number can be traced
- The sign-off record: who approved it, on what date, against which IC materials
The stakes for this discipline have risen sharply. Bain's 2026 Global Private Equity Report finds that a typical buyout now needs around 10% to 12% average annual EBITDA growth to deliver a benchmark return, where a typical deal in the 2010s needed only about 5%[1]. When returns depend almost entirely on operational delivery rather than multiple expansion, the gap between the plan you wrote and the results you show cannot be allowed to blur.
The window that baseline must govern is also getting longer. Bain notes the industry sits on a stock of 32,000 unsold companies worth $3.8 trillion, with buyout holding periods at exit now hovering around seven years, up from five to six between 2010 and 2021[1]. A reference document that drifts across a seven-year hold is worse than none. Building the frozen baseline into a structured value-creation plan at the outset is what makes every later quarter comparable to the first.
Evidence updates versus dashboard status reporting
Most portfolio reporting today is dashboard-shaped: a grid of levers, each carrying a red, amber or green dot. The problem is not the color; it is what the color stands for. A RAG status is an assertion with no traceable support, and it can be stale before anyone reads it: management accounts typically arrive with a two to six week lag after period close, so a status color can be months old by the time it reaches a board. An evidence update inverts that structure. For each lever it states the claim, then attaches a dated, located source: management accounts for a margin lever, a CRM extract for pipeline, a signed contract for a pricing lever. A reviewer can walk from the number back to its origin, which is exactly the traceability a frozen baseline is meant to enable.
The periodic evidence report: structure and source requirements
The evidence report is a recurring artifact, not a meeting deck. It reads the frozen plan lever by lever, and for each lever it carries five fields: the original baseline figure from the frozen VCP, the target, the named owner, the current status stated as evidence, and the cited source for every claim. It also records who verified each lever's evidence and who signed off the report, so accountability survives staff changes. The source requirement is the discipline: every number must point to a dated, located document, and any claim that cannot cite one is stated as an open question rather than a result. A common cadence is monthly updates for early-hold levers where momentum matters most, and quarterly for structural initiatives, with the full report reconciled against the underwriting case each quarter.
Documenting underdelivery without revising the baseline
When a lever misses, the temptation is to update the plan so the miss disappears. That is the failure mode the frozen baseline exists to prevent. Instead, document the gap explicitly against the untouched baseline: what landed, what slipped, what changed in the business, and what the exit model now says. Keep observation separate from decision. A re-underwrite, a scope change or a plan reset is a legitimate move, but it is a separate, board-approved decision recorded as a new event, never a quiet revision of the reference document. This keeps the baseline intact, makes the escalation conversation factual rather than political, and leaves a clean audit trail of what was promised, what was delivered, and what was consciously re-decided.
Related reading in this series: Documenting Deal Structure Decisions for Board or IC Review and The 12-Month Post-Deal Review: Did the Acquisition Thesis Hold?.
