How to Sequence Stakeholder Engagement When Withdrawing a Regulated Product Line

Withdrawing a regulated product line is rarely a commercial decision alone. The order in which you tell people determines whether the exit is treated as a well-run strategic choice or a conduct event. Get the sequence wrong and you create foreseeable harm, regulatory censure, distributor disputes, and a workforce that finds out from LinkedIn. Get it right and the withdrawal becomes a demonstration of governance maturity.

Key Executive Takeaways

• The regulator should almost always be told before the market, but only after your internal decision is firm, your customer treatment plan is drafted, and your operational wind-down is credible.
• Sequencing failures usually come from treating engagement as a communications exercise rather than a set of interlocking legal, contractual and conduct obligations with different lead times.
• The hardest judgement is the gap between board decision and public announcement: too short and you look unprepared, too long and you risk leaks, insider trading exposure, and staff finding out second-hand.

Start with the decision, not the announcement

Before any external engagement, the board or delegated committee needs a documented decision that names the closure population, the rationale, the customer outcomes framework, the financial provisioning, and the accountable SMF. Regulators and skilled persons will later ask to see this. If the paper is thin, every downstream conversation is compromised.

What good looks like: a decision pack that already anticipates the customer harm analysis, the vulnerable customer overlay, the distributor contractual position, and the run-off obligations for in-force business.

Map the stakeholders before you sequence them

Build a single matrix covering: the regulator (usually FCA and PRA, sometimes FOS and FSCS by implication), existing customers segmented by product state and vulnerability, distributors and introducers, reinsurers or funding counterparties, staff (particularly those in scope roles), auditors, investors, and media. Against each, record the legal trigger, the notice period, the confidentiality constraint, and the person accountable.

Most people get this wrong by starting with a communications grid rather than an obligations grid. Communications flow from obligations, not the other way round.

The order that usually works

1. Regulator pre-notification, informal and confidential, once the board direction is clear but before final sign-off. This is where supervisors expect to be brought in, not surprised. Use it to test the customer treatment plan.
2. Board final approval, with the regulator's initial reaction reflected in the paper.
3. Formal regulator notification, including Principle 11 considerations, and any Part 4A permission implications.
4. Critical internal population: SMFs, legal, risk, operations, complaints, and the wind-down team. Cascade under confidentiality.
5. Distributors and material third parties with contractual notice rights. Miss this and you inherit disputes that outlast the product.
6. Staff more broadly, timed to precede external announcement by hours, not days, if the population is large.
7. Customers, sequenced by vulnerability and product state. Vulnerable and mid-claim customers first, with named contacts, not call centre queues.
8. Market announcement if listed, investors, and media.

The common failure is collapsing steps 5 to 8 into a single day because legal wants to control leak risk. That protects the share price and damages the customer outcome.

The judgement calls that actually matter

How long between board decision and customer notification? Long enough to stand up operational capacity for questions, complaints and alternative provision. Too many firms announce before the phone lines and web journeys are ready.

How much to tell distributors? Enough that they can meet their own conduct obligations to end customers. Withholding detail to manage commercial negotiations creates a conduct problem you will own.

When to involve FOS and FSCS thinking? Before customer communications go out, not after the first complaint. Your wording will be read against future redress standards.

What about in-flight applications? Decide the cut-off before the regulator asks. A clean, dated pipeline position is a marker of a controlled exit.

What good looks like at the end

A closure file that a skilled person could pick up cold and follow: board minutes, regulator correspondence, customer treatment rationale, distributor notices, staff communications, and a live tracker of run-off obligations. Withdrawals are judged years later, when a complaint or review reopens the decision. The sequencing you choose now is the audit trail then.

Your next decision

Before the next executive meeting, ask one question: if the regulator called tomorrow, could we show them a sequencing plan grounded in obligations, or only a communications timeline? If it is the latter, that is the work to do this week.

Frequently Asked Questions

When exactly should we tell the regulator?

As soon as the strategic direction is firm enough that not telling them would breach Principle 11, and before any external party outside the firm is informed. In practice this means an informal supervisory conversation ahead of final board approval.

Should distributors be told before customers?

Yes, but only by a short window, and only under confidentiality with clear onward communication obligations. They need time to prepare their own customer conversations and meet their conduct duties.

How do we handle staff in the affected line?

Tell SMFs and critical operational staff early under confidentiality. Broader staff communication should precede external announcement, but by hours, not days. Consultation obligations run in parallel and have their own statutory clocks.

What if news leaks mid-sequence?

Have a pre-agreed acceleration plan. The regulator should be told immediately that the sequence is compressing, customer communications should move forward, and the market announcement, if required, should be brought forward rather than delayed.

How long should the customer wind-down actually take?

Longer than the commercial team wants. Vulnerable customers, mid-claim cases, and products with switching complexity often need six to twelve months of active support beyond the withdrawal date. Provision accordingly.