How to Prepare a Credible SM&CR Statement of Responsibilities
This guide sets out how senior managers and governance teams should draft, test and maintain a Statement of Responsibilities that stands up to regulatory challenge and successor review. After reading it, you will know what to include, what to cut, and how to evidence the judgements behind every line.
A Statement of Responsibilities (SoR) is read twice: once when it is filed, and again when something has gone wrong. The second reading is the one that matters. Regulators, internal investigators and your successor will treat the document as the authoritative map of what you owned, when you owned it, and what you did about it. A thin, generic or stale SoR is a governance problem long before it is a regulatory one.
Start from what you actually do, not the template
Most weak SoRs are weak because they begin with the FCA template and work backwards. Start instead with a blank page and write, in plain English, what you are accountable for in this role: which businesses, legal entities, functions, products, geographies and risk types. Then map each item to the relevant Prescribed Responsibility, Overall Responsibility or Senior Management Function. If something you do in practice does not map cleanly, that is the interesting question. Either the mapping needs rethinking, or the firm's responsibilities map does.
What good looks like: a reader who has never met you can describe, within five minutes, the perimeter of your role, where it touches other SMFs, and where the hand-offs sit.
Be specific about shared and divided responsibilities
Shared responsibilities are where SoRs most often fail under scrutiny. If two SMFs share accountability for, say, operational resilience of a critical business service, the SoR must say who leads, who contributes, how disagreements are resolved, and where the decision rights sit. Vague phrasing like "jointly responsible with the COO" invites a regulator to ask who was actually in the chair when the issue arose. If you cannot answer that in the document, you will have to answer it in an interview.
The same applies to divided responsibilities across legal entities, matrix reporting lines, or group versus solo arrangements. Name the entity. Name the committee. Name the escalation route.
Anchor every claim to evidence
For each responsibility, you should be able to point to: the committee or forum where it is discharged, the MI you receive, the delegations you have made and to whom, and the frequency of review. You do not need to put all of this in the SoR itself, but the Management Responsibilities Map, committee ToRs and delegation letters must be consistent with it. Inconsistencies between these documents are the single most common finding in enforcement cases involving senior manager conduct.
Run a line-by-line reconciliation before filing. If the SoR says you chair a committee that no longer meets, fix it before a regulator does.
Write for your successor
The best test of an SoR is whether someone taking over your role in six months could use it as a working handover document. That means describing not just what you are responsible for, but the known issues, remediation programmes, regulatory commitments and open supervisory matters that sit within your perimeter at the point of signing. A successor-ready SoR protects both of you: it establishes what you handed over and what they inherited.
Keep it current
Trigger a review whenever: your scope changes, a new product or entity enters your perimeter, a shared responsibility is renegotiated, an SMF around you changes, or a significant regulatory matter opens or closes. Annual reviews are a floor, not a ceiling. A dated SoR that no longer reflects reality is worse than no SoR at all, because it evidences that governance was not keeping pace.
The next decision
Pull your current SoR today and read it as if you were the successor, the internal investigator and the supervisor. If any of the three would struggle to understand what you own and how you discharge it, start the rewrite this week.
Frequently Asked Questions
How detailed should the SoR be?
Detailed enough that a reader can understand scope, boundaries and hand-offs without needing a conversation. Short enough that it is readable in one sitting. Most credible SoRs run to two or three pages of substantive content, supported by a clear link to the Management Responsibilities Map.
What should we do about responsibilities that are genuinely shared?
Name the sharing arrangement explicitly, identify the lead SMF, and describe how decisions are made and recorded. Shared accountability is permitted and sometimes unavoidable, but it must be legible. Ambiguity is the risk, not the sharing itself.
Who should review the SoR before it is filed?
At minimum: the SMF holder, the Chair or line manager, the Head of Compliance, and the company secretary or governance team responsible for the Responsibilities Map. For material roles, legal review is sensible, particularly where group structures or outsourcing arrangements are involved.
How do we handle interim or acting arrangements?
File an updated SoR for the acting holder, even if the arrangement is short. Supervisors expect to see the paper trail. Relying on informal cover without documentation is a common and avoidable finding.
What is the single most common weakness regulators flag?
Disconnection between the SoR and operational reality: committees that have been restructured, delegations that have moved, or responsibilities that have shifted following a reorganisation. The document on file no longer describes how the firm actually runs.
Frequently asked questions
How detailed should the SoR be?
Detailed enough that a reader can understand scope, boundaries and hand-offs without needing a conversation. Short enough that it is readable in one sitting. Most credible SoRs run to two or three pages of substantive content, supported by a clear link to the Management Responsibilities Map.
What should we do about responsibilities that are genuinely shared?
Name the sharing arrangement explicitly, identify the lead SMF, and describe how decisions are made and recorded. Shared accountability is permitted and sometimes unavoidable, but it must be legible. Ambiguity is the risk, not the sharing itself.
Who should review the SoR before it is filed?
At minimum: the SMF holder, the Chair or line manager, the Head of Compliance, and the company secretary or governance team responsible for the Responsibilities Map. For material roles, legal review is sensible, particularly where group structures or outsourcing arrangements are involved.
How do we handle interim or acting arrangements?
File an updated SoR for the acting holder, even if the arrangement is short. Supervisors expect to see the paper trail. Relying on informal cover without documentation is a common and avoidable finding.
What is the single most common weakness regulators flag?
Disconnection between the SoR and operational reality: committees that have been restructured, delegations that have moved, or responsibilities that have shifted following a reorganisation. The document on file no longer describes how the firm actually runs.
Related guides
How to Structure an MLRO Annual Report That Evidences Effective Financial Crime Controls
A practical guide to building an MLRO annual report that gives the board and the FCA genuine assurance on financial crime controls. After reading, you will know how to structure the document, what evidence to include, and where most reports fall short.
Structuring a PS21/3 Operational Resilience Self-Assessment That Evidences Impact Tolerance Testing
A practical guide to building an Operational Resilience self-assessment that credibly evidences impact tolerance testing to the FCA and PRA. After reading, you will know how to structure the document, sequence the evidence, and surface the vulnerabilities supervisors expect to see acknowledged.
Structuring an ICAAP Under SS31/15 That Evidences Robust Stress Testing
A practical guide to building an ICAAP document under PRA SS31/15 where stress testing is genuinely integrated, credible, and proportionate. Readers will understand how to structure the narrative, calibration, and board engagement so Pillar 2A outcomes reflect the firm's actual risk profile rather than supervisory concern about weak analysis.
How to Prepare a Credible FCA Threshold Conditions Attestation Under Supervisory Pressure
This guide sets out how to prepare an attestation on compliance with the FCA's Threshold Conditions when supervisors have raised concerns. It explains what credible looks like, where attestations commonly fall short, and how to sequence board, executive, and evidence work so the submission holds up.
How to Prepare a Credible Operational Resilience Self-Assessment
This guide sets out what a credible Operational Resilience self-assessment looks like under the PRA and FCA regimes, with particular focus on evidencing impact tolerance testing. After reading it, you will know how to structure the document, where boards usually fall short, and what supervisors expect to see when they challenge your mapping, scenarios and vulnerabilities.
Where internal confidence may exceed external evidence
Polar Insight helps leadership teams test critical assumptions against stakeholder, market, regulatory, and operational reality before risk compounds.
Explore Stakeholder Proximity