Pension Schemes Bill [HL]

Lord Young of Cookham Excerpts

Report stage & Report stage (Hansard) & Report stage (Hansard): House of Lords
Tuesday 30th June 2020 Lords Chamber

Moved by

[Lord Young of Cookham]

53: Clause 118, page 106, leave out line 32
Member’s explanatory statement
This is a probing amendment, following the debate in Committee, to establish the Government’s proposals to use GOV.UK Verify for the purpose of authorising access to the Dashboard.

[Lord Young of Cookham (Con) [V]]

My Lords, Amendment 53 in my name presses the Government to clarify progress on identity verification. This is crucial because without a system for identity verification—proving you are who you say you are—no one can use a dashboard. The original proposal for verification was summarised on the ABI website:

“The process to confirm the identity of users is based on the gov.uk/verify system”.


Verify was a government-sponsored IT project that began in 2014 and has cost about £200 million. It should have provided the basis for accessing pensions dashboards. To put it mildly, however, it has not lived up to expectations, leaving a void in the dashboard programme.

Last year the NAO published a critical report on what in its words was

“intended to be a flagship digital programme”.

It said:

“Even in the context of GDS’s”—


the Government Digital Service’s—

“redefined objectives for the programme, it is difficult to conclude that successive decisions to continue with Verify have been sufficiently justified.”

A year earlier, the Infrastructure and Projects Authority recommended that Verify be closed as quickly as practicable. The Institute for Government’s Whitehall Monitor commented that the scheme continued to be “mired in issues”, had fallen “short of targets”, and had

“failed to build its intended user base and … is not delivering the efficiencies that the government sought.”

In March this year the Government stopped funding the scheme. Verify’s falling out of favour was heralded by my noble friend in his reply to my amendment in Committee. This is what he said:

“I understood what my noble friend said about Verify, and I assure him that the industry delivery group has this issue squarely on its radar.”


Putting on his black cap, he went on to say:

“The solution may not be Verify. … We hope to make announcements on that in due course.”—[Official Report, 2/3/20; col. GC 205.]


Responsibility for taking identification verification forward now rests with MaPS, the Money and Pensions Service. In its progress report in April on identity verification, there is no mention of Verify, which seems to have been airbrushed out.

Yesterday, I got an email from Mr McKenna of MaPS, for which I am grateful. I had asked him whether the current market engagement exercise on the dashboard included verification, and this is the reply:

“The current market engagement exercise does not include identity verification. This is a separate work strand within the programme that requires more work before we will be in a position to engage with the supplier market.”


So a prerequisite for the dashboard programme has been put to the back of the queue. Who is going to provide the identity verification service? Given the commitments that we have heard this evening that the service will be free, how on earth will it be funded? Will it be by MaPS, for example? Is my noble friend able to make the announcement that he trailed in his earlier reply to me, on the timing and funding of this crucial element in the programme?

Amendment 65, in my name, places an obligation on MaPS to provide a dashboard by replacing “may” with “must”. It is the identical twin of an amendment that I tabled in Committee, and I am grateful to my noble friend Lady Altmann and the noble Lord, Lord Sharkey, for their support. To the amateur, our one-word change seems a more economical way of achieving the desired objective than the five government amendments with thousands of words, but we bow before the expertise of professional drafters. I say straight away how grateful I am, as I am sure other noble Lords are, that the Government have listened to the strong case made on all sides in Committee, and recognised that we need the certainty of compulsion, rather than the uncertainty of discretion, when it comes to MaPS and the dashboard. That we have this concession is typical of the patient listening of Ministers and their officials in the last three months, on this and other issues, and I warmly welcome it.

But—and it is an important “but”—there is no date by which they have to do this. Without some idea of timescale, we could be left holding the menu without ever getting the dish—hence my Amendment 68, which obliges MaPS to complete this task by December 2022. I referred in Committee to the length of time it has already taken to get this project up and running. It was first promised by Government in 2002 as an online retirement planner, and we were told 12 years later by the then Financial Secretary to the Treasury that:

“A ‘RetirementSaverService’ (dashboard) will be essential to support pension freedoms.”


Five years after pension freedoms, there is still no dashboard, while eight national dashboards have been launched in Europe and we have been reassured by the ABI that there has been extensive testing of prototypes.

In response to my amendment in Committee, my noble friend Lord Howe said,

“but I can tell my noble friend that MaPS and the industry delivery group intend to set out their approach for the year ahead by Easter. By then, we should have at least the outline of a plan, with milestones I hope, so that we can be a little clearer on the answer to the question that he raised.”—[Official Report, 28/2/20; col. GC 184.]

Easter has come and gone, but no milestones. The latest from MaPS is:

“We plan to lay out a more detailed timeline by the end of the year.”


I looked at the ABI website over the weekend to see if it had updated it on the subject of the dashboard since Committee, and I found this under “FAQ”:

