How to Build a Regulator-Ready Wind-Down Plan That Demonstrates Operational Credibility

A wind-down plan is not a document exercise. It is a test of whether your firm actually knows how it would stop trading in an orderly way, without customer harm or market disruption, using resources it genuinely has. The FCA and PRA read plans looking for evidence of operational reality, not polished narrative. If your plan cannot survive a challenge session with your own executive committee, it will not survive a supervisor.

Key Executive Takeaways

• A credible wind-down plan is built from operational reality, not financial modelling: it must show you can actually execute the steps you describe, with the people, systems, and cash you have.
• The most common failure is understating wind-down costs and time, particularly people retention, technology contract exits, and client migration, which collapses the credibility of the whole plan.
• Regulator readiness comes from live testing, board challenge, and clear triggers, not from the length or polish of the written document.

Start with the operational spine, not the financials

Most weak plans begin with a solvent wind-down cost estimate and reverse-engineer the operational story. Good plans do the opposite. Map the actual sequence of events: what stops first, what continues, for how long, who does the work, and what infrastructure they need. Only then price it.

The operational spine should answer, concretely: which client segments get migrated or returned first, in what order, and why. Which regulated activities need permissions retained during wind-down. Which third-party contracts are critical, which have exit clauses, and which will demand renegotiation under duress. Which staff must be retained, at what cost, and how you would keep them once bonuses and career prospects have evaporated.

If you cannot name the individuals, contracts, and systems, you do not have a plan. You have an aspiration.

Cost the plan honestly, then add a buffer for reality

Supervisors have seen enough plans to know what is missing. The usual understatements: retention payments for critical staff, professional fees during a stressed exit, technology exit costs and data migration, run-off insurance, regulatory reporting continuation, and property or lease exit penalties.

Good practice is to build costs bottom-up from the operational spine, benchmark against known market examples, and then apply a stress overlay for the fact that wind-downs typically happen when things are already going badly. A plan that shows wind-down completing in three months on a lean cost base will not be believed. A plan that shows nine to eighteen months, with front-loaded costs and a realistic tail, will.

Triggers must be specific and pre-agreed

Vague triggers such as "significant deterioration in capital position" tell a regulator you have not decided when you would act. Triggers should be quantitative, tiered, and mapped to specific board and executive actions. Early warning indicators lead to enhanced monitoring. Amber triggers lead to pre-wind-down preparation. Red triggers lead to board decision on execution.

Crucially, the board must have discussed and endorsed these triggers before they are needed. A trigger that has never been debated will not be pulled in a crisis.

Test the plan against your own worst day

Run a live simulation. Take a plausible failure scenario, ideally one that combines a capital shock with an operational event, and walk through the first seventy-two hours. Who makes what decision. Who tells the regulator. Who tells clients. Who authorises the retention pool. Where does the cash come from on day one before assets are realised.

The gaps that surface here, unclear decision rights, missing delegated authorities, uncosted dependencies, are the ones a supervisor will find later if you do not find them first.

What good looks like

A credible plan is short on prose and long on specifics: named roles, dated contracts, quantified costs, tested triggers, and evidence of board challenge in the minutes. It acknowledges what is uncertain rather than glossing over it. It has been rehearsed, not just written.

Next step

Before your next board review, ask one question of the current plan: if we had to execute this on Monday, what would fail first? The honest answer tells you where to focus.

Frequently Asked Questions

How often should a wind-down plan be refreshed?

At minimum annually, and immediately after any material change in business model, group structure, key third-party arrangements, or capital position. A plan more than twelve months old with no evidence of review will be treated as stale.

Who should own the plan internally?

Accountability sits with the CFO or CRO under SM&CR, but the plan must be built with active input from COO, technology, HR, legal, and client-facing leadership. Ownership by finance alone is a common weakness.

How detailed should the trigger framework be?

Detailed enough that a non-executive director could read it and know exactly what action follows each threshold. If it requires interpretation in the moment, it is not a framework.

What is the single most common regulator challenge?

Understated cost and time to wind down, particularly around people retention and technology exit. Firms that address this proactively, with evidence, remove the largest source of supervisory doubt.