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.
The ORSA board narrative is where most insurers quietly overcommit. In trying to demonstrate a robust forward-looking assessment, boards approve documents that read as strategic contracts with the PRA: specific growth paths, capital trajectories, reinsurance structures, all stated with a precision the business never intended. Twelve months later, when the plan shifts, the supervisor asks why. The fix is not to weaken the assessment. It is to structure the narrative so that rigour sits in the risk and capital analysis, while strategy is expressed as a decision framework rather than a fixed path.
Key Executive Takeaways
- The PRA wants evidence that the board understands its risks under stress and has capital to match, not a five-year commitment to a specific strategy.
- Separate the forward-looking assessment (rigorous, quantified, owned) from strategic optionality (framed as decision triggers and ranges, not fixed choices).
- The most common failure is confusing the base case business plan with the ORSA, which locks the board into numbers it will need to revise within months.
Start with the assessment horizon, not the plan
The PRA's forward-looking assessment expectation under SS4/18 and the wider Solvency II ORSA framework asks whether the board has considered risks over a horizon appropriate to the business model, typically three to five years. That is not the same as endorsing the three-year plan. Anchor the narrative on the horizon and the material risks visible across it. The business plan is an input, not the subject.
Good ORSAs open with a short board statement of the assessment horizon, the reasons for it (product duration, reinsurance cycle, capital replenishment time) and an explicit acknowledgement that strategy within that horizon will evolve. This single framing move creates the space you need later.
Build the risk and capital spine before the strategic content
The assessment must stand on its own. Structure it in this order:
- Risk profile and material changes since the last ORSA, with quantified movement.
- Stress and scenario results against own funds and SCR, including reverse stress tests that identify the point of business model failure.
- Capital management actions modelled, with the sequencing, triggers and estimated timing of each.
- A clear statement of overall solvency needs, distinct from the SCR, with the board's reasoning.
This spine is where rigour lives. It is also where boards most often underinvest, delegating too much to the actuarial function and signing off analysis they cannot defend in a supervisory meeting. The board narrative should show challenge: which assumptions the board pushed back on, what alternative scenarios it asked for, what it concluded.
Express strategy as ranges and triggers
Once the risk and capital spine is credible, strategic content can be expressed as optionality rather than commitment. Instead of "we will grow bulk annuities by X percent per year," describe the corridor within which growth is consistent with risk appetite, the capital headroom required to enter it, and the triggers that would cause the board to pause, accelerate or exit. Do the same for asset allocation, reinsurance and M&A.
This is not vagueness. It is precision about the decision framework rather than the decision. Supervisors respond well to this when the underlying risk analysis is strong, because it demonstrates the board is actually governing the strategy rather than rubber-stamping it.
Handle management actions honestly
The most scrutinised area in recent PRA feedback has been the credibility of management actions in stress. If your ORSA relies on raising capital, cutting new business or restructuring reinsurance under stress, the narrative must show why those actions are executable in the specific conditions modelled, who has authority, and what the lead time is. Vague references to "management action" invite challenge and constrain you later, because the PRA will hold you to actions you claimed were available.
What good looks like
A strong ORSA board narrative is around 40 to 60 pages, opens with a board statement that owns the assessment, contains a risk and capital spine that could withstand a Section 166, and expresses strategy as governed optionality. It reads as a document the board wrote, not one written to the board.
Next step
Before the next ORSA cycle, ask your CRO and Chief Actuary to map every strategic commitment in the current document and classify each as fixed, ranged or trigger-based. That single exercise usually reveals where the last ORSA overcommitted, and where the next one needs to reframe.
Frequently Asked Questions
How specific do management actions need to be?
Specific enough to be executable: named action, authority, lead time, capital or liquidity impact, and the conditions under which the action remains viable. If an action depends on market access or counterparty willingness, say so and stress test the assumption.
Can the ORSA horizon differ from the business plan horizon?
Yes, and often it should. The business plan may run three years while the ORSA horizon extends to five to capture reinsurance renewal cycles or longevity trend risk. Explain the reasoning explicitly.
How do we handle strategic initiatives the board has not yet approved?
Include them as scenarios within the forward-looking assessment, with the capital and risk implications quantified, but frame them as options the board is evaluating rather than decisions taken. This preserves flexibility while showing the PRA you have considered them.
What is the right level of board involvement in drafting?
The board should own the assessment horizon, the risk appetite framing, the challenge on scenarios and management actions, and the final overall solvency needs statement. Drafting can be executive-led, but if the board cannot defend the document line by line in a supervisory meeting, it is not ready.
How often should the ORSA be refreshed outside the annual cycle?
Whenever the risk profile changes materially: a large transaction, a significant reinsurance change, a shift in asset strategy, or a market event that invalidates key scenarios. Waiting for the annual cycle in these cases is itself a supervisory concern.
Frequently asked questions
How specific do management actions need to be?
Specific enough to be executable: named action, authority, lead time, capital or liquidity impact, and the conditions under which the action remains viable. If an action depends on market access or counterparty willingness, say so and stress test the assumption.
Can the ORSA horizon differ from the business plan horizon?
Yes, and often it should. The business plan may run three years while the ORSA horizon extends to five to capture reinsurance renewal cycles or longevity trend risk. Explain the reasoning explicitly.
How do we handle strategic initiatives the board has not yet approved?
Include them as scenarios within the forward-looking assessment, with the capital and risk implications quantified, but frame them as options the board is evaluating rather than decisions taken. This preserves flexibility while showing the PRA you have considered them.
What is the right level of board involvement in drafting?
The board should own the assessment horizon, the risk appetite framing, the challenge on scenarios and management actions, and the final overall solvency needs statement. Drafting can be executive-led, but if the board cannot defend the document line by line in a supervisory meeting, it is not ready.
How often should the ORSA be refreshed outside the annual cycle?
Whenever the risk profile changes materially: a large transaction, a significant reinsurance change, a shift in asset strategy, or a market event that invalidates key scenarios. Waiting for the annual cycle in these cases is itself a supervisory concern.
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.
How to Challenge a PRA Pillar 2A Add-On Without Damaging the Relationship
This guide sets out how to structure a technically robust challenge to a PRA Pillar 2A capital add-on while protecting your supervisory standing. After reading, you will know how to sequence the challenge, frame the evidence, and manage the supervisory dynamic to secure a meaningful reduction.
How to Structure a Recovery Plan Playbook That Passes PRA Credibility Tests
This guide sets out how to build a Recovery Plan playbook that meets the PRA's credibility, usability and timeliness expectations without creating documents that could damage confidence if they surface externally. After reading, you will know how to sequence indicators, options and governance triggers so the plan works as a live management tool rather than a compliance artefact.
How to Structure an Operational Resilience Self-Assessment That Withstands Regulator Challenge
This guide sets out how to build an operational resilience self-assessment that holds up to FCA and PRA impact tolerance scrutiny. After reading, senior leaders will know how to sequence evidence, frame judgements, and pre-empt the challenges supervisors are most likely to raise.
How to Structure a Reverse Stress Testing Narrative for PRA Board Attestation
This guide sets out how to build a Reverse Stress Testing (RST) narrative that credibly supports board attestation under PRA expectations. After reading, you will know how to sequence the analysis, frame the point of non-viability, and present findings in a way that survives supervisory challenge.
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