Skip to main content

How to Shape a Section 166 Scoping Response That Holds

A practical guide to responding to a draft Section 166 notice in a way that produces precise, workable terms of reference without inviting unnecessary scope creep. Readers will understand how to engage the supervisor credibly, where to push back on substance, and how to set the review up for a useful outcome.

A Section 166 notice rarely arrives as a surprise, but the scoping phase is almost always underestimated. The draft terms of reference will shape costs, management time, remediation obligations, and the supervisory narrative about your firm for the next eighteen months. Getting the scope right is not about shrinking it. It is about making it precise, evidenceable, and aligned to the actual concern the regulator is trying to resolve.

Start with the supervisor's actual concern, not the draft wording

The draft terms of reference are a proxy for a supervisory judgement. Before responding, work out what that judgement is. Read the Dear CEO letters, recent correspondence, thematic review outputs, and any supervisory meeting notes from the last twelve months. If the concern is about governance over a specific product line, the scope should reflect that, not a generic governance review. If the concern is a control failure identified in a past incident, the scope should test whether that failure is systemic, not reopen every adjacent control.

What good looks like: a scoping response that opens by restating the supervisory concern in your own words, confirms you take it seriously, and then proposes terms of reference that would actually answer it.

Engage with the Skilled Person candidate early

Once the firm is on notice, the regulator will usually consult on the Skilled Person. Use this properly. The right firm matters less than the right lead partner: someone with subject matter depth in the specific issue, not a generalist. A lead partner who understands the domain will write tighter terms of reference, ask better questions, and produce findings that are defensible. A generalist will expand scope to compensate for unfamiliarity.

Propose precise terms of reference, with testable questions

Where draft terms use open language ("assess the effectiveness of...", "review the adequacy of..."), propose testable reformulations. Good terms of reference specify:

  • The population and time period under review
  • The specific controls, processes, or decisions being tested
  • The standard against which they are being tested (handbook rule, internal policy, defined good practice)
  • The outputs expected (findings, root cause, recommendations)

Vague scope is the single biggest driver of mid-review expansion. A Skilled Person who cannot define "effectiveness" at the outset will define it through fieldwork, and the firm loses control of the frame.

Separate diagnostic from remediation

Skilled Person reviews that combine diagnosis and remediation design in a single Lot tend to produce broader remediation than necessary. Where the facts allow, propose a Lot structure that separates the diagnostic review from any follow-on remediation work. This preserves firm ownership of remediation design and avoids the Skilled Person becoming the author of changes they later validate.

Address what you already know

If the firm has already identified the issue, started remediation, or commissioned internal work, say so in the scoping response. Attach the work. This does two things: it demonstrates the firm is not waiting to be told what is wrong, and it allows the scope to focus on validation and gap analysis rather than discovery. Supervisors read a firm that already understands its own problem as materially different from one that does not.

What most firms get wrong

The common failure is treating the scoping response as a negotiation to shrink the review. Supervisors read this immediately, and it hardens the scope. The firms that come out of Section 166 reviews well are the ones that engaged with the concern honestly, proposed scope that would genuinely test it, and demonstrated in the response itself that they were capable of running the review as serious counterparties.

The decision point

Before submitting the scoping response, ask one question at board or ExCo level: if the review finds exactly what the supervisor suspects, are we ready to act on it? If the answer is no, the priority is not the scoping response. It is the remediation work that should already be underway.

Frequently Asked Questions

Should we use external counsel to draft the scoping response?

Yes, for anything material. Counsel will frame the response in a way that preserves privilege where appropriate and ensures the firm's position is coherent across correspondence. But counsel should draft with the business, not for it. A scoping response that reads as lawyered reads as defensive.

Can we object to the Skilled Person candidate?

You can raise concerns about independence, capacity, or expertise. You cannot realistically object on the basis that the candidate will be rigorous. Focus on substantive fit: sector expertise, prior conflicts, and lead partner quality.

How detailed should the scoping response be?

Detailed enough to show you understand the concern and have thought seriously about how it should be tested. Short responses signal disengagement. Over-long responses signal defensiveness. Ten to twenty pages is typical for a material review.

What if the regulator rejects our proposed scope?

That is their prerogative. The value of a well-constructed scoping response is not that it is accepted wholesale. It is that it shifts the conversation onto specific, testable terms and demonstrates the firm as a credible participant in the review.

When should the board see the scoping response?

Before it is sent. Section 166 reviews are a board-level matter. The accountable SMF should own the response, but the board should have seen the proposed terms of reference and understood the implications.

Frequently asked questions

Should we use external counsel to draft the scoping response?

Yes, for anything material. Counsel will frame the response in a way that preserves privilege where appropriate and ensures the firm's position is coherent across correspondence. But counsel should draft with the business, not for it. A scoping response that reads as lawyered reads as defensive.

Can we object to the Skilled Person candidate?

You can raise concerns about independence, capacity, or expertise. You cannot realistically object on the basis that the candidate will be rigorous. Focus on substantive fit: sector expertise, prior conflicts, and lead partner quality.

How detailed should the scoping response be?

Detailed enough to show you understand the concern and have thought seriously about how it should be tested. Short responses signal disengagement. Over-long responses signal defensiveness. Ten to twenty pages is typical for a material review.

What if the regulator rejects our proposed scope?

That is their prerogative. The value of a well-constructed scoping response is not that it is accepted wholesale. It is that it shifts the conversation onto specific, testable terms and demonstrates the firm as a credible participant in the review.

When should the board see the scoping response?

Before it is sent. Section 166 reviews are a board-level matter. The accountable SMF should own the response, but the board should have seen the proposed terms of reference and understood the implications.

Related guides

Regulation & Regulatory Change

Structuring a Dear CEO Letter Response That Lands Credibly

This guide sets out how to construct a Dear CEO letter response that answers the FCA's concerns with evidence, candour, and proportionate commitments. After reading it, you will know how to sequence the response, calibrate tone, and close the loop in a way that builds supervisory trust rather than prompting further questions.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Section 167/168 Investigation Response Strategy

A practical guide to building an investigation response that protects the firm's legal and commercial interests while demonstrating genuine cooperation with the FCA. Readers will finish with a clear framework for governance, document handling, witness preparation, and stakeholder sequencing in the first critical weeks of an investigation.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Pillar 3 Disclosure Under CRR for PRA-Regulated Firms

A practical guide to building a Pillar 3 disclosure that meets CRR and PRA expectations on transparency while handling commercially sensitive information responsibly. After reading, senior leaders will know how to sequence drafting, govern omissions properly, and brief the board on the trade-offs that matter.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

How to Structure a Recovery Plan Under PRA SS9/17 That Evidences Credible Options

A practical guide to building a Recovery Plan that satisfies SS9/17 by demonstrating genuinely executable options, calibrated indicators, and a governance spine that works under stress. Readers will finish with a clearer view of what the PRA is actually testing and how to evidence it.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Regulation & Regulatory Change

Structuring a Solvency II ORSA That Evidences Forward-Looking Risk Judgement

A practical guide to building an ORSA report that demonstrates genuine forward-looking risk assessment to the PRA. Readers will understand how to structure the document, where boards typically weaken their own case, and how to present a capital position that stands up to supervisory challenge on its merits.

Regulatory submissionRegulatorsBoards
4 min readRead guide →

Where a specific question needs an outside answer, quickly

Polar Insight's Expert Network connects leadership teams with practitioners who can speak to a precise regulatory, commercial, or stakeholder question before a decision is finalised.

Explore Expert Network