My Lords, I am pleased to introduce this statutory instrument, which, subject to approval, will make amendments to the Pensions Dashboards Regulations 2022. The instrument removes the staging profile from the 2022 regulations and introduces a single connection deadline of 31 October 2026 for relevant occupational pension schemes to connect to pensions dashboards.
The successful introduction of automatic enrolment more than a decade ago, combined with a trend towards people working multiple jobs in their lifetime, has seen a substantial increase in smaller pension pots. Without intervention, the number of lost and forgotten pots will remain exactly that—lost and forgotten—and financial planning for retirement will become still more complex. Pensions dashboards will help hard-working savers to locate pension pots that they have accumulated over time, reconnecting them with lost and forgotten pension pots and supporting better planning for retirement. People will be able to view their various pensions, including their state pension, securely and all in one place online.
There can be no doubt that pensions dashboards have the potential to become a game-changer that will revolutionise the pensions landscape. The UK is not alone in realising the enormous potential that pensions dashboards bring. Countries such as Denmark, Israel and Australia have all established pensions dashboards as a feature of their financial landscape. However, the UK’s pensions industry is arguably unique by virtue of its scale and complexity. We should not underestimate the ambition and challenge of securely connecting thousands of schemes and of presenting data in a coherent manner, from state and private pensions, for the benefit of savers. We anticipate that, once all schemes in scope of the regulations are connected, the pension records of over 71 million memberships from relevant occupational pension schemes and providers of FCA-regulated entities will be accessible to people at the touch of a button, at a time of their choosing.
The reason for bringing forward these amendment regulations is that, at the end of last year, the Pensions Dashboards Programme, which is responsible for delivering the digital architecture that underpins pensions dashboards, informed my department that more time was required to complete the build of the digital architecture. The PDP faced several key issues: the technical solution has not been sufficiently tested and there is still work to do to finalise the necessary supporting documentation and to get the necessary systems in place to support the pensions industry with the connection process. It was concluded that more time was needed to successfully deliver dashboards and that a reset of the programme was required.
The Minister for Pensions subsequently issued a Written Statement in March 2023, announcing the delay and setting out that the Pensions Dashboards Programme would be reset to get it back on to a path for successful delivery. The decision to pause, review and reset the programme will provide it with the time to ensure complete delivery of the ecosystem and supporting documentation before industry begins to connect. So far, the reset has assessed the digital architecture and I am pleased to report that no fundamental issues have been identified. This has provided reassurance to the Government to move forward with amending the regulations.
I am most grateful to my noble friend for the clear exposition of this statutory instrument and for the very helpful meetings that he and his officials have held with noble Lords over the past few months. I am also grateful to him for the letter that he wrote to me following the last meeting.
Looking around, I see some aficionados from our earlier debates on the pensions dashboard. I was looking at a debate from 28 January 2020, when I said:
“Over the weekend, I logged on to the Pensions Dashboard Prototype Project, which I found informative, but right at the end it said: ‘The industry and government hope to have Pensions Dashboard services ready by 2019’”.
At that time, we were debating a consultation document and the response to it. Again, I quote:
“Reading the response to the consultation document, we are told: ‘Once the supporting infrastructure and consumer protections are in place, and data standards and security are assured, most pension schemes should be ready to provide consumer’s information to them within three to four years’”.—[Official Report, 28/1/20; col. 1373.]
That was in January 2020. My noble friend knows that this project has been dogged by uncertainty and delay.
I have a specific point to raise about the identification service. Consumers will obviously have to identify themselves before they can access the dashboard. The Government’s initial proposal was to use Verify, a system sponsored by the Government with ambitious targets to have 46 government services accessible by March 2018. Sadly, that project was not a success. The NAO said that
“it is difficult to conclude that successive decisions to continue with Verify have been sufficiently justified”,
My Lords, it is obviously deeply regrettable that the pensions dashboard has been delayed—again, I should probably say. If it is not ready, a delay to the connection is obviously necessary, so there is not an awful lot to be said about the regulations themselves. As we have just heard, the Explanatory Memorandum is less than fulsome on the reasons or the implications, as the Secondary Legislation Scrutiny Committee pointed out in its rather critical report, so I want to ask a few questions. I have not been able to attend some of the briefing sessions that the Minister has organised, so I apologise if I am covering what was said at some of those, but it might be worth having it on the record anyway.
What is the reason for the delay? The Explanatory Memorandum and the Minister talked about insufficient testing,
“more work … to set up adequate support for industry … and … to finalise … supporting guidance and standards”.
However, those are not reasons; they are not what has caused the delay. Delays of this nature are typically caused by inadequate scoping at the outset—we got it wrong at the beginning—by changes to the scope along the way, or by some combination of the two. Which is it? Who is responsible? What action has been taken to make those responsible for the delays accountable? If the team needs to be strengthened, has that happened?
The other possibility is simply that the dashboard was overcomplicated from the outset, which I think was what the Secondary Legislation Scrutiny Committee may have been alluding to. Are we sure that we are not gold-plating it? Are we reinventing the wheel here? For example, have we taken advantage of the experience of open banking? We could have piggybacked on that.
Is a third-party supplier involved? If so, who and what responsibility does it have for the delay? Are there penalty clauses in the contract? If a third-party supplier is not involved, is it sensible for us to try to do a project of this size entirely in-house?
I thank the Minister for so clearly setting out the purpose of the regulations. I enjoyed the reference of the noble Lord, Lord Young, to his previous contribution in the debate on this issue, which was well made. My position is that it is not disappointing that the Government’s enthusiasm for such an early launch has been tempered; I always considered that it would be a very complex project and I am delighted that there is now a much greater focus on the complexities and ensuring what is delivered. I never really wanted it delivered two years ago because I did not think that it would be well delivered then. It needs to be well delivered, because of the scale that it covers.
These regulations replace the pension schemes staging profile, staging deadlines and connection window with a single common deadline for connection of 31 October 2026. I want to reflect on the guidance to schemes on a new connection staging timetable.
The DWP’s description of the purpose of that guidance has varied according to which document is read—there is not an absolute consistency. The documentation ranges between encouraging schemes to meet the new timetable to threats of a breach of the regulations if they do not, and “having regard to” the guidance is a concept that is a little unclear. Can the Minister clarify what exactly is the status of that guidance and when a breach—and a breach of what in regulation terms—would be triggered?
I will move on to an issue that we probably have not debated a great deal in previous discussions of the dashboard. The Explanatory Memorandum refers to the monitoring and review of this legislation, saying that the approach to be adopted is
“to put in place a multi-strand evaluation strategy, the details of which are being explored”.
This strategy will
“ensure the critical success factors can be successfully tested with learning helping to further develop dashboards over time”.
My Lords, I, too, thank my noble friend for his clear exposition of the regulations. I am very supportive of them and I think they have general support around the Committee. Indeed, they are pretty essential, as my noble friend described. If we do not pass them, there is a danger that schemes currently required to load data to the dashboard by the end of August will be in breach, and there will be nothing they can do.
Replacing the statutory staging timetable with a single end date of October 2026 is understandable. It is also welcome that the reference date for the dashboard requirements of pension schemes is being moved to 2023-24 so that it can include some of the newer pension schemes, which will then have to go on to the dashboard. However, I would be grateful if my noble friend could help me with a few questions. It is fine if he would like to write to me; I do not expect him necessarily to have all the answers, although he may not be surprised by the questions.
My first question relates to the Government’s intention to publish a new timetable in the form of guidance. When will it be published? Also, my noble friend said that it will not be mandatory, although trustees must, as the noble Baroness, Lady Drake, said, have regard to the guidance and will get at least six months’ notice. What is the penalty for non-compliance with the guidance, if it is not mandatory? If it is struggling, a scheme may simply say, “We’re not going to do it because the amount of money we need to spend to get on the dashboard is not worth our while”. The customers and members of those organisations would then not benefit from the dashboard.
My second question relates to the vital issue of data accuracy, which is essential for dashboards. I hear what my noble friend said about accuracy requirements in the GDPR. Following our briefing meetings, I was grateful to him and his officials for a follow-up letter that clearly explained that the Pensions Regulator has set out in guidance expectations on data quality, record-keeping, measuring data once a year and trustees ensuring that processes and controls are in place so that data standards are of good quality. Master trusts are supposed to have processes for rectifying errors they have identified and then reconciling them. This is all in place and is most welcome, but I have to ask my noble friend: where does responsibility lie for checking the data, ensuring its accuracy and then correcting and reporting back that those data have been assessed and corrected? If that does not happen, on whom would penalties fall? To whom can members and the dashboard turn to ask, “Are you sure these data are correct?” Who is ultimately responsible for signing off on that or carrying responsibility for penalties if that does not happen?
4:45 pm
My next questions are about data security, which my noble friend Lord Young has already touched on. Can my noble friend the Minister explain what is happening around enhancing data security? We know that there have been problems, and there have been warnings about the problems that could arise from scammers and others being able to hack into the data on the dashboards.
I have two final questions. With this reset and reconsideration, will consideration be given to having uniform data standards so that all pension companies have to use a standardised system, as has happened in Australia? That could make an enormous difference to the ability to have all the data recorded in one place and updated regularly.
Will my noble friend comment, or perhaps write to us, on the status of the corrections made as part of the big exercise within the state pension system to identify and correct state pension entitlements, particularly of women? I know it is a significant exercise but any update would be welcome, as that needs to feed into the dashboard too.
My Lords, I thank the Minister for bringing this statutory instrument to the Grand Committee. I have read the November debate and I look forward to a further detailed disposition from the noble Baroness, Lady Sherlock, with her usual forensic care. I will therefore not go into great detail; I am glad she will be winding up.
Can the Minister give me some reassurance? Compared to many others, I am coming new to this brief. Having looked through the regulations I see that there are no longer any binding interim dates, just one big deadline in 2026. Does the Minister not see how hard it will be to get busy pension schemes—commercial pension schemes—to prioritise this over their other day-to-day work? Other noble Lords have made the point about data being ready for dashboards. How much time will these pension schemes give to this, given that there are no interim dates and just one big date in 2026?
It seems to me that the issue is deadlines, and there is a need for the Government and pension schemes to nudge people to make sure that all details are up to date on the various pots so that they can pull that through to the dashboard when it is launched.
In a debate on 8 June, the Government elaborated on the need for dashboards to change the way people plan for retirement, and the Minister said that more time was needed to deliver this complex build. Paragraph 7.4 of the Explanatory Memorandum includes explanations. I have never seen so many explanations for why something has not happened:
“The technical solution has not been sufficiently tested, more work is needed to set up adequate support for industry with their connection journey and there is still work to do to finalise the necessary supporting guidance and standards”,
and so on. It is the biggest list of excuses for delay that I have come across for some time.
My Lords, I thank the Minister for his introduction to these regulations and all noble Lords who have spoken. It is very nice to welcome the noble Lord, Lord Palmer, to the pensions dashboard crew; we look forward to having discussions with him on the later iterations of this project, which one sincerely hopes will not come to pass.
We have been very supportive of the pensions dashboard. Therefore, we agree with the noble Lord, Lord Vaux, that it is deeply regrettable that we are in this place and that the Pensions Dashboard Programme needed to be reset. I accept that my noble friend Lady Drake is right: if the digital architecture was not going to be ready to enable pension schemes to connect before the first deadline, which is the end of next month, it is clearly better to pause and get it right. After all, the dashboard service will enable access to trillions of pounds of assets and accrued benefits belonging to working people. It has to be secure as well as fit for purpose.
My noble friend Lady Drake is often a Cassandra on these matters; she sees these problems coming. My problem is not that the Government should pause and reset, if that is necessary; it is that they need to stop pretending that everything is fine, until the moment when it is suddenly not fine. That is a bit of a habit in government: “Is everything fine?” “Yes, yes, yes. Oh, no, it has all fallen apart, but will be fine again with a new deadline”. We somehow need to find a way of discussing things in politics that allows a grown-up approach to understanding when projects will be difficult. There is an overconfidence on the part of the Government such that, when everyone raises problems, Ministers are sent out with a brief that says, “No, it will all be fine; there is nothing to see here”, until it falls over.
I do not expect the Minister to solve that problem overnight, but I commend this to the Government as an opportunity to think again about how we handle big projects—and, in particular, how Parliament can have some accountability for them. An awful lot of money is at stake here—private, commercial and public. There ought to be some decent accountability over it.
5:00 pm
We are told that guidance-based staging dates will be determined by the end of the year, I think it was said. This leaves a lot of uncertainty. I think I caught it correctly when the Minister said that this instrument curtails the period of uncertainty for schemes. However, I heard an interesting comment. Jon Pocock, who is pension dashboard delivery manager at Broadstone consultants, said:
“Until there is clarity on how rigid the guidance dates are and the flexibility schemes have to meet them or not then we anticipate, rightly or wrongly, that many schemes will simply defer acting”.
Does the Minister agree? Can he tell us when the guidance will be published, so schemes know how long they have?
20 of 42 shown
The staging profile in Schedule 2 to the 2022 regulations set out the order in which different types of schemes, categorised by size and type, would connect to pensions dashboards. However, the 2022 regulations did not provide the flexibility necessary to deliver a programme of this magnitude—a digital undertaking that will enable users to search over 3,000 schemes to find their pensions.
This instrument curtails the period of uncertainty for the pensions industry. The staging profile in the 2022 regulations required the first schemes to connect at the end of August 2023. By laying these amendment regulations, we are seeking to avoid any perception that schemes would be in breach through no fault of their own. As mentioned, all schemes in scope will now be required to connect to dashboards by 31 October 2026 at the latest. The regulations will provide more flexibility to deliver pensions dashboards while retaining the broad framework of a phased approach to help to manage the flow of connections and maximise coverage as early as possible.
The Government will work with partners and the pensions industry on a connection timetable to be published in guidance. We expect that the connection timetable in guidance will prioritise large schemes with the greatest number of members. This will maximise the potential for savers to realise the benefits of dashboards as early as possible. The dashboards available point—the point at which dashboards will be available for widespread public use—could therefore happen before the October 2026 connection deadline in the regulations. Although the connection timetable set out in guidance will not be mandatory, there is a requirement for scheme trustees or managers to have regard to this guidance. Not doing so would be a breach of the regulations. The Financial Conduct Authority will ask its board to make corresponding deadline changes in the dashboard rules for FCA-regulated pension providers shortly after Parliament approves these amending regulations.
I will now explain what has not changed. Although the instrument amends the requirements on trustees or managers by removing Schedule 2, there are no other material changes to the regulations. All other requirements have been retained, including the requirements to be satisfied for qualifying pensions dashboard services, connection duties and requirements on “find” and “view”. Crucially, the requirement for the Secretary of State to provide six months’ notice ahead of the dashboards available point remains unchanged. The Government will continue to work with the industry on the matters that must be considered before dashboards are launched to the public.
The consumer is at the heart of all our endeavours. These relevant matters are important to ensure that pensions dashboards are launched to the public safely and securely, having been rigorously tested. Protecting the best interests of savers is the core principle behind dashboards and the Government remain firmly committed to ensuring that people’s data is accurate, simple to understand and, above all, secure. Dashboards will ensure that people always remain in control over who has access to their data, as existing legislation, including data protection duties, underpins the requirements that must be adhered to by pension providers, schemes and qualifying pensions dashboard services.
Accurate and high-quality data is essential to delivery and the success of pensions dashboards rests on the pensions industry’s ability to successfully match consumers to their information. The Government and the regulators have repeatedly advised the industry to get its data ready for dashboards. It should use the extra time to ensure that it can meet its dashboard obligations. Schemes and providers are already subject to existing statutory and other protections on data, including the accuracy principle under UK GDPR, which places a requirement on schemes to take all reasonable steps to erase or rectify inaccurate data without delay. It is crucial that dashboards give power to savers and not to scammers. Robust controls and standards will be built into the digital architecture to prevent potential scammers or fraudsters from gaining access to people’s information.
These amendment regulations will facilitate a collaborative approach to connection that delivers on our commitment to introduce pensions dashboards. Pensions dashboards have the potential to transform retirement planning for ever and these regulations are another step in the right direction. I therefore commend them to the Committee. I beg to move.
and the Government withdrew support from Verify in 2020. The pensions dashboard has had to develop its own service in the meantime.
In my noble friend’s very helpful letter, he referred to the new government service, GOV.UK One Login. He said:
“The core of the system has been launched: its sign-in element, a web-based identity verification journey, and a fast-track identity checking app”
are up and running. I have actually connected to and logged into One Login, and am now registered.
In his letter to me, my noble friend went on to say:
“As you may recall, the PDP”—
pensions dashboard programme—
“has procured an interim identity service provider, whose contract runs until January 2024”.
At what point will the pensions dashboard transfer from this interim service? Will it transfer to the government-run One Login, which seems the obvious thing to do, assuming that it is as robust? By the time the system is launched in 2026 or earlier, will the interim service have been put to one side and will we all have moved over to One Login; or will the interim service still be the one that we have to use, for the next few years? I hope to hear that it will have transferred to One Login, so that we do not have to register twice—first with the interim one and then with One Login. That is my main point.
My final point is on the Secondary Legislation Scrutiny’s Committee report on this statutory instrument, published on 22 June, which I am sure my noble friend has seen. The committee raised two points in its conclusion, to which I am sure my noble friend will reply. In paragraph 27, it quoted its 16th report:
“We encourage the Government to take this opportunity to address the complexity and costs of the dashboard … by simplifying and standardising the system wherever possible”.
The committee confirmed that that remains its position in its latest report on this instrument. Finally, it said:
“We are disappointed to, once again, find our Report supplying basic information to the House that DWP should have published in the EM”—
the Explanatory Memorandum. I am sure my noble friend will respond to those points, in addition to my main point about the verification service.
The EM is very quiet on the cost implications. What was the forecast development cost? I am talking about not the overall costs of the dashboard over 10 years but the development cost. What is it now? How much has it cost to date? How much is still to be spent? Who will cover any increase—industry, government, taxpayer? How will that work?
When large software projects of this nature go wrong, they tend to keep going wrong. I come from a software world, so I have experience here. What comfort can the Minister provide that this really will be the final delay and that we are now properly on top of the project?
At the time of the Act that enabled the dashboard, we had a lot of debate about the creation of other, privately created dashboards, and there was a lot of agreement around the Room at the time that the Money and Pensions Service dashboard should be the first to be run. I agreed with that but, given the delays, perhaps we want to think about it again. What other dashboards is the Minister aware of being developed? Are any at a sufficient stage of development that it might be quicker or cheaper for the Money and Pensions Service to consider partnering with them?
Finally, can the Minister provide any forecast of when the dashboard will become available to the public?
The plans include research into dashboard usage, outcomes from that usage and information provided by providers. However, I cannot see any reference to key pensions public policy outcomes in those critical success factors. I did not see them when the previous regulations came with the Explanatory Memorandum and I cannot see them now.
To take it at its most basic, if, for example, as a result of dashboard usage, greater numbers of people took out more of their pension savings in their 50s or early 60s, is that a success because they have engaged, or undesirable because more people will have a lower income when they get to state retirement age? We have to be very clear what are the public policy aspirations we are seeking from that greater usage. Clearly, it is not set out, as far as I can see, in the critical success factors and the multistranded evaluation strategy—although I recognise that that is work in progress. Will any of those critical success factors identified in the Explanatory Memorandum be benchmarked against desired public policy outcomes over the long term?
Staying with that concept, what long term do we want as the outcome—not only from dashboards but a whole range of other things, although dashboards are before us today? Yesterday we saw eight papers on pensions, including analysis, consultations and consultation responses, all published in one go. I cannot let that moment pass without asking the simple question of the Minister: was any consideration given to how those eight papers and sets of proposals would impact on the multistrand evaluation strategy for the dashboard? I appreciate that the Minister may not be able to answer that today but it is an important question that needs answering.
For me, the decision by the department and the FCA to proceed with a gross investment performance metric in the proposed VFM framework, as announced yesterday, rather than net of all costs and charges, together with the continued dithering by the FCA over the transparency of costs and charges value reporting in decumulation products, is a backward step which does not resonate with the pension savers’ interest and informed decision-making. That was a deeply disappointing element of that VFM framework to read. We know from the FCA’s own findings that a wide range of charges are applied in the decumulation market, which should be rigorously assessed in a joint FCA/DWP/VFM framework. That has just been sidestepped.
Yesterday, the Chancellor referred positively to the Australian supers, but I point out that they have a tough regulatory requirement to report investment returns net of fees. If the Government are going to promote private market investment, where charges are higher, transparency of returns net of fees is essential if the saver is not to end up paying back the excess returns to the industry. The link to the evaluation strategy and the dashboard is: what information will be provided, what influences on behaviour are we expecting and how will that produce better outcomes? I must admit that, when I read that VFM framework, I thought it disappointing and rather contradicted the idea that members using the dashboard will make more informed decisions. I did not want the moment to pass without making that point.
I have another question, in the light of the comments from the noble Baroness, Lady Drake, about the number of releases we have just had from the DWP. I admire the work that has been done by the department—it has clearly been extremely busy—and a lot of it is really useful. However, how will the dashboard dovetail with the reforms proposed for small pots? The Government rightly want to help people—as is part of the intention of the dashboard—to merge pots and not leave small amounts of money in legacy schemes. What are the plans for integrating the dashboard rollout with the small pots reforms?
Other noble Lords have mentioned guidance in passing. Does the Minister believe that guidance will be sufficient to concentrate minds on the issue? I am not sure that guidance will be sufficient in many cases.
There are some small points, but I am not sure how they are addressed. I may have missed that somewhere, so I hope the Minister can provide me with an answer. For instance, how are widows’ and widowers’ rights to the pensions of their husband, wife or partner being dealt with? I had a similar case: I have a modest council pension pot and I asked what happens when I die; does my wife receive a contribution? That was six months ago and I still have not had a reply, and it is being dealt with by one of the very large pension funds. I would like some reassurance that these dashboards are not going to make the situation even worse.
In theory, pensions mainly apply to older people, although people seem to take them much earlier nowadays. It worries me that the whole idea of the dashboard is based on a knowledge and working use of IT. It may surprise noble Lords to learn that a lot of people do not use IT; many people just use their mobile phones to make calls. The whole principle of the dashboard and the way in which people access information is based on being able to operate an IT system. I have doubts because, even if the people concerned are not old now, as they get older and less able, when they will really want to know, they will be fiddling around not knowing how to get into the dashboard. Will we end up with big companies such as Aviva taking over pension schemes? I have no problems with Aviva. It seems to have taken over an awful lot, although it does quite well, but I am worried that many of the smaller pension funds will opt out.
Page 2 of the valuable impact assessment that was produced gives three options: do nothing, an alternative to legislation, and—the preferred option—the Government legislating. After reading all this, I wondered whether the first option, to do nothing, might have been safer, but we have to move forward.
We need to be careful, but we must say when this will happen, and the guidance has to be accepted by the pension funds so that they know when to do something, rather than waiting until October 2026 and saying, “Gosh, we have to do this by tomorrow”. My first point was that we need some interim dates to focus minds on this issue otherwise, as we were here a year ago and were here before then, we will be here again with another list of excuses, as detailed on this document.
Clearly, people such as my noble friend Lady Drake—indeed, many on these Benches—cautioned the Government that they were underestimating the complexity of delivering the dashboard and being overoptimistic about the speed, but we want a dashboard to work. I am with the noble Lords who are raising challenges about the reasons. We have had some helpful briefings, and some slightly less helpful official ministerial Statements, but the truth is that it is hard to know what exactly has gone wrong and why it was not picked up earlier.
The Minister told us the reason, saying
“the technical solution has not been sufficiently tested and there is still work to do to finalise the necessary supporting documentation and to get the necessary systems in place to support industry with the connection process”.
A cynic would say that, basically, that means that it was all fine apart from the technology, the paperwork and the systems. That is not an explanation of what went wrong. It is a little like when my washing machine breaks and a helpful friend will say, “What’s wrong with it?” and I reply, “It’s not working. It’s not washing clothes—I don’t know”. We need more than that. I know that the Minister is keen to have his officials talk to us, but there needs to be some process of public openness and accountability when things go wrong, so that there is the ability to hold to account and understand. However, here we are, with this reset.
As we have heard, the original timetable was hardwired into secondary legislation, hence the need for the instrument. As the Minister explained, it amends the 2022 regulations to remove the staging profile, staging deadlines and connection window and insert instead a common requirement for all schemes to connect to dashboards by 31 October 2026. The new approach is described like this in paragraph 11.1 of the Explanatory Memorandum:
“Through this instrument, the Department for Work and Pensions is retaining the policy of compulsory connection by a set date and intends to encourage a staged approach set out in guidance, rather than mandated in Regulations”.
Therefore, the answer to the noble Lord, Lord Palmer, is that there will be interim dates in the guidance, but they will be suggested interim dates. It is not yet quite clear what that will mean in practice. Trustees and managers will need to have regard to such guidance but as I understand it—the Minister can clarify it—that would not necessarily mean that they are obliged to comply with the suggested dates, or presumably they would be not suggested dates but mandated ones.
That raises some key questions. With a single compulsory connection deadline, is there not an obvious risk of a backlog of schemes still waiting to connect as we get close to 31 October 2026? What action will the DWP take if there is evidence of back-ending by schemes or of backlogs building up? That is not just our concern. Dr Yvonne Braun, a director of the Association of British Insurers, said:
“Our members have indicated they’re willing and able to continue to comply with a voluntary timetable, although it would have been our preference that these remained a regulatory requirement to prevent a last-minute rush of firms connecting to the system. We ask that government keeps this under review and considers making the staggered dates a regulatory requirement again if it should become clear that the wider industry is not taking the same approach”.
What is the Government’s response to that?
Although the timetable in the guidance will not be mandatory, we know that scheme trustees or managers must have regard to it, as not doing so would be a breach of the 2022 regulations. They will also be expected to demonstrate how they have had regard to it. However, as my noble friend Lady Drake said, the language of the Explanatory Memorandum is much more about encouragement. Paragraph 7.6 refers to MaPS and TPR communicating with
“trustees and managers of schemes in scope to encourage connection ahead of the single connection deadline, in line with the connection dates set out in guidance”.
It is not clear to me where the line lies between compulsory and voluntary when it comes to guidance. Can the Minister clarify that?
Can the Minister explain what “have regard to” means in practice? Is there an established meaning of this in law? It is a phrase that comes up, so can he help us on that? A crucial question is what would count as not having regard to the guidance. For example, suppose a scheme manager reads the guidance carefully and develops a plan to connect just in time for October 2026, and she is confident her scheme will be ready by then, does that count as having sufficient regard? Suppose lots of others do the same thing, and they all get to that point but cannot connect because there are too many of them and the system cannot manage it, are they in breach of the law? Have they failed then to have due regard to the guidance? What is their position?