PCPM All articles
Project Delivery

Inherited Mandate: Keeping Delivery Steady When the Executive Sponsor Changes

PCPM
Inherited Mandate: Keeping Delivery Steady When the Executive Sponsor Changes

Programmes in the UK seldom collapse because a technical problem proved insoluble. More often they lose their footing when the person who held the mandate walks out of the room, and nobody has written down what went with them.

Sponsor turnover is not an exception. It is a routine feature of organisational life: promotions, restructures, board rotations, ministerial reshuffles, elections that change the political leadership of a local authority. Each transition opens a gap between the authority a programme has been assuming and the authority its new sponsor believes they hold. Left unmanaged, that gap is filled by assumption.

The quiet shock of a departing sponsor

A programme that has run for eighteen months carries an invisible ledger of judgements: which supplier variation was tolerated, which scope was quietly deferred, which risk was accepted on the understanding that the finance director had been spoken to. None of that sits comfortably in a status pack. It sits in the head of the sponsor and in the relationships they have built.

When the sponsor leaves, three assets leave with them. Decision rights go first: who can approve spend above a threshold, who can accept a change to the benefits profile, who can speak for the programme at a board. Tacit context goes next: why option B was rejected in favour of option C, and what the regulator said off the record. Social capital goes last, and is often the most damaging loss — the informal access to finance, legal and supplier leadership that made escalation quick rather than painful.

Three artefacts to have ready before the announcement

Continuity is easier to design than to improvise. Three artefacts, maintained as living documents, do most of the work.

The decision log with standing status

Most programmes keep minutes. Far fewer keep a decision log that records, for each substantive decision, the date, the authority exercised, the rationale and — critically — a status of standing, superseded or requiring reaffirmation. The status field is what turns an archive into a control. When a sponsor departs, the programme director should be able to hand over a list of decisions that remain valid and a shorter list that a new sponsor must consciously own.

The delegated authority map

The map should be aligned with the organisation's scheme of delegation, not with the programme's convenience. In central government, the relationship between the Senior Responsible Owner and the Accounting Officer needs to be explicit; in a local authority, the respective positions of the cabinet portfolio holder, the section 151 officer and the monitoring officer will shape what a sponsor can and cannot agree. In a private company, the board's reserved matters and the finance director's approval thresholds are the relevant boundaries. A one-page diagram, reviewed at each governance meeting, prevents the drift that occurs when a new sponsor assumes a mandate broader than the one they have been given.

The commitment register

External promises are the hardest to reclaim. Contract variations, lease agreements, grant conditions, regulatory undertakings and public statements all constitute commitments that a new sponsor may not know they have inherited. Each should carry a note of who made it, on what authority, and whether it requires re-confirmation. Suppliers are rarely shy about reminding a programme of what was agreed. It is better for the programme to remind itself first.

The interim arrangement

Nature abhors a vacuum, and so does a programme board. An interim sponsor should be named within days, with a written and deliberately narrow scope: to keep the programme safe, to maintain the decision log and to convene the re-baseline. An interim sponsor with a full strategic remit invites a second transition when the permanent appointment is made. An interim sponsor with a caretaker remit preserves the option for the incoming executive to set direction without first unpicking decisions made in their name.

The 30-day re-baseline conversation

The re-baseline is not a restart. It is a structured reaffirmation, held within thirty days of the new sponsor taking up the role, and it should produce a one-page mandate statement signed by both the sponsor and the programme director. A workable agenda runs as follows:

The value of the exercise lies less in the document than in the conversation it forces. A sponsor who has publicly confirmed which commitments stand cannot later claim to have inherited a plan they never endorsed. A programme director who has heard the sponsor's priorities first-hand can stop guessing which of the old assumptions still apply.

Failure modes worth naming

The courteous pause is the most common. Everything waits for the new sponsor's review; weeks pass; supplier mobilisation costs accrue; the team loses rhythm. The silent rewrite is the most corrosive: priorities shift without a decision record, and the programme discovers the change when a budget line moves. The audit gap is the most expensive: a new sponsor inherits a programme they cannot defend to internal audit, to a funder or to a select committee, because the rationale for earlier judgements was never written down.

Making sponsor continuity a control

Continuity should be treated as a delivery control rather than a matter of courtesy. That means recording sponsor transition as a named risk on the register, identifying a deputy or successor at the point of appointment, and including transition readiness in periodic assurance reviews. The discipline is unglamorous, and it is precisely the kind of unglamorous discipline that keeps programmes moving when the carousel turns.

The mandate is not the sponsor's personal property. It belongs to the organisation, and it should survive the person who happens to be holding it this quarter.

All Articles

Related Articles

The Departure Window: Governing a Notice Period as a Delivery Workstream

The Departure Window: Governing a Notice Period as a Delivery Workstream

The Empty Chair in the Approval Chain: Making Leave a Delivery Control

The Empty Chair in the Approval Chain: Making Leave a Delivery Control

The Untested Hour: Giving Operational Rehearsal a Budget Line in UK Delivery