Skip to main content

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.

Basel 3.1 board papers fail in one of two ways. Either they understate the capital impact to keep the room calm, in which case the PRA, internal audit, or the CFO's own reforecast catches it later, or they lead with a wall of RWA arithmetic that buries the strategic choices the board actually needs to make. The paper that gets approved does neither. It presents the impact honestly, frames the decisions cleanly, and gives directors the confidence that management has already stress-tested the answer.

Key Executive Takeaways

  • Lead with the capital impact range and the strategic choices it forces, not with technical rule mechanics or implementation milestones.
  • Show the output floor trajectory, standardised approach recalibrations, and model approval risks as one integrated number, not three separate annexes.
  • Pre-wire the paper with the Chair, CRO, and CFO before it reaches committee so the debate in the room is about response, not credibility of the numbers.

Frame the paper around the decision, not the rule

The board is not approving Basel 3.1. It is approving management's response to it. Your opening page should state, in plain terms: the day one impact on CET1, the fully loaded impact at end of transitional period, the business lines most affected, and the two or three decisions requested. Everything else is supporting evidence.

Most first drafts get this backwards. They open with a summary of the PRA's near final rules, walk through the credit risk, market risk, and operational risk changes, and only arrive at the capital number on page nine. By then the audit committee chair has stopped reading and the NEDs are asking about implementation cost instead of strategic response.

Present the capital impact as a range, with the assumptions visible

A single point estimate invites challenge and, worse, invites the board to treat it as certainty. Give a range: a central case, a downside reflecting output floor bite plus model approval delays, and an upside reflecting successful IRB retention and portfolio actions already underway. Show the CET1 ratio impact in basis points at each stage of the transitional path from 2027 through 2030.

What good looks like: one page, one chart, three scenarios, and a short table showing which assumptions drive the difference between them. The assumptions most worth surfacing are output floor calibration by portfolio, SME and infrastructure support factor treatment, residential mortgage LGD floors, and the fate of any IRB models currently in the PRA queue.

Do not net off mitigations before showing the gross impact

The most common credibility failure is presenting a net number after assumed management actions, such as RWA optimisation, model recalibration, or business mix changes. The board cannot assess whether those actions are realistic if it never sees the gross figure. Show the gross impact first, then each mitigation lever separately, with an execution confidence rating and a timeline. If a mitigation depends on PRA model approval, say so, and quantify the delay risk.

Address the output floor honestly

For IRB firms, the output floor is where papers most often lose credibility. Directors who have been briefed for years on IRB capital efficiency need to understand that the floor progressively erodes it. Show the floor's bite year by year. Identify the portfolios where standardised RWAs will exceed modelled RWAs at 72.5%. If the floor changes the economics of specific product lines, say which ones, and flag the strategic decisions that follow: reprice, exit, restructure, or accept lower returns.

Pre-wire before you paper

The paper should not be the first time the Chair, CRO, CFO, and audit committee chair see the numbers. Walk each of them through the analysis individually. Their challenges will improve the paper, and their support in the room will shift the debate from "are these numbers right" to "is our response sufficient". If the CFO disagrees with the range, resolve it before submission, not during.

What to request

End with specific decisions: approval of the implementation programme budget, endorsement of the capital plan revisions, sign off on the ICAAP linkage, and agreement on the disclosure position for the next results. Vague requests for "noting" invite drift.

The next move

Before your next draft, strip the paper back to four pages: impact, choices, mitigations, decisions requested. If it cannot say what matters in four pages, the analysis underneath is not yet ready for the board.

Frequently Asked Questions

How much technical detail belongs in the main paper versus annexes?

Main paper: impact numbers, strategic choices, decisions requested, and the one or two rule changes that materially drive the outcome. Annexes: rule by rule walkthroughs, methodology notes, and model inventory. If a NED needs the annex to understand the recommendation, the main paper is not doing its job.

Should we show the impact gross or net of Pillar 2A offset?

Show both, clearly labelled. The PRA has signalled Pillar 2A recalibration to avoid double counting, but the timing and quantum are not certain. Presenting only the net number assumes a regulatory outcome you do not control.

How do we handle the disclosure question if the numbers are still moving?

Agree a disclosure position with the CFO and head of investor relations before the paper is tabled. The board should approve a range and a communication approach, not a specific number that may shift before the next results. Consistency between board approved numbers and external disclosure is what internal audit and the PRA will test.

What is the single most common reason these papers get sent back?

Mitigations presented as certainties. If the paper claims RWA optimisation will recover 40 basis points but cannot show which portfolios, which actions, and which quarter, the audit committee will assume the gross impact is the real number and ask why management is not planning accordingly.

Frequently asked questions

How much technical detail belongs in the main paper versus annexes?

Main paper: impact numbers, strategic choices, decisions requested, and the one or two rule changes that materially drive the outcome. Annexes: rule by rule walkthroughs, methodology notes, and model inventory. If a NED needs the annex to understand the recommendation, the main paper is not doing its job.

Should we show the impact gross or net of Pillar 2A offset?

Show both, clearly labelled. The PRA has signalled Pillar 2A recalibration to avoid double counting, but the timing and quantum are not certain. Presenting only the net number assumes a regulatory outcome you do not control.

How do we handle the disclosure question if the numbers are still moving?

Agree a disclosure position with the CFO and head of investor relations before the paper is tabled. The board should approve a range and a communication approach, not a specific number that may shift before the next results. Consistency between board approved numbers and external disclosure is what internal audit and the PRA will test.

What is the single most common reason these papers get sent back?

Mitigations presented as certainties. If the paper claims RWA optimisation will recover 40 basis points but cannot show which portfolios, which actions, and which quarter, the audit committee will assume the gross impact is the real number and ask why management is not planning accordingly.

Related guides

Boards, Governance & Defensibility

Structuring a Consumer Duty Board Champion Report That Evidences Good Outcomes

This guide sets out how to write a Consumer Duty board champion report that demonstrably evidences good outcomes without triggering FCA product intervention or supervisory escalation. It shows senior leaders what to include, what to leave out, and how to frame difficult findings so the board can act without handing the regulator a case file.

Regulatory changeRegulatorsBoards
4 min readRead guide →
Boards, Governance & Defensibility

How to Structure a Whistleblowing Annual Report to the Board Under SYSC 18

This guide sets out how to build a board-level whistleblowing report that meets FCA SYSC 18.6 expectations while protecting reporter identity and case confidentiality. After reading, you will know what to include, what to leave out, and how to frame themes so the board can discharge oversight without becoming a de facto investigations committee.

Regulatory changeBoardsRegulators
4 min readRead guide →
Boards, Governance & Defensibility

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.

Regulatory submissionRegulatorsBoards
4 min readRead guide →
Boards, Governance & Defensibility

Regulated Industry Governance Best Practice: A Practical Guide

This guide sets out what governance best practice actually looks like in regulated financial services, from board composition to evidencing challenge. After reading it, senior leaders will know where their governance is likely to fail regulatory scrutiny and what to fix first.

Regulatory changeBoardsRegulators
4 min readRead guide →
Boards, Governance & Defensibility

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.

Regulatory submissionRegulatorsBoards
4 min readRead guide →

Where internal consensus may be mistaken for validation

Polar Insight's Decision Rooms bring outside challenge to a live decision, so blind spots and untested assumptions surface before commitment, not after.

Explore Decision Rooms