“If the prototype has worked, why do I have to wait until 2019 to use this myself?”


Perhaps that could be updated before Third Reading.

Since Committee, MaPS and the ABI have had to cope with the pandemic, and their top priority has to be the continued payment of pensions, the collection and investment of contributions, and the provision of advice. But the introduction of “must” instead of “may” risks being meaningless without some indication of a date by when the obligation must be discharged. I hope that my noble friend can provide some sort of road map and destination time by which we will do this.

Finally, Amendment 63, in the name of the noble Baroness, Lady Sherlock, would require the MaPS dashboard to be up and running for a year before other dashboards. My initial view was that we did not need to have more than one dashboard as the data displayed on each would be identical, so why duplicate? However, as a Conservative, I was persuaded to support competition and choice, but I have a lot of sympathy with this amendment; I believe it would be best if MaPS became the brand leader of dashboards and was well established as such in the minds of the public. It has a better chance of doing this if it is first out of the traps, rather like the BBC and commercial broadcasters. In practice, this should be the case as MaPS is in charge of the plumbing for all the dashboards.

Looking at the progress update report from MaPS in April, I see that Chris Curry of MaPS is in charge of the pension dashboards programme. His remit will be to develop the secure digital architecture to support and enable the development of pension dashboards. Therefore, MaPS is doing the specification, procurement and testing of the common systems that everyone will be using; with this inside track, it ought to be first in the field.

The Minister said in reply to the debate on this in Committee:

“It could be that the publicly funded dashboard will be launched first and be first in class, and that others will follow.”—[Official Report, 26/2/20; col. 185GC]


It would be helpful if the Minister could go a little further this evening and encourage MaPS to say publicly that it is indeed its intention to be up and running before anyone else. On this, as indeed with other amendments, I will listen very carefully to what my noble friend says in reply. I beg to move.

[Baroness Drake [V]]

My Lords, the introduction of a pension dashboard service raises major considerations of the public good and consumer interest, which is why I, my noble friend Lady Sherlock and many other noble Lords across the House have argued strongly for citizens to have the right to access their data through a public dashboard and not be restricted to commercial services.

I thank the Minister for his courteous consideration of our arguments and the decision of the Government to require the Money and Pensions Service—MaPS, a public body—to provide a pension dashboard service. Amendment 63 would ensure that the MaPS public dashboard must have been in operation for a year, and the Secretary of State must lay a report before Parliament on the operation of that service, before commercial dashboards are authorised by the FCA to enter the market. A MaPS dashboard would be part of their function to deliver guidance to the public that is free at the point of use—a safe space, unfettered by any commercial interests.

As the Government can mandate all pension providers and schemes to release personal financial data on the order of 22 or more million people, Parliament needs to be confident that the public good and consumer interest are well served. The points of the noble Lord, Lord Young of Cookham, are extremely valuable and important, and I thank him for making them. Financial technology should be harnessed for the public good and to improve financial markets, and the dashboard has that potential.

However, building a dashboard service has complexities and challenges. The architecture, the liability model, consumer redress on detriment, data standards and sharing risks, identity verification and security—that quite rightly preoccupied the noble Lord, Lord Young—delegated access and consumer behavioural responses, to name just a few, are all work in progress. As I observed in the previous debate:

“The long-term savings market is particularly vulnerable to consumer detriment”.—[Official Report, 26/2/20; col. 176GC]


There is a major governance challenge to be addressed: the consumer protection of millions in both the provision of the dashboard and the infrastructure that supports it.

The ABI, speaking for some commercial providers, has acknowledged the need for strong governance to make clear what obligations, liabilities and controls will be in place and are necessary. In requiring near-universal coverage, the dashboard service raises the bar on protecting customers from poor behaviour by regulated and unregulated providers, scammers and consumers’ own vulnerability, when all their savings can be viewed in one place.

--- Later in debate ---

[The Deputy Speaker]

I have received no requests for noble Lords to speak, so I call the noble Lord, Lord Young.

[Lord Young of Cookham [V]]

My Lords, I thank noble Lords who have taken part in this debate, not least my noble friend Lord Howe for his response to the issues raised. I repeat the welcome given by all those who spoke to the government amendments, which in effect oblige MaPS to provide a dashboard. I make it clear that I do not propose to press any of the amendments in my name to a Division.

On identity, I note the new joint unit between DCMS and the Cabinet Office to come up with a digital verification process. It sounds a little like the exercise that was started in 2014 to initiate the Verify programme, which had the same objective. I only hope that this initiative is more successful.

On funding, there was a sentence in my noble friend’s response that I did not have time to write down in full, but it sounded as if it came from the Treasury: that funding options would be considered as part of a range of solutions. I would like to look a little further at that, but I welcome the reassurance that there will be no charge to the consumer. I am grateful that he recognised the importance of getting the identity verification process right as a precondition for a successful dashboard.

