Scoping a Section 166 Review: How to Limit Remit Without Looking Obstructive

The scoping phase of a Section 166 review is the single most consequential moment in the entire exercise. Once the Requirement Notice is finalised, the reviewer's methodology, sample sizes, lookback period and reporting lines are effectively locked in, and every ambiguity will be resolved against the firm. Yet firms routinely treat scoping as an administrative step rather than a negotiation. Done well, scoping produces a review that is rigorous, targeted and finite. Done badly, it produces a rolling investigation that expands with every interim finding.

Key Executive Takeaways

• The scoping response is where remit is won or lost; challenge the draft Requirement Notice line by line before it is issued, not after.
• Reframe scope around specific risks, populations and time periods rather than open concepts, and offer the FCA precision as a substitute for breadth.
• Position every limitation as a proportionality argument grounded in the FCA's own supervisory principles, never as a defensive refusal.

Understand what the FCA is actually trying to test

Before drafting a single word, work out what supervisory hypothesis sits behind the s166. Read the supervisory correspondence, the most recent portfolio letter, any recent Dear CEO themes and the case team's questions over the preceding six months. The Requirement Notice will almost always be an attempt to test a specific concern: governance failure in a product line, control weakness in a process, or credibility of management information. If you cannot articulate the hypothesis in one sentence, you are not ready to negotiate scope. Firms that push back on remit without understanding the underlying concern read as evasive.

Engage before the Notice is finalised

The FCA's practice is to share a draft Requirement Notice and invite comment. This window, usually short, is where the real work happens. Treat the draft as a legal instrument. Every noun matters. "Governance arrangements relating to product X" is different from "governance, oversight and culture across the retail division." Push for defined populations, defined time periods, defined processes and defined comparators. If the draft uses phrases like "including but not limited to," ask for the list to be closed. If it references "any related matters the Skilled Person considers relevant," ask for that discretion to be tied back to the specified concerns.

Offer precision as the trade

The FCA will not accept a narrower scope simply because it is more convenient for the firm. It will accept a narrower scope if you offer something better in return: greater depth, faster reporting, cleaner sampling, or direct access to specific data sets and personnel. Frame your response as, "We propose focusing on A, B and C, because this will produce more probative evidence of the underlying concern than a broader review of D, E and F." This shifts the conversation from remit reduction to methodological improvement.

Control the lookback and the sample

Two areas that consistently spiral are lookback period and sample size. On lookback, anchor to a specific regulatory or operational event: a policy change, a system migration, a rule implementation date. On sampling, propose a stratified approach with clear stopping rules, rather than accepting open-ended sample expansion driven by interim findings. Build in a formal checkpoint where any proposed sample increase must be justified against the original hypothesis.

Handle the Skilled Person selection carefully

The lot process gives you influence but not control. Meet each shortlisted firm before selection and probe how they interpret the draft scope. A reviewer who reads remit expansively will cost more, take longer and produce a harder report. Feed your observations back to the FCA through the selection process. Do not appear to be shopping for a soft reviewer; appear to be shopping for a reviewer who understands proportionality.

What good looks like

A strong scoping response runs to a few pages, not tens. It accepts the FCA's core concern explicitly, restates it in precise terms, proposes a defined workstream structure with populations, periods and outputs, and identifies what is expressly out of scope with brief reasoning. It never uses the word "disproportionate" without evidence. It offers the case team a document they can defend internally.

What most firms get wrong

The common failure is silence. Firms receive the draft, raise minor drafting points, and hope the reviewer will interpret scope sensibly. They do not. Reviewers price and plan against the widest plausible reading of the Notice. The second failure is tone: legalistic pushback that reads as obstruction and hardens the supervisor's stance. The third is internal: scoping handled by compliance without SMF and legal sign-off, producing commitments the firm later regrets.

Your next decision

If a draft Requirement Notice is on your desk, convene the SMF16, SMF17, General Counsel and the accountable business SMF within 48 hours. Map the hypothesis, agree the three or four scope points worth fighting, and prepare a written response that trades precision for breadth. After the Notice is issued, this leverage is gone.

Frequently Asked Questions

Can we refuse to accept the FCA's proposed Skilled Person?

Not outright, but you can raise conflicts, capability concerns or capacity issues during the lot process. Raise them in writing, with evidence, and early. Refusing without substance damages the relationship and rarely changes the outcome.

Should we ask for a Section 166(3)(a) firm-commissioned review rather than 166(3)(b)?

Where available, a firm-commissioned review gives you more control over engagement terms and reviewer management, though the FCA still approves scope and reviewer. It is usually preferable unless the supervisory concern is severe enough that FCA direct commissioning is inevitable.

How do we handle interim findings that expand beyond the original scope?

Insist at the outset that any proposed scope extension is routed through a formal change control process involving the firm and the FCA case team. Reviewers who expand scope unilaterally should be challenged in writing, promptly and without hostility.

Is legal privilege available over scoping communications?

Communications with external counsel about the scoping strategy attract legal advice privilege. The scoping response itself, once submitted, is not privileged. Structure internal analysis accordingly, particularly the assessment of what the FCA is really concerned about.

How long should the scoping phase take?

Two to four weeks is typical. Rushing produces bad Notices; delaying signals disorganisation. Ask for a realistic timetable at first contact and hold to it.