How to Structure a Section 166 Response That Preserves Board Credibility
A practical guide to responding to a Skilled Person review in a way that protects the board's standing with the regulator. Covers how to sequence the engagement, where boards typically damage their own credibility, and how to convert findings into a credible remediation posture.
Start from what the regulator is actually testing
A Section 166 is rarely just a diagnostic exercise. By the time the FCA or PRA has commissioned one, they have a working hypothesis about your firm and are testing whether the board sees what they see. Your response is not being marked on technical accuracy alone. It is being read for signals about self-awareness, grip, and whether the board can be trusted to fix things without further supervisory escalation.
This is the frame that should govern every drafting decision. Not: how do we defend our position. But: what would a credible, self-aware board sound like on this evidence.
Get the board posture right before you touch the drafting
The single biggest error is treating the s166 as a management exercise with board sign-off at the end. By then it is too late. The board needs to form its own view of the findings, in its own words, before the executive response calcifies.
Convene the board (or a designated committee) early, ideally as soon as the Skilled Person's provisional findings are shared. Two things need to happen in that room:
- The non-executives must be able to articulate, unprompted, what went wrong and why. If they cannot, the response will not survive contact with the supervisor.
- The board must decide where it agrees with the Skilled Person, where it disagrees, and where it accepts the finding but disputes the characterisation. These are three different postures and require different language.
Boards that skip this step end up owning an executive narrative they do not fully believe, which shows the moment a supervisor asks a probing question.
Structure the response in three layers
A credible response has three distinct layers, and they should be visible in the document:
Acknowledgement. What the board accepts, without qualification. Be specific. Vague acceptance reads as evasion. If the finding is that risk appetite was not embedded in first-line decisions, say that, and say when the board first should have seen it.
Context, not defence. Where context matters, provide it, but never as a substitute for acknowledgement. "We accept the finding. The board also notes the following factors, which inform the remediation approach rather than mitigate the failure." That phrasing matters. Regulators can tell the difference between context and excuse-making within two paragraphs.
Remediation with ownership. Every action needs a named owner (SMF where relevant), a date, and a board-level assurance mechanism. Generic "management will review" language is fatal. So is over-promising on timelines you cannot hit.
Handle disagreement carefully, but do handle it
Boards often assume that disagreeing with any part of the Skilled Person's findings is dangerous. The opposite is true. Blanket acceptance of every finding, including ones the board genuinely believes are wrong, damages credibility more than a well-argued disagreement.
If you disagree, do it once, clearly, with evidence, and move on. Do not litigate. State the disagreement, explain the basis, and confirm that the remediation approach still addresses the underlying supervisory concern even if the characterisation is disputed. This shows a board that thinks independently rather than one that will say whatever it takes to close the file.
What good looks like
A response that preserves credibility usually has these features:
- The board's voice is audible, distinct from management's.
- Acknowledgements are specific and time-bound.
- Remediation actions are owned by individuals, not functions.
- There is a clear line of sight from finding to root cause to action.
- Where the board disagrees, it does so precisely, once.
- There is an explicit statement of what the board will do differently in its own oversight, not just what management will change.
That last point is the one most firms miss. A s166 is almost always, at least in part, a finding about board effectiveness. If the response contains no changes to board or committee behaviour, the regulator will read that as the board failing to see itself in the findings.
The next decision
Before your next drafting session, ask one question: can each non-executive director, in their own words, explain what the Skilled Person found and why the board accepts it. If the answer is no, stop drafting and go back to the board. Everything else is downstream of that.
Related guides
Structuring an MLRO Annual Report That Satisfies SYSC 6 Without Triggering FCA Intervention
This guide sets out how to structure and write the MLRO annual report so it meets SYSC 6.3.9G expectations and gives the board a defensible record of financial crime oversight. After reading it, senior decision-makers will know what to include, what to leave out, and how to frame weaknesses without inviting supervisory follow-up.
What Makes a Decision Defensible to Regulators: A Practical Guide
This guide explains what regulators actually look for when they test a major decision after the fact, and how to build defensibility into the decision itself rather than reconstruct it later. You will finish with a clear view of what to document, who to involve, and where most firms leave themselves exposed.
How to Handle a Pre-Emptive Regulator Meeting After a Governance Failure
This guide covers how to prepare for and run a self-initiated regulator meeting when you have discovered a material governance failure inside your firm. After reading, you will know how to sequence the disclosure, frame the failure, and position remediation in a way that preserves credibility and controls the supervisory response.
How to Structure a Basel 3.1 Board Paper That Secures Approval
This guide sets out how to write a Basel 3.1 implementation board paper that wins approval without softening the capital impact numbers. Read it to sharpen your framing, sequencing, and stakeholder handling before the paper goes to committee.
Structuring an ORSA Board Narrative That Satisfies PRA Without Boxing In Strategy
This guide sets out how to write an ORSA board narrative that meets PRA forward-looking assessment expectations while preserving the board's room to change direction. It shows how to sequence risk, capital and strategy so the document is credible to supervisors without hardcoding decisions the board has not yet taken.
Polar Insight helps senior leaders in financial services understand what their key stakeholders actually think before significant decisions are made.