Baroness Drake (Lab)

My Lords, I declare my interest as a DB pension scheme trustee as recorded in the register. I thank my noble friend Lord Davies for securing this debate. This is an important code, and it should not pass without comment. As the Explanatory Memorandum and my noble friend observe, while aggregate DB funding levels have improved in recent years, financial markets and economic conditions are changeable and funding positions can quickly deteriorate. There is a dynamic in the pensions world related to economic circumstances, whether fiscal policies, investment returns, gilt yields or the impact of technologies on markets, to name but a few. An intended purpose of the code is to allow TPR to be more proactive in identifying and mitigating emerging risks in a targeted way. There have been significant instances over the past 30 years of regulatory failure to identify or respond quickly to emerging risks in DB pension provision, some with dreadful consequences. What do the Government believe are the most compelling levers in this code that will materially improve mitigating such emerging risks? The new code sets two key requirements: planning for the length of the scheme’s journey plan to get to full funding at an appropriate pace of de-risking and assessing current funding positions when carrying out valuations. As part of that planning, the code trustees must set a funding and investment strategy���that is, the journey to getting to the planned endgame for the scheme. The strategy must set out how the trustees will transition from the scheme’s current funding position to low employer dependency funding when the scheme is mature. In making that transition, how risk can be supported by the employer and the strength of the scheme has to be made clear. During the consultation a lot of concern was expressed that the new code could weaken an important fiduciary power of trustees to make the investment allocation decisions by requiring trustees to invest in line with the investments set out in the funding and investment strategy that must be agreed with the sponsoring employers. In response to those concerns, although changes have been made to the code to clarify that decisions in relation to the scheme’s investment allocation are not constrained by the notional investment allocations in the funding and investment strategy, an inference remains that, in most instances, TPR expects trustees to align their investment strategy with the funding and investment strategy. Will the Minister confirm unequivocally that the code will not remove the power of existing trustees to decide on the scheme’s investment allocation? It is an important power in addressing moral hazard. The code places a welcome greater emphasis on the strength of the sponsoring employer covenant, which is of fundamental importance but is often lost in debate, when considering funding and investment risk. The level of cash generated by a sponsoring employer and its future prospects will be key determinants of how much investment risk a scheme should take. The strength of an employer covenant can change very quickly following mergers, acquisitions, restructurings et cetera. Such changes may result in changes to the level of debt in a company, dividend policy, free cash flow, covenant and longevity. The code requires any funding deficits to be repaid as quickly as the sponsor can reasonably afford, but trustees will have to consider the impact on the employer’s sustainable growth. Trustees will need to assess such affordability annually; they will also have to provide evidence for their view of what is reasonably affordable and their opinion on the maximum supportable risk that a sponsor employer can bear. These are potentially significant areas for disagreement between sponsoring employers and trustees, with one seeking to discharge a fiduciary duty to protect its members and another wanting maximum freedom from the liability of funding a pension scheme, but TPR has still to provide its covenant guidance on the main areas that trustees must consider when assessing the employer covenant. In that sense, there is a significant area of this code where an important point of detail is missing. Can the Minister advise when such covenant guidance will be issued? The code emphasises a flexible and scheme-specific approach to regulation, taking into account the variety of DB schemes. It contains provisions for schemes that remain open to new members and may not be maturing, such as schemes that are now closed. Again, that is quite a controversial issue in the initial iteration and consultation on the development of this code. The considerations around investment strategy and the ability of trustees to choose how to invest now recognise the different characteristics of open schemes compared to closed schemes; the importance to open schemes of long-term planning; and a more flexible approach to assessing investment risk, which is supportable by the covenant and the scheme. Finally, the Explanatory Memorandum—I shall pick up with brevity a point that my noble friend elaborated on in more detail—states: “The approach to monitoring this legislation is that there is no requirement to carry out a statutory review of the draft Code”. However, as we all know, the previous Government were—and, more so, the current Government are—focused on the issue of wider funded pension scheme consolidation and scheme investment strategies. Although I recognise that the Minister cannot comment on the outcome of such considerations or what may flow from the first pension review, if those outcomes had an impact on the provisions of the DB code, what would be the mechanism and consultation for revising the code as a consequence?