On the date, I say with respect that we heard a lot from my noble friend about “day one” but nothing about “day when”. We are no further forward in having any idea as to when the pensions dashboard will be up and running. I look forward to the six-monthly progress reports and I welcome what he said about recognising the urgency of getting the system up and running.

I think that we had a new commitment from my noble friend this evening which I welcome, which was that no one would be able to provide a pensions dashboard before MaPS. I am not sure that we have had that before. I wonder whether there will be some legislative underpinning of that commitment, which I would very much welcome.

The bulk of the debate was on Amendment 63. The majority of those who spoke, led by the noble Baronesses, Lady Drake, Lady Janke and Lady Sherlock, my noble friend Lady Altmann, and the noble Lords, Lord Vaux and Lord Sharkey, all wanted, in the interest of consumer protection, MaPS to have a head start so that it could be trialled and tested. My noble friend Lady Neville-Rolfe put the contrary view that there should be a more market-based approach to the dashboards without an inside track for the public sector. I do not propose to support the amendment in a vote, but my view is that it would be best if MaPS made it absolutely clear that it plans to be up there, using all its advantages, ahead of the field to set the pace. However, I understand the arguments and I suspect that when it comes to a Division the Government may be obliged to rethink whether this is something they really want to go to the stake on, or whether it is something that they can live with. In the meantime, I beg leave to withdraw Amendment 53.

Amendment 53 withdrawn.

--- Later in debate ---

[Lord Young of Cookham [V]]

My Lords, I will add a brief footnote to the powerful case made by the noble Baroness, Lady Bowles. She referred to the Railways Pension Scheme. As Secretary of State for Transport from 1995 to 1997, I am familiar with the scheme, which has grown in the intervening years to be one of the UK’s largest funds and which I believe to be well run.

I shared with my noble friend Lady Stedman-Scott the concerns of the RPS; namely, as the noble Baroness, Lady Bowles, has said, that the draft DB funding code that will emerge as a result of this legislation would oblige the various schemes under the RPS to de-risk with lower returns. As the noble Baroness has explained, these would have to be made good by the industry, if it could afford it, or its employees, or the schemes would be closed to new members.

I was encouraged by my noble friend’s helpful reply, dated 17 June, which said:

“Those employers and schemes who are already following good practice and planning for the long term should not need to change and we would not expect such schemes to require significant additional funding.”


However, I shared the letter with the RPS and, despite this, it believes that the powers in the Bill are too loosely expressed and that more specificity would ensure that the subsequent regulations got off on the right track. If the Minister cannot accept the amendment, can he make a commitment that there will be a distinction between open and closed schemes, to be followed up in the subsequent regulations? Will he ask his officials to discuss these concerns further with interested parties in an endeavour to find an acceptable way through as the Bill completes its passage through both Houses?

[Baroness Altmann [V]]

My Lords, I support Amendment 71, to which I have added my name. I have little to add to the excellent words of the noble Baroness, Lady Bowles, and my noble friend Lord Young of Cookham.

I stress to my noble friend the Minister that this is a really important amendment. The Government’s recent White Paper called for pension scheme funding which enables the best deal for members, supports the economy and does not place extra burdens on business. If those are the objectives—and I think they are the right ones—they will be at odds with the draft DB funding code that may emerge from this legislation, which seems to want to drive DB schemes on a path to so-called de-risking, aiming for a particular date of maturity. This concept is simply inappropriate for an open scheme.

The regulatory approach for schemes such as USS or the Railways Pension Scheme would see their ability to invest for the long term, which must be in the members’ best interest, become much more difficult. There does not seem to be sufficient recognition of the difference in liquidity profile and investment horizon of an open, relatively immature scheme compared to a closed scheme. Indeed, this would pose an existential threat to the survival of all remaining 1,000 or so open schemes. In the face of quantitative easing, increasing exposure to gilts and fixed income assets makes little sense while central bank policy is designed to force bond yields lower. Forcing schemes to compete with central banks to buy ever more expensive bonds is the most expensive way to fund these pension commitments.

The Bank of England’s pension scheme is an ideal example. It follows a lowest-risk approach, investing solely in gilts and other such supposedly safe assets. It does not match its liabilities, but it is open and entails a contribution rate of between 40% and 50% of pensionable salary. Should such pension contributions be required without any upside potential for a diversified investment strategy that can take advantage of the wide range of investment options available from infrastructure assets, building housing for rental and other areas where pension schemes with a long-term horizon are ideally placed to take advantage—for example, our own infrastructure, in which other countries’ pension schemes have significantly invested—schemes such as RPMI would require such significant contribution increases that members could not afford it and would opt out, and employers could probably not afford it either.

Therefore, I urge my noble friend to look carefully at this really important issue and to recognise explicitly that there are different needs for open DB schemes relative to those that are otherwise closed.