How to Structure an SMCR Statement of Responsibilities That Withstands FCA Scrutiny

A Statement of Responsibilities is the single document the FCA will reach for when something goes wrong. If it is vague, inconsistent with the Management Responsibilities Map, or silent on a function the firm actually performs, the firm has a problem before any investigation begins. Good SoRs are not long. They are precise, current, and match reality.

Start from what the Senior Manager actually does

Most weak SoRs are written top down from the rulebook. Strong ones are written bottom up from the role. Sit with the Senior Manager and map what they decide, what they approve, which committees they chair or sit on, what budget they control, and what they are the final escalation point for. Then test that against the Prescribed Responsibilities and any Overall Responsibility allocations. The SoR should read like a description of a real job, not a compliance artefact.

If you cannot describe the responsibility in a sentence a non-specialist would understand, it is not yet clear enough for the FCA.

Allocate Prescribed Responsibilities with intent

PRs are where accountability gaps most often appear. Common failure modes:

• Splitting a PR between two Senior Managers without a clear primary owner.
• Allocating a PR to someone whose role does not give them genuine authority over the activity.
• Leaving a PR with the CEO by default because no one else wants it.

For each PR, ask: does this person have the authority, information, and resource to discharge it? If the answer is no, the allocation will not survive scrutiny. Document the rationale for non-obvious allocations in the Responsibilities Map, not buried in board minutes.

Address shared and divided responsibilities head on

The regime permits sharing and division, but both create risk if poorly handled. Where responsibility is shared, the SoR of each Senior Manager must describe their specific contribution and how the interface works. Where it is divided (for example, between a UK CEO and a group function head), the boundary must be explicit, including what happens when the two disagree. A statement that simply says "shared with X" is not sufficient.

Keep the Responsibilities Map in lockstep

The SoR describes one individual. The Map shows how all SoRs fit together. The FCA will read them side by side. Three tests to run before sign off:

1. Does every business activity, function, and legal entity appear on the Map with a named owner?
2. Do the Map and the individual SoRs describe the same responsibilities in the same language?
3. Are reporting lines on the Map consistent with the committees and escalation routes described in the SoRs?

Inconsistencies between these documents are the single clearest signal to a supervisor that governance is not being actively maintained.

Write for the reader who will use it in anger

Assume the reader is a supervisor investigating a specific incident two years from now. They will ask: who was responsible for this at the time? The SoR should answer that question without ambiguity. Avoid aspirational language, matrix descriptions, and references to policies that explain nothing. Date every version and retain prior versions with clear change logs.

Refresh when the role changes, not when the audit comes

Material changes include a new business line, a restructure, a change of committee chair, a reallocation of a PR, or a change in regulated perimeter. Each should trigger a review of the affected SoRs and, where significant, a Form J submission. Firms that batch-update SoRs annually tend to accumulate drift that becomes hard to explain.

What good looks like

A Senior Manager can read their own SoR and confirm, without hesitation, that it describes their job. The Chair can read the full set and see no gaps, no overlaps, and no orphaned activities. The supervisor can read the Map and the SoRs together and understand exactly who decides what.

If you cannot say all three today, the next action is a line by line review of the SoRs of your most recently appointed and your most recently restructured Senior Managers. That is where gaps typically sit.

Frequently Asked Questions

How detailed should an SoR actually be?

Detailed enough that a supervisor can identify the decision maker for any material activity in the person's remit, but not so detailed that it becomes a job description. Most effective SoRs run to two or three pages. If yours is longer, it is probably describing process rather than accountability.

What is the right way to handle a Senior Manager with group responsibilities?

Describe the UK regulated firm responsibilities first and in full. Then address the group dimension separately, making clear which decisions sit with the UK entity and which are reserved to group. Ambiguity here is a frequent source of FCA concern, particularly in subsidiaries of overseas parents.

When does a change require a Form J resubmission?

Any significant change to the Senior Manager's responsibilities. In practice this includes reallocation of a Prescribed Responsibility, material change in business scope, or a change in reporting line that affects authority. If in doubt, resubmit. Late or missed submissions are easier to spot than most firms realise.

Who should own the SoR drafting process?

The Senior Manager owns the content. The company secretary or SMCR lead owns the consistency and version control. HR and Legal provide support. If Compliance is drafting SoRs on behalf of Senior Managers with limited input from the individual, that is itself a governance weakness.

How should we handle interim or acting arrangements?

Issue a fresh SoR for the interim holder for any period beyond 12 weeks, and document the arrangement in the Map from day one. Interim periods are a common source of accountability gaps because firms treat them as temporary and defer the paperwork.