Scenario

The New CFO Reviews Every Committed Project

Six weeks into the role, the CFO re-baselines everything the organisation thought was decided. This scenario distinguishes a healthy reset from a political one, and shows sponsors how to come through either.

A new CFO reviewing inherited commitments is governance working as intended; most portfolios more than a year old contain cases that deserve reopening. The difficulty is that a reset and a purge look identical in week one, and behaviour during the review is shaped by which one people believe it is.

Last reviewed 3 July 2026 · Free and ungated

Pressure-test this decision

A reset and a purge look identical from the inside. Selected senior operators who have run these reviews as incoming CFOs, and taken projects through them as sponsors, will tell you in confidence which one you are facing, before the verdicts land.

Pressure-test this decision

How a client brief works · What you receive

Week six: the portfolio stops

The announcement follows a pattern: incoming CFO, first full look at the numbers, then a note to the executive team saying all projects above a threshold will re-present their business cases before further spend is released. Within days the organisation reorganises around the review. Sponsors dust off approval papers from two years ago and discover how much the assumptions have aged. Programme directors divert their best people from delivery to deck production. The PMO becomes a court of appeal. And in every corridor conversation, the same question: is this about the projects, or about the predecessor who approved them?

Why the CFO is doing this, and why sponsors hear something else

The incoming CFO has strong reasons that have nothing to do with politics. They own numbers they did not build, and re-baselining now draws a clean line between the predecessor's commitments and their own record. Early-tenure reviews also come cheap: a new CFO can stop a weak project without eating the blame for having approved it, a freedom that expires with every month in post. Sponsors, meanwhile, experience the same review as an accusation. Their projects were approved through a process they did not design, and re-presenting the case feels like relitigating a decision the organisation already made, in front of a judge with an incentive to find fault. Both readings are rational, which is what makes the review combustible.

A reset and a purge look alike at first

The distinction shows in the design of the review, not in its announcement.

  • A reset applies published criteria to every project; a purge applies scrutiny selectively, and the selection pattern maps to sponsors rather than to numbers.
  • A reset can conclude that a project deserves more funding; a review that only ever cuts was scoped to cut.
  • A reset prices the cost of stopping mid-delivery honestly; a purge counts the savings and ignores the demolition bill.
  • A reset puts the CFO's own early commitments under the same criteria; a purge exempts them.
  • A reset ends: it has a date, a decision list and a return to normal governance. A purge becomes a standing tribunal.

What the review gets wrong when fear runs it

  • Sunk cost confuses both sides: sponsors defend money already gone, while the review sometimes stops projects whose remaining cost-to-value is excellent because the historic overrun looks bad.
  • Presentation gets scored instead of substance, so the surviving projects are the ones with the best-connected sponsors and the most polished decks.
  • Delivery stalls during the freeze, so even projects that pass emerge weeks behind, with vendors and teams to remobilise at extra cost.
  • Candour is punished: a sponsor who honestly restates a worse position invites a stop, so cases arrive re-argued rather than re-baselined.
  • The projects nobody champions, often maintenance and risk work, die by silence rather than by analysis.

What each side should pressure-test

Sponsors should rebuild the case forward: remaining cost, remaining value, what has changed since approval, stated plainly and without defending the original decision, because the original decision is not the question. A sponsor who arrives with a today-forward case and a genuine stop option is usually treated as an ally of the review rather than a target of it. The CFO should pressure-test the review's design before its verdicts: whether the criteria would survive publication, whether the process can raise funding as well as cut it, and what the freeze itself costs per week across the portfolio, a number these reviews rarely put on their own slide.

Where outside judgement changes this

Inside the review, every participant is a party: sponsors are defending, finance is prosecuting, the PMO is keeping score, and the executive team is watching which way the new power flows. The input with no position is experience of the pattern itself. Executives who have run these re-baselines as incoming CFOs, and sponsors who have taken portfolios through them, know which review designs produced a stronger portfolio and which produced a weaker, more compliant one. Selected senior operators from the Global Board can advise either side in confidence: the CFO on running a reset that reads as a reset, or a sponsor on presenting a project the review should keep. Both conversations improve the same outcome.

Frequently asked questions

Is it legitimate to reopen projects the board already approved?

Yes, when material assumptions have aged, and most cases older than a year contain some that have. Approval was a decision on the information available then. What needs care is the framing: re-baselining against today's facts is governance, while re-trying the original decision is politics, and everyone in the room can tell which is happening.

How should a sponsor handle a project that genuinely looks worse than its approved case?

Say so first, with a today-forward recommendation attached, including the stop option if honest analysis supports it. In a well-run review, the sponsor who restates candidly earns credibility that outlasts the project. In a badly run one, being the review's example of candour is still safer than being its example of concealment.

How long should a portfolio review take?

Weeks, not quarters, for decisions above the line. The freeze is expensive in ways the review's own reporting seldom counts, from stalled delivery to vendor standby charges. A review that cannot conclude within a quarter has become a second approval process running permanently alongside the first.

Whether you run the review or face it, rehearse it first.

Pressure-test this decision