In January 2024, The Pensions Regulator laid its General Code in Parliament, consolidating ten existing codes covering pension governance and administration. The original announcement anticipated commencement on 27 March; the regulator’s later annual report records actual commencement on 28 March 2024. The historical distinction matters. The code brought expectations into a more coherent format, while many underlying standards were already established. For multinational pension sponsors, the practical question is whether local governance can be demonstrated.
Begin with how the scheme actually operates
A collection of policies does not by itself show that a pension scheme is governed effectively. Reviewers should understand who makes decisions, what information reaches them and how outstanding matters are resolved. A governance review can compare the written arrangements with actual practice. It should identify where a task depends on an individual rather than a documented responsibility that another person could take over when needed.
This editor recommends a proportionate gap review that records the expectation, evidence examined, conclusion and owner of any remedial work. The governing body should be able to understand why a gap matters and how management proposes to address it. A lengthy checklist is less useful when it gives no account of the underlying risk or treats every incomplete document as equally significant to members and the scheme.
Connect oversight to service delivery
Pension administration often involves advisers and external providers. The governing body needs enough information to assess delivery and challenge unresolved problems. Reporting should explain exceptions as well as averages. An apparently satisfactory service measure may conceal a small group of members facing repeated delays. A review should establish who investigates those cases and how the governing body knows that the underlying problem has been addressed.
Delegation should have a clear scope. A service agreement can describe the provider’s responsibilities, but the governing body still needs an intelligible account of what has been delegated and what remains with it. The review should examine how material changes are reported. It should also consider whether the governing body receives information in time to make a decision, rather than after an operational problem has already escalated.
Use risk assessment to direct attention
The regulator’s announcement emphasised effective systems of governance and periodic review through own risk assessment. For a scheme subject to the relevant requirements, the exercise should connect risks with the procedures intended to manage them. Management should distinguish a control that exists on paper from one that has been used and reviewed. The governing body can then ask which unresolved weaknesses deserve the greatest attention.
A proportionate assessment should reflect the scheme’s actual circumstances. Complexity, service arrangements and member needs can differ substantially. Copying another scheme’s risk register may create the appearance of completeness while missing a material local issue. The responsible body should be able to explain its choices, including why a particular risk has received further work and how it will know whether that work has been effective.
Coordinate with the multinational sponsor
The sponsor’s finance and benefits teams can support governance by providing clear information about employer decisions and commitments. They should understand the boundary between group oversight and the local governing body’s responsibilities. A common reporting framework can make issues visible across countries, but it should not imply that one group committee discharges every local trustee obligation or can override a scheme’s established decision process.
The reporting framework should identify what requires escalation to the sponsor and what remains a local matter. Budget, provider changes and material benefit proposals may need coordinated decisions. Management should know who supplies the relevant information and who signs off the resulting action. Defined escalation helps avoid situations where a significant issue is known in one part of the organisation but never reaches the body able to address it.
Keep legal requirements and code expectations distinct
The code is a statement of regulatory expectations within the pensions framework. A governance review should identify the applicable statutory duties as well as relevant code provisions. That distinction supports better advice and clearer decisions. An adviser should explain the significance of a finding rather than refer to every expectation as an identical legal obligation. Management can then assess the appropriate response with the governing body.
This editor recommends using the General Code as a basis for a documented discussion about evidence, responsibilities and improvement. The 2024 consolidation gives that discussion a common reference point. Its value depends on whether the scheme can explain how it operates and show progress on material weaknesses. A proportionate record of decisions and follow up is more useful than a complete looking library of policies that nobody can connect to practice.
Share this:
- More [2]
