Structuring an MRA Remediation Response to the PRA That Closes Findings Cleanly

An MRA response is not a project plan. It is a supervisory document that fixes the perimeter of the finding, defines what closure looks like, and commits the firm to a specific set of actions the PRA can test. Get the framing wrong and a narrow finding becomes a thematic review. Get it right and you close the item on the original terms, on your original timeline, without inviting adjacent questions.

Key Executive Takeaways

• The response must mirror the exact language of the MRA. Any broader framing invites the supervisor to expand what closure requires.
• Root cause analysis should be specific and bounded. Vague causes such as "cultural" or "governance" issues almost always trigger wider scope.
• Closure evidence must be defined upfront and agreed with the supervisor, not left to interpretation at the point of sign-off.

Start with the supervisor's words, not your own

Read the MRA letter carefully and lift the operative phrasing directly into your response. If the PRA identified a weakness in "the calibration of IRB PD models for the SME portfolio," your response addresses exactly that. Not IRB models generally. Not SME credit risk broadly. The moment you widen the frame, whether to look diligent or to bundle related work, you concede that the issue is larger than the supervisor originally scoped it.

This is the single most common error. Firms restate the finding in their own terms, usually more expansively, thinking it demonstrates seriousness. It demonstrates uncertainty, and supervisors respond by testing the wider perimeter.

Root cause: specific, bounded, defensible

The root cause section decides whether the MRA closes as a discrete item or metastasises. Two failure modes dominate.

First, causes that are too narrow ("a manual error in the quarterly recalibration process") invite the supervisor to ask why controls did not catch it, which opens control environment questions. Second, causes that are too broad ("insufficient second line challenge") invite thematic review of the second line across the firm.

The defensible middle is a cause specific enough to be fixed by a defined action, but not so narrow that it implies a control failure the supervisor has not yet identified. Test every root cause statement against the question: what else could a supervisor legitimately ask about if this is true? If the answer is "a great deal," rewrite it.

Define closure evidence before you commit to actions

Work backwards. Before you list remediation actions, define what evidence you will produce to demonstrate closure and, ideally, agree this with the supervisor in a pre-submission call. Typical closure evidence includes: a specific policy change with board minute reference, a validated model recalibration with independent review sign-off, or a defined period of clean control testing.

If closure evidence is undefined, the supervisor sets the bar at the point of review, and they will set it based on their comfort, not your workplan. Firms consistently underestimate how much this costs them in time and scope creep.

Sequence actions to demonstrate irreversibility

Structure the remediation plan so that the earliest actions produce evidence of structural change, not activity. A supervisor who sees a governance decision, a policy amendment, and a control redesign in the first sixty days will treat the plan as credible. A supervisor who sees workstream mobilisation, steering committees, and gap analyses will assume the real work has not started.

Avoid milestones that read as internal project management. Every milestone should produce something the PRA can point to as evidence of change.

Manage the interim update discipline

Interim updates are where scope expands. A well-intentioned progress note that mentions related work streams, adjacent risks the team has spotted, or broader improvement initiatives will be read as an admission that the original scope was insufficient. Restrict updates to the actions committed in the response. If genuinely new issues emerge, escalate them through separate channels with separate framing.

What good looks like at closure

A clean closure submission does three things: it maps each committed action to the evidence produced, it references the original MRA language to confirm the finding is addressed on its own terms, and it says nothing about broader work. Silence on adjacencies is a feature, not an omission.

Your next decision

Before your next MRA response leaves the building, have someone outside the remediation team read it with one question in mind: what would a supervisor be entitled to ask about next, based only on what this document says? If the answer is anything beyond "whether you did what you committed to," rewrite before you send.

Frequently Asked Questions

Should we acknowledge related weaknesses we have identified internally?

Not in the MRA response. Address them through separate governance and, if material, through your normal supervisory dialogue. Bundling them into the MRA response converts your discretionary disclosure into a supervisory commitment.

How much detail should the root cause analysis contain?

Enough to justify the remediation actions and no more. If a supervisor cannot see why your actions logically follow from the cause, add detail. If detail invites questions about adjacent processes, cut it.

What if the PRA pushes back and asks for broader scope?

Engage on the specifics of their concern rather than accepting the expansion wholesale. Ask what evidence would satisfy them within the original scope. Often the pushback is about closure evidence, not scope, and can be resolved without widening the perimeter.

Who should own the response internally?

The accountable SMF for the risk area, supported by someone with direct supervisory relationship experience. Do not delegate drafting to the remediation programme team. They will write a project document, not a supervisory one.

When should we involve external advisers?

Before drafting, not after. Advisers add most value shaping root cause framing and closure evidence definition. Bringing them in to review a near-final draft usually produces marginal improvements to a document that is already committed to the wrong frame.