Own-Risk Assessment (ORA)
Legal Basis
The ORA requirement derives from Article 28 of IORP II (EU 2016/2341) and is transposed in Irish law as Section 64AL of the Pensions Act 1990 (as inserted by the Pensions (Amendment) Act 2022, implementing S.I. 128/2021). Trustees must conduct and document an ORA at least every three years, or following any significant change in the scheme’s risk profile. The ORA is one of the most substantive governance deliverables under IORP II. It is the primary mechanism by which the trustee board demonstrates that it has conducted a thorough, forward-looking assessment of the risks the scheme faces — and that governance and investment decisions are informed by that assessment.What the ORA Must Cover
Article 28(2) IORP II specifies that the ORA must cover, at minimum:- The overall risk profile of the scheme, covering all material risks
- The risk tolerance and risk appetite of the scheme
- A forward-looking assessment of risks to members and beneficiaries
- Both qualitative and, where appropriate, quantitative assessment of risks
- The interdependency between different risk categories
- Links to the investment strategy and funding strategy
- The effectiveness of risk mitigation measures in place
The ORA as a Living Document
The ORA is not a one-time filing. It is a living governance tool that must remain current, be revisited at trigger events, and be actively used in board decision-making. The PA has identified ORA quality as a primary supervisory focus for 2025–2029. Trustees must lead the ORA process — not merely sign a document prepared by a consultant or KFH. Where board minutes record only a one-line adoption of the ORA, the PA will question whether trustees engaged substantively with the content.Common Weaknesses Identified by the Pensions Authority
The following weaknesses appear repeatedly in PA supervisory reviews:| Weakness | PA Expectation |
|---|---|
| Viability / sustainability risks absent | ORAs must address the long-term viability of the scheme and the financial sustainability of the sponsoring employer |
| Outsourcing risks generic or absent | Where all key functions are outsourced, outsourcing concentration risk and exit risk must be scheme-specific |
| DORA / ICT risks not reflected | From January 2025, all schemes ≥16 members must address ICT and cyber risks proportionate to digital exposure |
| Risk appetite without current status | The ORA must state whether each risk currently sits within or outside the defined tolerance — not just list appetite levels |
| No member cohort analysis | DC schemes must link risk assessments to the actual demographics and contribution history of the membership |
| Board minutes show no substantive engagement | The PA checks whether board minutes record genuine discussion — not just adoption of a pre-agreed document |
ORA Methodology: What a Quality ORA Looks Like
A quality ORA is not a generic risk assessment. It is a scheme-specific, forward-looking document that demonstrates genuine trustee engagement with the risks facing the scheme and its members. The Pensions Authority can readily distinguish between a substantive ORA and a template document that has been minimally adapted.How an ORA Differs from a Generic Risk Assessment
Generic Risk Assessment
Compliant IORP II ORA
- Scheme-specific data: The ORA references the scheme’s actual investment portfolio, funding level, membership profile, and sponsor financial position
- Forward-looking: The analysis considers how risks may evolve over the scheme’s time horizon — not just current conditions
- Integrated: The ORA links to the investment policy and (where applicable) the funding strategy, evidencing that risk appetite is reflected in strategic decisions
- Evidenced: Risk assessments are supported by data and analysis, not just assertions
- Board-owned: The ORA is formally presented to and discussed by the trustee board, with the discussion recorded in board minutes
- Actionable: Where risks are identified as elevated, the ORA specifies the actions the board will take, with owners and timelines
Risk Appetite and Tolerance — What Article 28 Requires
Article 28(2) of IORP II requires the ORA to cover the scheme’s risk tolerance and risk appetite. The PA’s guidance clarifies that this means more than defining a tolerance level — it means assessing whether the scheme is currently operating within that tolerance. The ORA must therefore state, for each material risk category:- Risk appetite — the level of risk the board is willing to accept in pursuit of scheme objectives (qualitative or quantitative)
- Risk tolerance threshold — the boundary at which risk becomes unacceptable
- Current risk status — whether current risk in this category sits within, approaching, or outside the defined tolerance
- If outside or approaching tolerance — the specific actions the board is taking to bring risk back within acceptable levels, with responsible persons and target dates
The 8 Risk Categories Trustees Should Consider
The following risk categories align with the Pensions Authority’s ORA guidance and the requirements of Article 28 IORP II. Every ORA should address each category, with the depth of analysis proportionate to the category’s materiality for the specific scheme.1. Investment Risk
1. Investment Risk
2. Liquidity Risk
2. Liquidity Risk
3. Concentration Risk
3. Concentration Risk
4. Operational Risk
4. Operational Risk
5. Insurance and Other Risk Mitigation Techniques
5. Insurance and Other Risk Mitigation Techniques
6. ESG and Sustainability Risk
6. ESG and Sustainability Risk
7. New and Emerging Risks
7. New and Emerging Risks
8. Sponsor Risk (Employer Covenant)
8. Sponsor Risk (Employer Covenant)
ORA Documentation Requirements
The written ORA record must contain:- Date of the ORA and the names of the trustees who participated in the process
- Scope confirmation: confirmation that all required risk categories were considered
- Scheme-specific data used as inputs (membership profile, funding level, investment portfolio summary, actuarial data as applicable)
- Risk assessment for each category: risk identification, likelihood/impact assessment, current controls, residual risk rating
- Forward-looking analysis: how each risk may evolve over the scheme’s time horizon
- Links to investment strategy and funding policy: evidence that the ORA informs strategic decisions
- Actions arising: where elevated risks are identified, specific actions assigned to named individuals with due dates
- Board sign-off: formal record of the trustee board’s review and approval of the ORA, including the date of board sign-off
- Version control: document version number, date, and history of previous ORA versions
Who Signs Off the ORA
The ORA must be formally reviewed and approved by the trustee board. While the Risk Management KFH leads the ORA process and drafts the report, the ORA is a board document — not a KFH deliverable. The board’s review and sign-off must be recorded in board meeting minutes, which form part of the compliance evidence trail.Link to the Governance Framework
The ORA does not stand alone. It must be linked to:- The investment policy: risk appetite identified in the ORA must be reflected in the investment strategy
- The risk management policy: the ORA methodology must be consistent with the documented risk management framework
- The risk register: risks identified in the ORA should be captured in the scheme’s ongoing risk register, owned by the Risk Management KFH
The 3-Year Review Cycle and Trigger Events
Trustees must conduct a new ORA at least every three years. However, certain events require an earlier review regardless of when the last ORA was completed:| Trigger Event | Why It Matters |
|---|---|
| Significant change in investment strategy | A new asset allocation or investment mandate changes the scheme’s risk profile materially |
| Major sponsor event | Sponsor restructuring, ownership change, financial distress, or insolvency significantly changes sponsor risk |
| Material change in membership profile | A large bulk transfer, scheme merger, or significant change in active/deferred/pensioner mix affects cash flow and liability profile |
| Significant funding level change | A material deterioration (or improvement) in the funding level alters the risk landscape |
| Regulatory change | New legislative requirements may create compliance risk not captured in the existing ORA |
| Material operational failure | A significant operational incident (fraud, data breach, administrator failure) triggers a reassessment of operational risk |
| Significant market event | An extreme market event that affects the scheme’s investment portfolio may require an updated risk assessment |
How PensionsPortal.ie Automates ORA
PensionsPortal.ie’s ORA workflow reduces the time and effort required to produce a compliant, board-ready ORA — while maintaining the quality and scheme-specificity that the Pensions Authority requires.Data Import
Risk Category Assessment
AI-Assisted Narrative Generation
Human Review Gate
Board Presentation and Sign-Off
Pensions Authority References
- ORA Guidance for Trustees — Pensions Authority
- Code of Practice for Trustees (Final), Section 6 — ORA requirements
- IORP II Directive, Article 28: Own Risk Assessment
- Pensions Act 1990, Section 64AL: Own Risk Assessment (as inserted by Pensions (Amendment) Act 2022)
- S.I. 128/2021, Regulation 29: ORA implementation