Public Accounts Committee

19 October 2026

Public Accounts Committee House of Commons

Follow its sittings
00:05 - 01:44
Speaker 4
Order order.  Welcome to this session of the Public Accounts Committee on Monday the 19th of October 2026.  Digital identity and underpins how people prove who they are, demonstrate their eligibility and access to public and private services securely.  Since this committee announced our inquiry onto digital ID, the government has dropped its plans international ID digital ID scheme.  But the underlying issue remains as more services move online questions about how public can prove who they are conveniently and securely remain highly relevant and they are certainly not going to go away. 

The National Audit Office's report found that the UK already has many of the components associated with digital ID, but the responsibility is fragmented across government, more than a dozen organisations and there are no coherent strategy for how they should work together.  So today the committee will examine how DCMS is organising its new responsibilities in this area, whether the government has a clear long-term approach and accountability arrangements and how it will address the practical challenges around legacy systems, fragmented data, privacy, security and public trust.  So we are very pleased to have with us the permanent secretary and her team.  So what I'm going to do is my usual practice and ask you please permanent secretary if you will introduce yourself and I'm a little bit quirk today, I want everybody to please tell us what professional digital training they have had in the past please. 
01:44 - 02:03
Speaker 8
Hello, afternoon, I'm Susanna Storey, I'm the permanent secretary at the Department for Digital, Culture, Media and Sport.  I haven't got any professional digital training but I have been involved from 2019 to 2023 as director general for digital and media in a lot of digital and tech policy.  Thank you. 
02:03 - 02:10
Speaker 4
Thank you for that introduction you are very welcome.  I'm going to go to your left and ask Christine to do the same please. 
02:10 - 02:42
Speaker 16
Hello, I'm Christine Bellamy, I'm the interim director general in Government Digital Services, specifically on the product side so looking after the digital products that we run for government which is fundamentally around the gov.uk proposition at its core.  I'm a four year civil servant, but before that I was at the BBC for 10 years where I ran digital and tech for news sport and for the education portfolio.  Before that I was at Johnson Media where my job was to transform one of the people to transform that organisation to a digital organisation. 
02:42 - 02:45
Speaker 2
Thank you.  Rod Latham please. 
02:45 - 03:01
Speaker 14
Hi good afternoon, I'm Rod Latham, I'm the director for cyber security and digital identity in DCMS.  Like Susanna I don't have any professional digital qualification but I've worked in technology policy in the civil service in a number of roles including this one for several years and before that in the Cabinet Office. 
03:01 - 03:07
Speaker 7
Moving to my right, Philippa Rouse please.  Is it it is Rouse, have I pronounced it correctly?  Thank you. 
03:07 - 03:34
Speaker 15
It is Rouse.  Thank you.  Good afternoon.  So I'm Philippa Rouse, I am currently the director for gov.uk connect within Government Digital Service.  From February till July I was the programme director for the digital identity taskforce. 

I don't have digital qualifications, I'm an analyst by background and I spent seven or eight years leading tech-enabled transformation for the Home Office in the migration and border space. 

03:34 - 03:35

Speaker 3

Thank you.

03:35 - 03:37

Speaker 5

Finally, by no means least, Natalie Jones, please.

03:37 - 03:51

Natalie Jones

Hi, I'm Natalie Jones. I'm the director for OneLogin and verified credentials. I'm also the SRO of GOV.UK OneLogin. I have a variety of scaled agile digital professional qualifications as well as being an MPLA graduate.

03:51 - 04:33

Geoffrey Robert Clifton-Brown

Thank you very much. So, I'm going to start, please. And I think I'm going to start with you, Permanent Secretary, but I'm very happy if you pass it over to one of your team because it's pretty sort of standard technical stuff. We've now had two machinery of government changes in fairly short order, moving digital policy of one form or another from Cabinet Office to DSIT, which has been now abolished. Part of it seems to have been now transferred to DCMS, other bits going to other departments.

Could you sort of fairly simply explain what the current state of play with digital policy in its totality, including AI, is, please?

04:33 - 05:14

Susannah Storey

Absolutely. Yes, so this Prime Minister at the end of July announced a machinery of government change which set up a task force for AI in the Office for Prime Minister and Cabinet. And then the rest of DSIT has been split between DCMS and the business department. So DCMS is responsible for policy around telecoms, cyber, tech, and digital, and also for the Government Digital Service, as well as a number of other things that came in that MOG. And the business department is responsible for science and innovation alongside its previous responsibilities.

So that's a quick version, but happy to double-click on anything that would be helpful.

05:14 - 05:18

Speaker 6

Just precisely where AI sits, please.

05:18 - 05:29

Susannah Storey

So the strategy for AI sits with the task force and the Minister for AI who attends Cabinet, Feryal Clark, is in the task force in the Office for Prime Minister and Cabinet.

05:29 - 05:46

Geoffrey Robert Clifton-Brown

So on the face of it, that sounds or seems a little bit odd that you've got responsibility for much of the digital policy, but the AI sits out of your responsibility. Given that that is the case, how are the two of you going to liaise?

05:46 - 06:33

Susannah Storey

Yeah, I mean, the way I see it is that it's a mainstreaming of digital responsibilities. So the business department is going to be doing a lot more on innovation, science, thinking about things like data centers and some of the business sides of this whole agenda. In DCMS, we've got the kind of tech stack, so we're thinking about cyber and there are a lot of AI questions there, of course, and telecoms and mainstream digital policy. And in practice, we, the task force, and the business department are going to be working incredibly closely together. And luckily, because all of these teams knew each other well when they were in DSIT, we've got all of those relationships and so I think so far there are positive signs of really good joint working.

06:33 - 06:44

Speaker 12

Obviously on the ministerial side, Feryal in the OPMC, my Secretary of State, and Jonathan Reynolds are also very close on this whole agenda alongside some of our junior ministers who are involved as well.

06:44 - 07:41

Geoffrey Robert Clifton-Brown

So the next question is I'm interested in how your department is going to influence the rest of government because I've likened AI as a tsunami and it's going to hit the government and I'm not sure the government is yet prepared for that. So I have a Treasury minute in front of me responding to our recommendations on the Bank of England. This was from the Treasury, I think. No, DSIT. And it says this, the response, and I think it's out of date, but I'd like you to respond to this because it's a theme that this committee has had for some while.

The responsibilities of a Government Chief Digital Officer are delivered by the Permanent Secretary for DSIT, supported by deputy heads of function from the main digital departments plus Government Digital Service's Directors General with responsibility for supporting digital transformation across government and digital products GDS builds and runs. So is that out of date? And if so, how is it now being modified?

07:41 - 08:39

Susannah Storey

So when the machinery of government change happened, my predecessor Emran Mian was clear that the arrangements that DSIT had were that he was head of profession for digital, and then he has five deputy heads of profession from the main digital departments plus GDS. So Chris to my right and Emily, who are the two DGs in GDS, and then we also have Daljit at HMRC, Helen at DWP, and Megan at MOJ. And so basically we five, the five DGs and me form the executive committee. So I stepped into his shoes because I wanted to make sure we had continuity of approach. And then obviously what we're doing while getting up to speed, and I think I said this in the response to you, we will just look at it, see how it works, and if we make any further changes, we'll let you know.

But I do think across the broad waterfront of digital, and I know that this committee and also the Science and Tech Committee have put forward...

08:39 - 25:58

Geoffrey Robert Clifton-Brown

Right, order, order. I think what I'm going to do, we're going to come back and I'll ask that question again and ask with the politeness of being able to answer it. Thank you very much. So I'm going to suspend now.

Order, order. Welcome back everybody. And we were just, I was just asking a question on the new government's policy on the Chief Digital Officer and how that will work. And you, Permanent Secretary, were going to answer that question for me please, if you could just sort of start afresh from that.

25:58 - 27:38

Susannah Storey

Yeah. So, since the machinery of government change in the summer, we've been working at pace to integrate the new department and we are taking our responsibilities for digital obviously very seriously. The main approach to policy comes through the departmental governance, my executive committee and up to the board. And then for the Government Digital Service, that comes through that DSIT route as well. For the cross-Whitehall digital work, which I think is what you were asking about, I stepped into the shoes of my predecessor Emran Mian as head of profession.

And we run that approach with deputy heads of profession, which is five Director Generals from across Whitehall. Two of them are in my department in DSIT, Chris and her colleague Emily. And then three of them are from other leading digital transformation departments. So Daljit at HMRC, Helen at DWP, and Megan at MoJ. And through that structure, we meet regularly for a digital ExCo.

And some of the other things we do, I'm having regular digital business reviews with the big departments. So since I've been in this role responsible for digital, I've already seen the Home Office and HMRC. So we use that as a way to get that cross-cutting view from across the piece. And just one other thing, if you don't mind I might mention Chair, that also I chair the Technology Risk Group. And that is a place where we look at some of the many risks on the digital from a digital perspective and I report back to the heads of department on that.

So that's probably the other piece of governance that it's worth mentioning.

27:38 - 28:09

Geoffrey Robert Clifton-Brown

So what has happened to the recommendation that this committee has often made, and I think been accepted by government, that every single department and next-steps agency should have a very senior, uh, Chief Digital Information Officer, um, preferably at director level, and at least one but preferably more members of their non-exec board, uh, who has real digital experience, so we can start to get your digital, uh, policy really promulgated across government?

28:09 - 28:42

Susannah Storey

Yeah, I think that's a really important point that you've made, and from what I can see, my colleagues are making progress. I mean, it is certainly the case, I think, right across the public sector, but also in the private sector, people are very seized of these many digital issues. Um, there's quite regular conversations with my peers about cyber risk, um, and across the departments, people are implementing that recommendation by the end of December. And I think there's been good progress, um, and, uh, yeah, happy to come back with any further detail on that if helpful.

28:42 - 29:14

Geoffrey Robert Clifton-Brown

So it's you, your department, that is responsible for coherent policy across government. And who is responsible for, you mentioned cyber risks, that we, we've been told many times on this committee that at least 30% of digital hardware is legacy systems, which is much more prone to cyber attacks and doesn't necessarily support large language models like AI. Who is responsible for maintaining a register in each department and actually the timetable to replace all those obsolete bits of kit?

29:14 - 30:32

Susannah Storey

Yeah, well, I mean, when I've been doing, um, my preparation for this committee, I've been really interested to read so much of what you have said in this committee and also the Science and Tech Committee. And I think you're rightly identifying the very real risks of legacy IT. And I know you've said before that you want a register. There is a 2024 number, which is 28% as you say, um, but we're not satisfied with that. So, um, my colleague in GDS has been leading, um, a programme of work called Firmer Foundations.

I've written to all my colleagues, all of the permanent secretaries, asking them to nominate somebody who's their responsible person who can give us the data on their legacy systems, and we're just collating that information. We're also looking at how we can get more automated updates on it so that we actually know the picture on a more regular basis. Um, and we're looking, um, at using coding tools to try and spot some of these vulnerabilities to try and make sure even when there are legacy systems that we can address some of the issues. So I am very clear that we will not have all of the many benefits of AI except if we can address some of these legacy issues. And it's also something that I want to work closely with the Treasury on as we go into the next spending review.

30:32 - 31:20

Geoffrey Robert Clifton-Brown

So my final question is on people, people within the civil service, because you can have all these policies, but if you don't have the people properly trained and qualified to operate them, they won't. And the Prime Minister has set out a, I think, a timetable for, um, 10% of the civil service to be properly digitally trained by 2030. Um, uh, can you set out how, how, and the expectation, this is in my Treasury minute again on the Bank of England's daily settlement, and the expectation for digital leaders across government will be sitting at executive committee board level by the end of 2026. So two things there: the executive board and how you're going to move to that 20 target as enunciated by the Prime Minister. It's a big target, 10% of the civil service to be properly trained digitally by 2030.

31:20 - 31:54

Susannah Storey

That's right. And so at the moment, I have a rather spuriously accurate number of 31,361 civil servants. But I mean, given the numerator and the denominator are moving, I think we're at about 5.5%, which is not where we need to be. So it's a focus, I think, for all of us across the digital, um, area. And from GDS, we're going to publish a digital workforce plan because what we want to do is try and give a better sense of where we are.

It's helpful to you, Parliament, holding us to account, but it's also helpful to us, the leaders of these departments who are responsible. So we're in progress, but we're not where we need to be yet for that 2030 target.

31:54 - 32:41

Geoffrey Robert Clifton-Brown

So I think given that these are such important matters, how government digitalizes matters because it will matter in terms of the productivity and the speed at doing things and communicating across government and communicating to the public. Can we get an undertaking from you that you'll publish some of this data on a yearly basis? How you're doing on staff and how you're doing on chief digital information officers and non-exec boards, all the things that we've just been discussing. I mean, it would be really helpful if we could have a number, maybe once a year, not just in the annual report and accounts, because that's always out of date with respect to everybody, but we really want a sort of some fairly up-to-date numbers each year. Can we have that?

32:41 - 33:03

Susannah Storey

Yeah, I mean, we are getting better, as the NAO knows, at publishing our report and accounts, and I was pleased to get ours out pre-recess, but I do take the point. Let me take that away. I mean, I think the Cabinet Secretary has been very clear that in the context of civil service reform, she wants to see our work on technology right at the top of the agenda, and there's a lot of things that we're doing as a group. So I'm very happy to take that away, and I absolutely understand why you want it.

33:03 - 33:13

Geoffrey Robert Clifton-Brown

That's very helpful. Thank you very much for those answers. I now move to Dame Chi Onwurah, chairman of the Science and Technology Committee. We'd be very pleased to have you as our guest today. Please ask your question.

33:13 - 33:50

Chinyelu Susan Onwurah

Thank you, and thank you, Sir Geoffrey and the committee, for inviting me. My question is initially addressed to Philippa Rouse, but let me know if anyone else needs to come in on it. So, could you describe for me the government's long-term approach to digital identity? And as part of your description, could you set out how you, what you understand by digital identity, and specifically how that, amongst other things, how that differs from OneLogin?

33:50 - 33:51

Do you want me to start?

33:52 - 34:20

Susannah Storey

That's a huge question, and we tried to sort of specialize on particular areas. So, just to be really clear, the policy for digital identity has come to DSIT as part of the machinery of government changes announced in July, but the national digital identity programme is closed. So, we are working with our ministers on the policy approach they would like to take as part of this government on digital identity.

34:20 - 34:33

Chinyelu Susan Onwurah

Could you please describe what, sorry, but it's hard for me to understand, I think, if you don't describe what you mean by digital identity. Then you've got a national policy and you're talking about whatever it was the other thing you were, but, you know, what do you mean by digital identity?

34:33 - 35:04

Susannah Storey

Yeah, I mean, I think in simple terms, it's how people can demonstrate things about themselves safely and securely and digitally. And as you know, at the moment, and the NAO report, I think, was really helpful in this regard, we have an ecosystem in the UK that has both private sector digital verification services and a trust framework, and we have all of the work that colleagues here are responsible for on GOV.UK OneLogin and the wallet. So those are the principal ways at this stage. I don't know if you want to add anything, Chris.

35:04 - 36:51

Speaker 16

Yeah, really happy to come in. So OneLogin is making it possible for you to log in to services in government and to do it through one approach. So at the moment, we had about 44 different ways of logging in. The OneLogin programme is now doing well. We've got 245 services on board, and we expect all the relevant services that need to have OneLogin in them to be on board in the next couple of years.

And we're just in the middle of the HMRC work to move to OneLogin.

But that's a sort of foundational step. Another foundation which does set is set out really well in the NAO report is what we do with digital credentials and wallets. And the work on the strategy at the moment that is now being worked through, two things on that. Ourselves in government, we are doing a digital wallet where we'll start, we've started already with the veterans card and we'll move to the digital driving license which we're building now. But we are working with the private sector to make sure that we're not just duplicating what's there already.

So we're now in conversation post the digital ID scheme closing to make sure we've got a strategy for credentials for the country. So that's the sort of second pillar. The third pillar is around joined up services. And so the work here is around how we make it possible to see an individual across government as one person. And that bit doesn't exist yet in government.

We've got some good examples of where we are sharing data, but that work is the work that we're getting into now as almost like the third pillar. And then fourth is the work on inclusion. So we have about 9% of the population who find it can't prove who they are because they don't have a driving license or a passport, and the inclusion programme will be one of the also one of the pillars that we work on.

36:51 - 37:45

Chinyelu Susan Onwurah

Thank you. I do think that's helpful. Just let me read that back to you to make sure I've understood it. So digital ID is the ability of people, British people presumably, to identify themselves digitally, to have a digital identity. The national digital ID programme, which was one digital ID for everyone, is closed down.

But the work that you are doing on enabling British citizens to identify themselves digitally continues and involves the private sector as well as the public sector and digital wallets and credentials etc. And as part of that you are wanting to be able, you are, so this you have a, you have an approach that or an objective that government should be able to identify people, individuals across all services.

37:45 - 37:52

Speaker 16

With consent. So just to build on that. So it's about the individual being in control of the data they share.

37:52 - 38:06

Chinyelu Susan Onwurah

Okay. So I think we'll come back, I'm sure there'll be a bit, but just in, so then if you were to summarise the government's approach to digital ID in that definition, what would you, what would you say? How would you summarise that?

38:06 - 38:37

Speaker 16

So government wants to make it easy for people to get what they need from government at point of need. Digital ID isn't just about the public sector. It's not, but that's, but also what it wants to do is make sure that people can go about their daily lives and be able to buy homes, rent flats etc. So we want to make it possible that it's not hard for them to prove who they are and so they can go on to perform the task they need to do. So it should always be need-based.

We should only be doing it if it helps citizens go about their daily lives.

38:37 - 38:51

Chinyelu Susan Onwurah

Right. And then what like what you were saying when I so rudely interrupted you was about in terms of for the the view of government view of individuals across services, that would only be with their consent.

38:51 - 39:30

Speaker 16

Yeah, so the work on that we're underway now and the appointment of Philippa into GDS is going to be helpful in that space and what our team go on to do. What we're doing across government is making sure that we build on what's there already. So we have some good examples of data sharing. You've probably used it yourself, some people around the room, where you apply for a driving license for example and it will bring in your passport picture if you say yes. So there are some good examples of where we share data already.

And we want to make sure that we're doing it with purpose. And so we're working with departments at the moment to make sure we're thinking about the problems that need to be solved. But the individual is in control of who they decide to share that data with.

39:30 - 40:01

Chinyelu Susan Onwurah

Just, I mean, I know a lot of people want to come on this, but is that always the case? Because for example if DWP, the Department for Work and Pensions, can share data on an individual with as I understand it Treasury or other government departments without the citizen giving explicit consent. And there are gateways I think as I remember which are which are allowed to do that.

So, so does government strategy for digital ID always involve consent for sharing across government?

40:01 - 40:41

Speaker 16

I'll just I'll define the answer if I can. In the context of digital services, then we are that is a consent model. There are many ways that departments think about sharing data, which sit within departments and are fully regulated by the department they sit in. The way I'm bringing the question forward and answering the question is around someone is within a service, they are proving their identity, they want to prove who they are and therefore they want to go on to perform a task. So in the confines of digital ID used in digital services, then consent is the model, but that doesn't mean that across government there aren't other ways that that data is shared.

40:41 - 40:53

Chinyelu Susan Onwurah

Just, how will you define a service then? Because benefits doesn't seem to be isn't a service, so a service, DVLA, is that what how do you define digital services then?

40:53 - 41:17

Speaker 16

Well, the strategy needs to be fully finished, but the work and it needs to be signed off obviously by the Secretary of State. But in essence, the what we're trying to do here is make sure that the identity we go on to do is purposeful for the individual using it. And so with that in mind, with a services perspective, that's where we're using the consent model, but we may be maybe different if we use it in different contexts.

41:17 - 41:28

Chinyelu Susan Onwurah

Let's not spend too much time, perhaps you could write to the committee or to me with how you differentiate between services that have the consent model and, you know, I think benefits is a service or whatever, which don't have a consent model.

41:28 - 41:29

Of course.

41:29 - 42:16

Geoffrey Robert Clifton-Brown

Could I follow that question? I mean, I'll probably know the answer to this, but I don't. If you were obtaining a certain benefit from DWP or or even HMRC, in the private sector you would probably sign a consent form for that information to be shared with another department. And given that this is a pretty serious matter, if you're claiming certain benefits, you're giving permission for HMRC or DWP to actually take money from your bank account. Is there any clause has to be signed at the moment you apply for that benefit, it should say you are giving your consent for another government department to look at your financial details, including your bank accounts?

42:16 - 42:34

Speaker 16

We're not that far on with the model yet, so we will happily as we go through the strategy, we'll be able to talk you through it as as the proposition comes forward. But at this stage, we we would only consider that as we as we go into the strategy and any strategy would be signed off.

42:34 - 42:44

Geoffrey Robert Clifton-Brown

Out of polite politeness, you started to answer the question. I don't want you to repeat anything, but if there was anything anything you wish to add to Dame Chi's question, I'm very happy to take it.

42:44 - 43:25

Philippa Rouse

So my my role as as Chris has set out from here on in is to to work with colleagues from across GDS and government to build that capability to enable some of that data sharing. So kind of absolutely will be working through and building on the kind of questions that the committee are asking and the NAO report that very kindly helpfully sets out and certainly working through some of those knotty questions and issues around under what circumstances is is consent required and appropriate versus some of the other powers that government has to share data, for example, to reduce or to identify and reduce fraud.

43:25 - 43:33

Geoffrey Robert Clifton-Brown

Okay. Thank you very much. I think I will now come to Sarah Olney, please.

43:33 - 43:35

Speaker 21

Where is she? Sarah, hello. There.

43:35 - 44:37

Sarah Olney

Thank you, Sir Geoffrey. Yes, so there's some interesting findings in the report about international experience of digital identity services. And one of the findings, and this is repeated across a number of countries, is that digital, you know, using a digital identity service has to be integrated or has to has to provide users with a quicker and more convenient way of accessing an existing service in order, and that's where you see the the greatest take-up. So I'm interested to know the practical benefits that could be provided by new digital identity services that cannot already be achieved using existing services. So where people are happily using existing services without the need for digital identity, do you think there are examples of those kinds of services where digital identity has a role to kind of enhance user experience?

44:37 - 44:42

Speaker 22

And I will ask Ms. Bellamy first since you are nodding quite vigorously.

44:42 - 46:36

Speaker 16

I'd just start first of all with the problem with the 9% who can't prove identity already. And so they don't have a driving licence or a passport and so they find it difficult to even start the journey. So that's one of the reasons that any advances on digital identity we could help to, one of the ways we could help solve that problem. I think when people come to services now, you have to present a lot of information many times. So one login gets you through the front door, but then you are starting to sort of have to fill in forms more than once, you're having to give information more than once.

So there is an opportunity there to think about how we may solve that. What we've seen from other international comparisons is that when you do that, you can make decisions quicker. You can see that in the Australian model recently where you're able to get people to services with much less toil because you're able to prove who they are across departments. So I think that's one thing to pull out. And and fundamentally what it's doing is the individual gets to see their data across different places so they can see where they are in a system.

So some of the benefits come through that way. Then also when we move out into the private sector, what we can see with the work on the digital driving licence, for example, a good example in the in the feedback from users when we've been testing it is that if you're a young woman, for example, and you need to prove your age, you're only 18 and you want to, you know, buy alcohol in a pub, at the minute you show all of your information. You show everything, your photo, your address. And moving to sort of digital credentials and digital wallet, that individual is able just to show that piece of information that says they can buy the beer. And so in doing that, we're able just to give more to the to the service that they already have through that credential.

46:36 - 46:46

Speaker 23

So we can see there's quite a few benefits. There's more to do to make sure that there's value for money in any credentials that we do. And we want to make sure we get that right.

46:46 - 46:58

Sarah Olney

Ms. Storey, if anything else to add in terms of the the benefits that the digital ID can or digital verification can add in those places where it's going to be a new part of the of the process.

46:58 - 47:26

Susannah Storey

I mean, I think from our perspective, and we've really found the NAO's report very helpful, including the annex two, which runs through 12 things that are important. And it's one of the things we want to look at in any future strategy when ministers make their policy decision. But I think we know that any service needs to be convenient to get take-up. I think Natalie, it's fair to say, isn't it, in the work you've done on GOV.UK One Login, that some of the benefits have been from reducing fraud and increasing access.

47:26 - 47:28

Speaker 24

You might want to say something about that.

47:28 - 48:17

Natalie Jones

Yes, I think in terms of digitising services, it's always been a requirement for people to prove who they are for certain things. But actually a lot of those processes were inconsistent, they weren't designed necessarily with a full understanding about where they would find people, so people without, Chris has already mentioned people without photo ID. One Login is focused on creating a simple front door to access all government services on the basis you do it once and then you reuse it. Up until One Login there was a sort of one-to-one relationship between having a username and password and proving who you are. So you would prove who you are to DVLA and then you would prove who you are again to DWP and then you would prove who you are again to HMRC.

And what One Login enables you to do is prove your identity once and well and then rely on that evidence to access other services.

48:17 - 48:26

Sarah Olney

Can I just quickly ask, when you say once, you mean once for all time or once a day, once a week? Because I'm not accessing all of those services continually.

48:26 - 50:12

Natalie Jones

So One Login, the first time, so not all government services require you to prove your identity. It's based on the sensitivity of the data or whether the thing is particularly tied to you. So obviously for a driving licence it's really important you are who you say you are, but if you're paying your car tax it actually doesn't matter who you are, you just need to have the means to pay. So the first time you as a user create a One Login and you access a service that requires you to prove your identity, One Login takes you through an identity verification process using things that you already have. So if you've got photo ID you can use that, but if you don't there are ways for you to prove who you are using other means.

And then once you've done that, that verification of your identity is stored in One Login so that if you go to another service that requires identity you don't need to do it again. So once and for all. I would say there are some caveats around that. One of the things we've discovered as we've worked through One Login and with the bigger departments is it's not ideal to identify somebody and not look at that account for a decade or two because actually accounts can be compromised, it's hard to know then when the person behind the keyboard is who they were originally. So One Login creates an account for you and it curates that account and it looks out for signs of attack or fraud.

So for example if we could see your credentials accessing eight services in the same minute we might think that's a bit weird, is it really them? And so we have fraud analysts who would look at the telemetry that comes off the back related to fraud and investigate for you. So in an ideal world you would prove your identity once, your account would stay within a normal parameters of activity and therefore you wouldn't need to prove your identity again. But in some scenarios if perhaps we thought your account had been compromised we might ask you to re-prove your identity at that point. But it's not expected that people will have to do it routinely every six months or every year or anything like that.

50:12 - 50:14

Speaker 25

Did you want to clarify a point?

50:14 - 50:39

Chinyelu Susan Onwurah

Yes, because thank you very much for the description of One Login and we understand that it's not wholly HMRC, it's not rolled out there yet fully. And perhaps clarify that and also the NHS which does have digital login, I have digital login, but whether that is going to be, you know, is going to be part of One Login as well.

50:39 - 51:49

Natalie Jones

So we've been working with HMRC in partnership for about four years. They're a huge organisation with complex fraud and user needs. HMRC is now fully onboarded to One Login as part of its first phase. So if you are a new user and you don't have an existing Government Gateway you will now never need to get one. If however you're one of the 32 odd million people who've still got Government Gateway you'll be in wave two and we'll be migrating you over and we're expecting that to start next year.

And then there's a third set of people that use HMRC services and that's those that interact with HMRC as part of their professional lives. HMRC refers to them as agents and orgs, I think large number of accountants for example, and they're wave three and we're currently in the design phase with HMRC about when they will onboard. In terms of health, yes sorry, and NHS in terms of health, there has always been a separation. So there are no current plans for One Login to sit on the front of health services or for the health service to sit on the front of government services because there's a sort of mental gap in the way people perceive these things.

Health and central government services are kind of separate.

51:49 - 52:18

Geoffrey Robert Clifton-Brown

Maybe this is the point to ask you, Natalie, but maybe Susannah wants to come in on this. There's one word that I think is very, very important in all of that, and that is trust. I think trust is the one thing, because of dramatic stories of hacking and one thing and another, that public are very concerned about the rollout of digital and the government holding more and more data on them. How's the government going to overcome that?

52:18 - 54:35

Natalie Jones

So, if I, if I could talk about a sort of practical example with one login, um, I'll, I can talk you through the sort of security model, but at a principle level, one login holds the bare minimum of data it needs in order to operate. So it is not a big data lake. The amount of information it holds about individuals is a very small number of data items. So the first thing to say is it's not a big target in that respect. That data is also kept in disaggregated places, so again, if you wanted to get hold of that data, you need to break into a number of different places in the system before it would be of any use to you.

It's also built with privacy-enhancing principles in mind. So, one login effectively works a bit like a security guard on a building. So when you want to access a service, it says, "Have you got the right pass?" and then it checks that the pass has got your face on it and it'll let you in. But that security guard doesn't know what you do in the building, or what conversations you have, or what data you access, and neither does one login. And that's a conscious design choice.

So one login does not know what you do when you get into the service. It knows what time you accessed the service and what time you left, and that's it, and it checks your credentials as you go in to be sure that it's you. And that's useful for things like fraud. So like I said, if you're accessing eight services in the same minute, we'd be like, "Hang on, that's weird," and it would trigger an alert because we might think your account had been hijacked and we'd send you a message to that effect. So similarly with verified credentials, one login works like a sort of perimeter fence for all government services, and it also will protect the gov.uk wallet.

So while it will know that you downloaded a credential, it doesn't know the contents of that credential. So when we roll out the mobile driving licence, it will know that you downloaded a driving licence, but it won't know whether you've got any points or whether you can tow a caravan. So it, it, it just holds the minimum amount of information it needs to perform its, its job as that security layer. Um, it's not, it's not, it doesn't hold or track any further data than that. And actually, just to, there's a thing, um, in the report that's quite helpful on page 20, um, paragraph 1.22 and 1.21, there's a thing about, um, identifiers.

So one login does not issue a single identifier to people, and in fact it does make use of tokenization, which is a privacy-enhancing, security-based protocol as well.

54:35 - 54:53

Susannah Storey

I think that we do really agree with you that it's absolutely critical to have trust, and that's something obviously across the wider digital system. And I think the other point just to flag in the NAO report is when you talk about transparency and accountability, so that's certainly something that's important as well.

54:53 - 55:23

Clive Betts

Of course it is. My understanding is that Estonia, which has built a very comprehensive system of putting people's various information together in, in one place, they, they I think have a privacy enhancer, if you'd call it, where if anyone else goes in the system, the person whose system it is, the person whose data is there, can check who else has accessed it. Is that something you're building in as well?

55:23 - 56:11

Speaker 16

It's a it's a really really good point. Thank thank you so much for it raising it. Estonia has a single identifier system. When you're born you get a an identifier. So it's sort of built from scratch its system.

But what it has done really successfully is is made sure that the individual is is in control. And so if somebody access your account you see everybody who's accessed it whether it's your doctor whether it's someone who's just you've rented a flat you see all of those interactions. So when we look through the proposals going forward we want to make sure that um when we're working both with the private sector and locally we want to make sure that we've got we think about those going forward. And so as we design the strategy that we will we will make sure that we consider it. And if we can make sure that that's part of of it going forward then we'll consider it going forward.

56:11 - 56:13

Speaker 27

Make sure you'll consider it?

56:13 - 56:25

Speaker 16

Sorry we'll make sorry I can't say today because we've not fully formed the strategy but it's definitely in there as something that we believe is something that we should be doing in the UK but we're yet to finalize the strategy.

56:25 - 56:29

Speaker 28

When will you be able to tell us whether you are going to do that?

56:29 - 57:00

Speaker 16

So the strategy is now um being worked through and will go to Secretary of State for approval now we've moved to DCMS. And so that work is in flight now. We're just a few weeks um post the ID scheme being scrapped. So we're working hard and fast to make sure that we've got the right strategy for the UK that also works in conjunction with the private sector. But trust is at the at right in the in the heart of it and absolutely we'll be thinking about those.

So I think in timelines we'll come back to committee with the timelines on that going forward.

57:00 - 57:01

Helpful to do that.

57:01 - 57:02

Yeah of course.

57:02 - 57:21

Chinyelu Susan Onwurah

That's very kind. Thank you. A very short question. Um so just to just to clarify the ambition to have one view of the citizen across government that is associated with One Login so it would not go to to the NHS.

57:21 - 57:28

Speaker 16

The all of the research so far is that they stay separate because that's become from that's what that's what users are telling us. Yeah.

57:28 - 57:37

Chinyelu Susan Onwurah

But the ambition to have one view of across government is is there and that's associated with One Login. Fantastic. Thank you. Chair.

57:37 - 57:39

Speaker 29

Matt Tame please.

57:39 - 58:04

Matt Tame

Um thank you Chair. Hi. I'd like to ask a few questions if I may about the uh costs of developing and operating an integrated service. So do you think that there is or do you have the understanding of what those costs are likely to be for future services that you're looking to roll out uh and and also indeed in terms of the rest of the work for One Login?

58:04 - 58:21

Susannah Storey

Yes so um I mean when ministers decide their policy overall then we'll have the scope of it and then we'll be able to cost it. So I can't give a future hypothetical cost um but Natalie do you want to talk about some of the costs of One Login because we have obviously got a track record there it's been running for a few years and we can tell you about the costs and benefits if that's helpful?

58:21 - 59:33

Natalie Jones

Yes certainly. So One Login benefits from being on the Government Major Projects Portfolio so it has a fully approved um business case. So far it's realized 752 million in net benefits from April 2022 to the end of August 26. Um and those benefits are driven by reduced identity-related fraud 396 million reduced duplication and cheaper digital access to services 218 million and time saving for end users at 138 million. The current business case runs out to March 2028 um with a total net benefits um figure of 2.83 billion by then.

So and that's against a total um cost of 702.94 through to March 2028. So One Login has a mature benefits realization um plan. Um we had a a model on how much fraud it would stop which we worked through with the Public Sector Fraud Authority.

We started with a conceptual model. We've just gone back for the second iteration with some actual data from DVLA to show how effective our fraud detection is and what kind of net benefits that's putting back into the economy.

59:33 - 59:57

Matt Tame

And and you're concluding that it's proving beneficial then presumably? Okay. Okay. Great, thanks. So um just and I do appreciate Susannah that you can't because because it isn't defined you can't tell me what the cost would be but you have an understanding through the experience of OneLogin of the kind of magnitude of costs and the and the feasibility of being able to to launch other services that would...

59:57 - 01:00:35

Susannah Storey

I mean I think the way we've looked at it and this is consistent also with what the NAO is saying is there's kind of costs of building and maintaining whatever the service is if it isn't something that we have already. And obviously the benefit of gov.uk OneLogin is it exists, it's built and it can be scaled. Then the costs of any kind of connecting of services and kind of ongoing hosting including things like cybersecurity. And I think we're all conscious that at the moment you know the need to have really good cyber protection is going up the agenda. So that's a sort of general answer but I think it would be better when we have the policy decisions from ministers to come back to you if that's okay.

01:00:35 - 01:00:38

Speaker 37

That would be great and if you're happy to do that that would be really helpful.

01:00:38 - 01:00:41

Speaker 32

Of course, because if we have a strategy we'll publish it.

01:00:41 - 01:00:51

Speaker 35

Understood, understood. I mean you obviously it's sort of I guess within a context that IT infrastructure costs often balloon and become very much more expensive than anticipated.

01:00:52 - 01:01:04

Speaker 38

But as a committee we have seen reports and examples where such projects have been delivered lower than the cost anticipated and within time. So obviously it's of interest from that perspective.

01:01:04 - 01:01:06

Speaker 34

Great, thank you very much.

01:01:06 - 01:01:09

Speaker 33

Okay. Well done. That's me done for the moment.

01:01:09 - 01:01:13

Speaker 31

Thank you very much. We come to Sarah Green please.

01:01:13 - 01:01:41

Sarah Green

Thank you Chair. I'd like to revisit some of the conversation we were having earlier. So back in July the government announced that it was no longer pursuing a government-issued digital identity and you've confirmed that the national programme has closed. But is it not the case based on the answers you've given us this afternoon that the infrastructure of digital ID in the public sector is still being pursued?

01:01:41 - 01:02:40

Susannah Storey

So the there was a specific task force focused on Keir Starmer's national digital identity programme and Philippa was in it and some others and that work was looking at the specific policy intentions they had for a national programme. And as you know and I think various select committees have had evidence from some of the people involved, they were going through the consultation and it was stopped in July. There are within the work that we do identity attributes and the trust framework that Rod's team are responsible for, that's all about having DVS providers who meet that and then gov.uk OneLogin also has ways of identifying people but that is not the same as a national digital identity strategy which as you know before started out as a mandatory thing and then changed to voluntary.

01:02:40 - 01:02:42

Speaker 30

How's it different?

01:02:42 - 01:03:09

Susannah Storey

I guess from our perspective it's having through gov.uk OneLogin services where people can identify themselves but they can use other means if they want. If they're getting DWP services they could go to the post office, they might never be digital at all. So we're trying to provide services that work and enable people to use them digitally but they can also use other means. And I don't know if you want to talk a bit about the trust framework Rod.

01:03:09 - 01:04:49

Rod Latham

Yeah thank you. So um yeah I oversee the Office for Digital Identities and Attributes which tries to provide a level playing field for public and private sector so you've got kind of clear rules of the road on audits. That is underpinned by the Data Act that was that sort of passed before passed by Parliament before the announcement about the national digital ID programme.

And so what we're doing with that is sort of continuing on that that same trajectory that that we're on before and Parliament has put various statutory functions on us that we're now kind of in the process of of implementing. I would add on what Susannah's said, there's and having been involved with the national digital ID program early on. So we've got we already had OneLogin and the Gov Wallet, which were sort of existing plans. We already had the work we were doing with the trust framework to try and provide that sort of clarity and and rules of the road and I'm very happy to kind of get into that in more detail. What the national program was principally about was in ensuring a kind of an extra, a new product that that could be made available to everyone who wants it.

That is no longer something that we're looking at doing. The the big thing that we we therefore need to kind of do on the back of that is inclusion. So for those who who don't have passport and driving license and some of those documents, how can you prove your identity without them? So I think Chris has already spoken to a number of things that they're doing through the trust framework. We have we kind of embed inclusion as a as a part of how we're trying to encourage everyone who's operating under the trust framework to be thinking about inclusion and and accessibility.

01:04:49 - 01:04:52

Speaker 44

And I think there's probably more we can we can kind of do in that space.

01:04:52 - 01:05:23

Sarah Green

Thank you for that. So my my final question before I hand over, because I know other colleagues will have questions for you, is how you how you address the privacy concerns that members of the public have. You can see that some of my questions are driving at that. How do you we were talking about trust earlier with the chair. How do you because from where I'm sitting, it does sound like the infrastructure's still being put in place.

How would you address someone like me or someone watching and allay their privacy concerns?

01:05:23 - 01:06:18

Rod Latham

I'm happy to start off on on sort of the wider piece that we do and then others might want to to come in as well, chair, if if that's all right. So the the purpose of what the trust framework does, as I say, is to try to set rules of the road and standards for for every operator, whether that's private sector or public sector. Security and privacy are absolutely at the heart of that. It's designed to give people the confidence that if you're using something that is on our we have a transparent register of who's sort of passed the accredited checks to get there. So people can see who that is.

We're we've recently rolled out a trust mark so people can kind of see that to try and make it easier for people to understand what's on there. So in order to be on that, that means you've gone through those checks around privacy, security and security, data minimization. So that the the kind of idea of what we're trying to do there is set an environment in which whoever's providing that service, a user can be confident.

01:06:18 - 01:06:20

Speaker 42

You're overseeing that?

01:06:20 - 01:07:07

Rod Latham

So my my team in in DCMS sort of look after this ecosystem. So we publish the the trust framework. We're required under the Data Act to update that on at least an annual basis. In order to get on our register to say you've kind of met those standards, you have to be accredited by a a separate and independent body. We have two at the moment that do that.

We're we're looking to try and encourage more into that market. And those conformity assessment bodies are themselves then accredited by the UK Accreditation Service. So so we have sort of multiple way checks in the in the process to make sure that, you know, we have the rules, they are being followed, people can see that they're being followed and that they can have confidence in that in the system as a whole.

01:07:07 - 01:07:10

Speaker 41

Do you want to just touch on gov.uk OneLogin?

01:07:10 - 01:07:51

Natalie Jones

Yes, if I can just say building on the things I've already said about data minimization principles. So the privacy notice for OneLogin is already public. And we've agreed to publish the data privacy impact assessment by the end of the year despite having no obligation to do so in pursuit of transparency. That's actually been with the ICO once. We've got some updates because we've got new routes.

So every time you add a new piece of functionality, you have to then update it. So the latest version is with the Information Commissioner's Office. They signed off the previous one and we'll be publishing that as well. And OneLogin is also certified against the trust framework to make sure that we're meeting those standards around privacy, security and and transparency.

01:07:51 - 01:07:54

Speaker 43

Thank you. So I'm going to hand back to the chair because I know that other colleagues will have similar questions.

01:07:54 - 01:07:58

Speaker 40

We'll come back, Sarah, if anyway, Rupert, please.

01:07:58 - 01:09:47

Rupert Lowe

Thank you, Chairman. Yes, I should disclose that as a sitting MP I'm implacably opposed to digital ID in any form. And I'm eternally grateful to Silkie Carlo at Big Brother Watch for all the work she does on identifying state intrusion into the electorate's lives. Listening to you, I'm nervous about the business of convenience. The government always sells things to people on the basis of convenience, a bit like they tried to sell the Euro to us on the basis of convenience.

So I don't like being sold things on the basis of convenience, so I'm immediately suspicious. I think, you know, thanks to the NAO, as you say, they've produced another fantastic report. And I thought the key bit in that to me was in the summary, which says to deliver value for money, digital identity will need to be both usable and trusted across both public and private sectors with individuals being able to use it easily, securely and consistently across services. That's to me the key statement. And then I look at the trust in the UK government from the electorate.

And I see that trust in government in the UK is regularly closer to Colombia than it is to either Estonia, which Clive used, or indeed Denmark. And usually about 10% lower than it is in France, which is pretty amazing given what's happening in France at the moment. So I think my question to you is how are you going to convince the electorate to trust you because as the NAO says, you're not going to be able to make this work unless people trust the state and failing states, which I consider us to be, have a history of clipping coinage and generally robbing their electorate. So how are you going to get the British people to buy into this?

01:09:47 - 01:10:46

Susannah Storey

Should I start and then I might hand over? I'm not going to answer all the points in there because there was a lot, but I think in the heart of it you're making the same point as the chair about trust and we very much agree with that. And I think what we're trying to do firstly is deliver any policy that ministers might have in this space and then for the services we already have, so gov.uk OneLogin and the trust framework, make sure they're as clear and transparent as possible. And then hopefully as the NAO say, people will want to adopt them because they will understand how to use them, they'll know what they're trying to do and then they will be more, there'll be greater adoption. So I think our job is to do these services well, clearly, transparently and to take the lessons from the NAO's report.

01:10:46 - 01:10:48

Speaker 45

I don't know if there's anything you want to add.

01:10:48 - 01:12:58

Speaker 16

Yeah, really, really happily. I think it's a real fair challenge. I think in the UK, the products and service that people come to to access government services is gov.uk. And the trust number for gov.uk is about 82%. So it should be more than that, but it's 82% and holds firm at that number.

And it sits when you look at all the research, it sits sort of to the side of the government of the day. It's very much about service in its own right. And people use it when they need it. And so OneLogin, the reason OneLogin is OneLogin is because it builds on the credibility of the gov.uk work that people use in their daily lives. And so it builds from a foundation of trust.

But absolutely we cannot break that trust of making sure that service works for them. And I think it ties to the question before. The point then is that we're making sure that people come to services and they access them in their daily lives and they're able to be in control.

And we've talked about consent before, but control's a better word. And we need to make sure we do that when it comes to identity. So what we published in the digital blueprint was that the identity credentials we would do were ones that people had already. So as an example, the veterans card, we do have a digital credential for veterans and you can download it into your wallet, a digital wallet. And it means if you're a veteran, you can get access to discounts on particular outlets in the UK, you can get into museums at lower cost, etc.

And we were finding from veterans that if they didn't have it with them, they didn't get the benefits of it. So the benefit there was making sure that you could prove you're a veteran at point of need and you could go about and have access to it. The driving license is the same. DVLA are telling us that people are asking for them to have that credential on their phones because it'll make it easier for them to hire a car in this country and abroad. So I think it has to be secure, it has to be trustworthy, and it has to matter.

But the current credentials will be ones that exist that we have already in government and we'll be using them in a digital setting. So we need to make sure that they work for the user. And the gov.uk product and service is the one that users will use. And we need to make sure always that that stands the test of time and is trusted.

01:12:58 - 01:14:08

Rupert Lowe

Again, that sounds more like convenience than trust. So again, I look and the British people look, they're not stupid. And they see that the current Secretary of State for DCMS, she was heavily involved in Think Labour when it was known as Labour Together, was rebadged after a series of scandals. Now they were pretty implacably supportive of digital ID. So I think again, if we're not careful, we will end up getting digital ID by the back door rather than the front door.

And although you tell us that's not the case, I again, I think this comes to the trust point. People don't necessarily trust and believe that what they're being told is true. Now that may be because of COVID, it may be because they watched what Trudeau did in Canada with the truckers, it may be they look in China and government there starts to make judgments about whether they're living a good life. So I think you've got a big problem unless you can win the trust of the British people. And that's what the NAO I think very eloquently state.

01:14:08 - 01:14:12

Speaker 50

So I'm not sure what we've heard today convinces me that you will be able to do that.

01:14:12 - 01:14:16

Speaker 48

Right, okay. Susannah, do you want to try that one?

01:14:16 - 01:15:21

Susannah Storey

Very happy to. It was a broad, a broad... I don't think you need to do the political bit. Okay, well, yeah, I wasn't proposing to do that. Except to say I think that as and when we do have a policy decision around this from our ministers, I'm sure my Secretary of State will be happy to come and talk about it.

I mean, I think one of the things that's interesting is we know in a world of the AI tsunami, Chair, that you were talking about earlier, there will increasingly be need for people to be able to prove who they are and they're not a bot or an agent. And I think we're going to see a lot more questions in these spaces, whether it's the private sector or the public sector. So again, what we're trying to do here is make sure for the services we've got, they're clear, transparent, convenient, so that we can hopefully people will want to use them, but there will be other routes if they do not. And then with the trust framework, it makes sure that for those certified bodies, they're meeting a certain set of criteria, which hopefully give an increased amount of trust.

01:15:21 - 01:15:28

Speaker 49

Thank you. Anything further, Rupert? Not for now, Geoffrey. I think I've got another question. Good.

Guy, please.

01:15:28 - 01:16:30

Clive Betts

Oh, without being controversial, I'd just say to Rupert, look, I was born in the last century, but I've still got to have regard as an elected representative to the fact that life has changed in this century and people expect to see things done differently, particularly younger generations.

And therefore we've got to adapt what we do as a parliament, as a government, to ensure we take account of that. I mean, on my phone there, look, I've got various apps for retailers, for an energy company, for Sheffield Wednesday season ticket. All this stuff's on there. Why you don't have some stuff on about government and its services to enable you to do things more easily, I don't know. So I'm going to ask the question then.

It is a question. When looking at whether you do things anew or go and build on what's already there, particularly in the private sector, how do you make those judgments? Because building something new, all singing, all dancing seems great, but actually what's in the private sector may make it quicker to do it. So what's the balance and how do you make those judgments?

01:16:30 - 01:17:09

Susannah Storey

Well, first just to say in terms of the app, there is a gov.uk one login app, so hopefully if you want to, you can download that on your phone. The things that we will be doing and I think already do is really use the NAO's report to think about how are we clear about the roadmap, are we confident about the value for money, and that's the way we'll make decisions about future services. But at this stage, as I say, what we're doing is scaling gov.uk one login and the wallet and then continuing to certify future DBS providers.

01:17:09 - 01:17:13

Speaker 52

Right, and the future, how are you going to make those judgments?

01:17:13 - 01:17:36

Susannah Storey

Well, I think it comes from the policy decision ministers make. So if they decide they want to do something different, something more, something new, then obviously we'll look at what do we think is deliverable, what's the VFM, and also the useful 12 points in the NAO's annex two where they're helping, you know, show some of the criteria that are useful to look at.

01:17:36 - 01:17:43

Speaker 53

What discussions are you having with what parts of the private sector to see what they can contribute and how?

01:17:43 - 01:19:52

Rod Latham

So one of the things we're doing in response to the first part of your question as well is working with departments across government because just the way the kind of the legislation and everything works at the moment, there's different acts that put different requirements on things. So we've recently worked with the Home Office, say, to change some of the legislation around proving your age for buying alcohol, which is quite a big kind of use case. So in terms of where we're looking at the kind of public-private sector interface, we're working with public sector organisations to sort of change some of the legislation, but that then can enable public or private sector solutions. And when we look at things like right to work checks, you know, there are already private sector organisations who are doing millions of those every year. So it's sort of often we're trying to kind of, you know, do what government, only government can do and then enabling the private sector to then kind of find and build on those markets.

We try and take a very kind of open policymaking approach in how we engage with the private sector. So we are constantly kind of talking to both the kind of the digital verification services industry, but also then what we call relying parties, so those parts of the private sector, you know, it's not just about those who provide the technology to check digital identity, you need someone in the pubs, the clubs who've also then got the technology to receive it, the supermarkets. So we do engage with sort of lots of different parts of business to try and understand what would work. Is there something that we don't have in say the trust framework at the moment that would be useful? And as I say, we're required to update that trust framework every year so we can work out what needs to change.

We've recently put it up on GitHub. It's open there for people to make comments and say what they disagree with, what they think we should be changing. So we're trying to do this in a way that opens it up to the private sector to be able to say you know what their views are and what would be most useful so we can kind of build a system that works for them.

01:19:52 - 01:19:54

Speaker 51

Is it okay if Natalie comes in as well?

01:19:54 - 01:22:21

Natalie Jones

So building on what Rod said as a practical example, with the digital driving licence. So we've been clear from the off, the strategy has been that the digital driving licence you'll be able to use in all the same ways as your physical one. So primarily it's about your right to operate a car but people use it to pick up parcels, to buy beer if they're under look under 25, to place a bet on the Grand National. And so I think of it as building two halves of a bridge. So government owns that data, we have it, we can offer people the opportunity to put it in a wallet much the same people now use digital boarding passes and gig tickets.

You know, you could have a digital driving licence. But it only really works as Rod said if somebody at the other end is going to check it and enable you to actually buy the beer. So we've got a bit of a chicken and egg situation. So we've been working really closely in the Government Digital Service with industry and just last week we opened up a sandbox. And what I mean by that is it's a testing environment that enables the private sector who are certified against the trust framework to actually integrate with the wallet technology that we've got.

So we've got a test version to check that it all hangs together so that an individual can go to DVLA, download a driving licence, they can show it in their wallet, it can be checked by the private sector and then that can cascade all the way to a pub or an online business that's got some sort of regulated use case. So when we talk about working in partnership with the private sector it's true, we've been partnering all the way through. The sandbox opened last week. We're planning an event in December where we invite those private sector providers into the Whitechapel building so we can do some live end-to-end testing to check that all the technical protocols because we're all building to the same technical interfaces but there's always you know sometimes when you put things together they don't work absolutely perfectly. So we're fine-tuning that.

The next phase of that testing will be in December when they come to the Whitechapel building with a view to starting a national rollout next year. And we can only do that, a digital driving licence is only useful if there are people ready and shops and and businesses ready to receive it. So we really do have to make sure that our comms and our technical planning and our kind of stakeholder management and partnership with industry all come together at the same pace so that we can put out something that's comprehensively useful as opposed to academically interesting which it could be if all the pieces of the puzzle weren't there.

01:22:21 - 01:22:30

Speaker 54

Just a few follow-up questions, presumably it's not just going to be the digital driving licence then that will be usable by private sector companies?

01:22:30 - 01:22:56

Natalie Jones

No, so all the credentials that go in the wallet will be over time. So we're working across Whitehall with all the departments on things like proof of benefits, your pass certificate when you first take your driving test, your disclosure and barring certificate. We've identified upwards of 80 plus pieces of evidence that government provides to people that they then use to prove something about themselves somewhere else. And so they're all in a in a roadmap to go into the wallet.

01:22:56 - 01:23:33

Clive Betts

Just one follow-up to what Rod Latham was talking about with the the fact that there are certain parts of the private sector that need to find people's identity and prove it in order to comply with government legislation. It could be landlords letting a property or an employer employing someone to make sure they have the right to work, the right to rent. One of the complaints you get sometimes is well we get shown this piece of paper, we're not sure whether it's actually true. You know someone can come along and say well that's my proof that I can be in this country and can work, well is it? So how how are you going to make sure that the robustness of the data there is sufficient to comply with those requirements?

01:23:33 - 01:24:30

Natalie Jones

So one of the really big advantages to digital versions of documents is exactly that. So as long as they are programmatically checked, they are much harder to fake than their physical counterparts. So when you show your ticket or your boarding pass, somebody scans it. And when they scan it, they are checking that it came from the right source, that it hasn't been tampered with, that it meets all the security protocols. So the credentials that go in the wallet that will be read by the private sector will meet all of these things, so that a retailer will get a green tick.

And it bakes in that selective disclosure as well. So there was the example earlier about the person only disclosing the fact that they're over 18. The person in the pub or the business will scan the thing, they will see a green tick that says over 18. But it's also checking that it hasn't been tampered with, it came from the right source, and all of those security boxes have been ticked. So it's much harder to fake when programmatically checked than a physical driving licence, which you can find on Amazon.

01:24:30 - 01:24:51

Clive Betts

And back to those requirements then, so the issue is one being here legitimately and being able to work. Um, how are you going to make sure that person has the necessary digital ID because the pieces of paper can be fraudulently produced when the digital ID can't?

01:24:51 - 01:25:45

Natalie Jones

So in the first instance, the offer of a digital driving licence is entirely in addition to the physical driving licence. So it will be an optional extra. And we need to see what adoption rates are like. And there will always be people for whom the physical alternative remains the better choice. So I think it's a little bit organic.

We need to make it useful, the market needs to mature. And over time, I would expect more transactions to move towards the very convenient, you don't have to carry a driving licence or your passport with you because you've always got your phone. And a lot of the cases are related to proving your age, and the youth are seldom seen without their phone in their hands versus tucking their driving licence in the back of their phone case. So from a sort of fraud and a theft and a loss perspective, actually having it on your phone is more secure for them as well.

01:25:45 - 01:26:58

Rod Latham

It was just helpful to, so what the change that we've done with the Home Office recently is, so that if you are doing a right to work check digitally, you have to use a digital verification service provider that's on the register that we run. So businesses will be able to have the confidence that who they're using has the kind of, is able to do that programmatic check and has the kind of right secure and trust. It is not the only way to do it, you can do non-digital checks. But if you're then doing that digital check through someone on the register, you then have a kind of statutory defence to be able to say, you know, I followed this process, this, you know, I had reason to believe that this was something that I could rely on. And if something goes wrong and you've ended up employing someone that you should not have been, that a business then has a statutory defence on that.

So I think what we're trying to do in that particular case of right to work is to be able businesses to have confidence that there is a way of doing this to a really high degree of confidence and security and transparency. But as Natalie said, it is not the only way to do it. This is a difference to the national ID programme. There are always going to be alternative ways to use as well.

01:26:58 - 01:27:02

Speaker 55

Thank you very much, Clive. Sarah Olney, please.

01:27:02 - 01:28:02

Sarah Olney

Thank you, Chair. And just coming back to Mr Latham, just sort of take that a little bit further. I mean, there are, and Ms Bellamy mentioned earlier the point that was just raised about only needing to prove your age when you're wanting to buy an age-restricted purchase.

Do you think that there are gaps in terms of either the current, in terms of what digital identity can currently prove about you? Does that match up with the things that retailers, as an example, age-restricted goods, but also I suppose right to work, right to be in this country? Does digital identity currently provide that, and if not, what are you doing to fill those gaps?

01:28:02 - 01:29:44

Rod Latham

I think this gets to how it is a slightly mixed picture across different cases at the moment, which as I said just reflects that there's historically lots of different pieces of legislation. One of the things that we're trying to do in my team is kind of go systematically round to work with the government departments and through them with different sectors to try and understand how can we get this into the best shape that it could possibly be. So that's why we worked with the Home Office on alcohol and age, and as Chris mentioned, as you mentioned, one of the bits of feedback we had was around trying to minimize how much data an individual is giving out about themselves. Another piece of feedback we had from supermarkets was around trying to avoid their staff being put in a position where you have to ID someone who's maybe an aggressive 17-year-old, so they don't have the right to buy it, but it can be quite difficult for their staff, whereas if you've got a programmatic check, digital ID, it's all sort of being able to be done effectively without a human having to do that proactive check. So we've done that work with the Treasury on money laundering.

So what we're now trying to do is move on to other things: tobacco and vapes, knives and crossbows, property. So we're kind of working through with departments to work out what are some of those gaps and then trying to work with them around what needs to be changed to address it. And we try and open this up and engage with different sector bodies so we're getting that feedback around where do people see that there might be opportunities, as I would see it, for digital ID.

01:29:44 - 01:29:50

Speaker 57

What do you think are the biggest gaps at the moment as you progress along that road?

01:29:50 - 01:31:34

Rod Latham

I would think that the gaps that we have, one gap I'd say, so there's these gaps on adoption where as I say we can see cases like tobacco and vapes, property, knives and crossbows where we can see opportunity in trying to bring people into the system that we're running to ensure that those are secure and trusted. I think there's other gaps that we're looking at more broadly around how the system that the Office for Digital Identity and Attributes runs. So we might consider at the moment we did a call for evidence on trust services, which is things like e-signatures, which is slightly different but kind of adjacent to this. So we're probably going to do a little bit more work looking at that. We've mentioned inclusion a number of times and again we've got things in the trust framework that try and encourage people to be thinking about inclusion.

And inclusion is quite broad in this sense because as we've touched on you can get the digitally excluded, the identity excluded, and core accessibility. So I think we'll be looking as well around some of the things we can do to try and promote greater inclusion. So I think there's something around adoption, supporting, and hopefully I've given some sense of some of the use cases. There's something around continuing to hone the system which will have to keep going because the technology changes and the circumstances change. And then I think longer term we've got a desire to be interoperable with international partners, but that is something that will take some years to get to.

01:31:34 - 01:31:38

Speaker 56

Thank you. Thank you, sir. Rupert, please.

01:31:38 - 01:32:13

Rupert Lowe

Thank you, Chairman. Yes, I think the committee's quite keen to know why it is that it's been so difficult for you to connect all this data across various platforms. I mean, you collect a lot of data through the passport office, through the driving license, through pensions, through the NHS number. You've got all these various identification tools which you currently have. So why's it been so difficult?

Is it civil service bureaucracy? Is it IT problems? Is it logistical? What, why is it so difficult?

01:32:13 - 01:34:18

Philippa Rouse

So clearly over the years lots of different departments have built their systems separately. And again, I think the NAO report, figure seven on page 18, sets it out really well. The kind of history as to why these legacy systems have built up, so they have been different departments have built their systems for different purposes, to different outcomes. As Natalie's already touched on, actually different departments will have different identity and security standards depending on the service and the interaction between the service user and the department. And then as you've highlighted, different identifiers, national insurance numbers, unique tax reference numbers, passport numbers and the like.

Departments will have built their systems differently for often for good reason. So departments have had responsibility to ensure they're only capturing and processing the information they need to be able to make the decisions they need to make, to deliver good value for money. And departments will have been on, as this committee will have reflected on, their different transformation journeys. So what that means is that today we have lots of different legacy systems, disparate records that have been recorded to different standards. And so therefore joining up records across government when we are doing it needs to be done really carefully through mapping, testing, checking.

And so really where that takes us to now, and again the recommendations from the NAO report, is how do we work on moving government to common standards, to be able to move to a world where our systems are more interoperable, where we can connect them more straightforwardly, that the system of APIs that we have in place works much more smoothly. And so I can say a bit more of that's helpful about some of the sort of common standards that we are putting in place.

01:34:18 - 01:34:25

Speaker 58

So it sounds like it's a sort of siloed approach that's happened historically. Is that, is that, is that basic?

01:34:25 - 01:34:28

Susannah Storey

It's been organic growth in different places and now we're trying to be more systematic.

01:34:28 - 01:35:11

Rupert Lowe

I'm quite intrigued, if you're successful in your plan to effectively bring everything together, you're going to be collecting what's known as metadata. So on, which will give you a huge amount of power over the citizens. So once you've connected them, do you plan to collect this metadata? Do you already collect the metadata? And if you do, I guess the questions are who owns it, who retains it, who controls it, and who can access it?

Because again, I think this comes to the trust point, because people will be concerned that the secondary use of this data may not be in their interests. So how are you, are you intending to do that? Have you had any discussions about this? What, what is your plan?

01:35:11 - 01:36:11

Philippa Rouse

So the intention and the plan is definitely not to bring all this data into a single place, but instead very much building on the work that OneLogin have done to create the frameworks and mechanisms for the information to be shared but in secure and well-managed ways that mean that, you know, if two departments are sharing information about an individual then we can be absolutely confident that it's the right individual, that the department is sharing the data with the right department, and with all the kind of cybersecurity and controls in place.

So this is about building the frameworks and mechanisms to do that data sharing safely and securely without the need to create big pools of data, which then, for all the reasons that the committee are concerned about, then risk being a target for all sorts of different issues. So I don't know, Natalie, did you want to build on any of that?

01:36:11 - 01:36:13

Speaker 62

No, not really.

01:36:13 - 01:36:33

Rupert Lowe

I guess the question we all want to know the answer to is whether this is in the interest of the government or the citizens. That's the question, and I think as government's inserted itself into our lives to a greater extent, you could argue this is more in the interest of the government than it is in the interest of the individual. But that's a question which I guess you can't answer.

01:36:33 - 01:36:38

Geoffrey Robert Clifton-Brown

Let's let them answer first and then you can certainly come back in. Does anybody want to...?

01:36:38 - 01:36:40

Speaker 60

I wasn't sure if what the question was.

01:36:40 - 01:36:51

Rupert Lowe

I said I wonder whether this initiative isn't because the state needs this more than the individuals who pay their taxes need it. That's the question.

01:36:51 - 01:37:03

Susannah Storey

I mean, from everything I've seen coming to this portfolio, it is really about trying to create good convenient services for people. So that's what I've seen so far, and I think that's our position.

01:37:03 - 01:37:06

Speaker 59

Convenience often costs money. Yeah. Anyway.

01:37:06 - 01:37:08

Speaker 61

James, do you want to come in?

01:37:08 - 01:38:00

Chinyelu Susan Onwurah

Just to sort of put a point of clarification, that, you know, it is really important and I totally support the ambition to create good convenient services, and I know that lots of my constituents want that. I think the point that has been made about metadata is that whereas the data about, you know, your driving licence, your age, your address, we've agreed is the citizen's data and they should have control over it. The metadata, which would be, you know, when did they apply for a driving licence, or did they apply for a driving licence at the same time as their son was, you know, in another part of the country, or, you know, that the data around that, you know, who, you know, are there plans in terms of, you know, whether that will be stored with the underlying data and are there ownership and responsibility guidelines associated with retrospective metadata?

01:38:00 - 01:39:33

Speaker 16

With pleasure. It's absolutely the right question, and we will make sure that as we define the strategy and policy that we share everything with the committee. And just to back up what Susannah has said, fundamentally the connections we are making in government digital services is around convenience and is around people getting what they need quicker and easier. And context is really important, but it's the context of the individual in that process. And fundamentally it's where they are now and what they want to do next.

And so the way we are approaching it is if you, for example, have just had a baby, you are deciding what to do next and what you might need to do on the journey going forward, whether that's you've just found out and you're going to get your maternity rights all the way through to deciding you're going back to work. At the moment that's quite tricky, and you need to decide as you go and you need to ask many, many questions. What we are doing is thinking about journeys like that where we can say if the individual was in control and the individual could ask more questions, we could make decisions quickly. And that may involve HMRC, parts of they may know something, and the DWP may know something else, but the individual is in the middle of that and is saying, right, okay, I need to proceed to the next step, I'm therefore allowing DWP, for example, to see HMRC's data. And that is the approach we are taking, and that, you know, the people you've got in front of you today, that's our day job is to make sure that we're doing that on behalf of the citizen.

01:39:33 - 01:39:42

Speaker 63

Any other questions from any committee members? I've got one or two, but... We've still got 11 to 12 to do. Oh, question 12, sorry. 11.

Yeah.

01:39:42 - 01:40:06

Matt Tame

So, hello, I wanted to talk a little bit more about digital wallets. So I was just having a little look through mine to see what information I have stored in it, and it's mostly tickets, it's flight pass, bank details obviously so I can pay for things and stuff like that. I just wondered if you could tell us a little bit about what the digital wallet credentials can do that traditional sign-in systems are not able to.

01:40:06 - 01:42:19

Natalie Jones

Certainly. So, your the gov.uk wallet will work an awful lot like the one that's got your club card in and your passes. So government credentials go in a government wallet, again secured by one login. The advantage is that often government gives you a piece of information somewhere that you need somewhere else. So take a disclosure and barring certificate, you might do it because it's part of your job, but you might also coach a grassroots football team at the weekend.

And actually being able to demonstrate that credential, show it on your wallet and have the club secretary scan it means that there are no bits of paper or PDFs which are easy to fake and easy to lose. So if you start to think about the sorts of questions that government asks, so if you're in receipt of benefits for example, it enables you to get free prescriptions, it enables you to access a food bank. So being able to demonstrate that in a really secure way. The other advantage with verified credentials aside from they're harder to fake is that actually from on the flip side, when they're out of date they can be revoked. So if you're entitled to benefits on a Monday but not by a Friday, your benefits credential will move into the expired section and that's what happens with your old train tickets, it's still there you can see it, but you can no longer use it.

So it provides those mechanisms that enable government to make it really, really up to date. Similarly, there's no lag time between being granted a benefit and the credential arriving, it could be literally minutes. So one of the things that the veterans have said about the veterans card, which is the only credential that's currently live and was has been a really great learning experience for us, is that it takes six weeks for their physical veterans card to arrive through the post, but their digital version they can download five minutes after they complete the application form and start using. So again, it's, it's quicker and they don't have to remember to take it with them because generally speaking they've got their phone at the point in which they realize. So none of that, oh no, I've left the letter at home, or a drawer full of important documents as we call them in my household, things that you might need to refer to later.

01:42:19 - 01:42:27

Speaker 38

Actually it can all be on your phone completely within your control, so nobody else can see them or access them without sort of biometric controls that are on your phone.

01:42:27 - 01:42:40

Speaker 65

Um, yeah thank you, that's interesting and funnily enough most of the stuff when I was looking at was of course in an expired section of the wallet, which meant that, you know, it's effectively revoked, isn't it as you're talking about. So, good, thank you very much.

01:42:40 - 01:42:42

Speaker 64

Thank you Matt. Clive next please.

01:42:42 - 01:43:15

Clive Betts

Well, we all want to get closer to the European Union, don't we? Yes, I do. I'm just saying. So, the EU is developing, probably quite ahead of the game compared with most parts of the world, their their own identity wallet, digital identity wallet. What talks are we having with them, given that, you know, many people from this country go to the EU on holiday and probably going to be required to produce things like their driving license that.

So are we looking to something that's going to be compatible so we don't have two completely separate systems that don't work together anyway?

01:43:15 - 01:43:33

Natalie Jones

So I'll start the answer and then hand over to Rod. So from a technical perspective, the wallet has been built to all the same protocols as the European wallet. So there is no technical barrier to integration, that's not the same thing as saying that all European countries will accept our driving license and I'll get Rod to explain why not.

01:43:28 - 01:45:16

Rod Latham

So it is definitely something that we are keen to do is have international interoperability. That would be good for the, again, to give choice to the citizen. At the moment we're still sort of relatively early in the journey both for ourselves and for the EU. And you know, they've got kind of deadlines coming by the end of this year for what they'll be rolling out. So it's still sort of at quite an early stage to be able to kind of work out exactly the timeframe and how the process might run on interoperability specifically with the EU.

Thank you Natalie.

We have lots of connections into the EU, so we talk to them about what they're doing and explain what we're doing. We go to various different kind of events and things that they have, one of which is coming up later this month. International standards is the sort of the route to getting that technical kind of degree of interoperability. And so the fact that international standards underpin what we're putting into the trust framework and into the gov.uk wallet and what the EU will be doing on their side. But interoperability won't be just about the technical challenge of it.

There's also then that kind of wider wrapper that we need to look at on privacy, security, and governance and controls. And so there will be further work that we'll have to do to be able to be assured and to assure the EU that they can have confidence in the system that we've got or we can have confidence in the system that they've got. So it's an endpoint that we want to get to. We're having those conversations and we're trying to work on international standards to make sure that we're kind of going down the right path. But it's something that I think will take a little while.

01:45:16 - 01:45:42

Clive Betts

Beyond IT sideways, you mentioned interoperability and we've talked a bit about age verification and young people want to prove they're 18 when they go for a drink. But many of those young people do go abroad as well. So are they going to be able to show their digital ID in a bar in Spain or the Canary Islands or wherever and have it recognized?

01:45:42 - 01:46:11

Rod Latham

That is where I'd like to get us to and that is what interoperability would mean. And then that means again you don't, you know, if you are on holiday in a European country you don't have to take your passport out with you. There'll be ways, there'll be lots of advantages in being able to do that digitally. As I say, we're not, it will just take a period of time to be able to get there because it is going to be quite complicated and we and the EU are at a relatively early stage in that journey.

01:46:11 - 01:46:24

Clive Betts

Is there any chance that we might be able to shorten the queues at the EU with their new passport controls?

01:46:24 - 01:46:27

Speaker 67

That's not within DCMS. I'm not sure I could comment on that.

01:46:27 - 01:46:39

Clive Betts

Is that even being considered? Because it is a digital problem, because I mean that's what their systems are now and they're really challenging for people and they are making it very difficult, I have to say.

01:46:39 - 01:46:47

Speaker 70

You mean the checks they're doing on the EU side? Yeah, I don't know, I'm afraid, where we are on that. I think the Home Office, we'd have to take that away with the Home Office. Yeah, apologies.

01:46:47 - 01:46:51

Speaker 66

That's part of it, yeah.

01:46:51 - 01:46:52

Matt, Truss would like to come in.

01:46:52 - 01:46:55

Speaker 69

Sorry, Clive, have you finished?

01:46:55 - 01:46:58

Speaker 68

I think so. I think I've been told it's somebody else.

01:46:58 - 01:47:22

John Tristan Osborne

Just a serious question if I may. So I know you've answered some of these questions in the round, but how long do you think it will take to actually create a digital ID strategy? Have you got any sort of dates either principally in the diary in terms of when you expect to publish? Are you at the stage now where you're engaging with the ministers? What's the sort of timeframes here for this to be enacted?

01:47:22 - 01:47:37

Susannah Storey

We don't have a timetable, but we are engaging with the ministers. And I think one of the things that was so useful about the NAO report is all of the things it gives us to go through, so we do want to make sure that we have time to do that. But I don't want to today commit to a timeframe because I don't know what it will be.

01:47:37 - 01:47:47

John Tristan Osborne

So are you expecting, I mean again you're not committing to a timetable, but that's kind of an open-ended answer. You're expecting within this Parliament? Or is that me putting words in your mouth?

01:47:48 - 01:48:31

John Tristan Osborne

Okay, that's fine. I will move on. The next question is, when this is published, how will you prioritize what are you seeking to do first? Obviously, we don't have that in front of us, so, but there's clearly competing demands here. From a volume perspective, it would be DWP.

And that would also pose questions from a digital accessibility perspective, as many of those people are probably the ones that might require support getting access. Young people, obviously, we've mentioned driver's licenses, though that's not exclusively young people, but also other services. How would we balance the competing priorities? Would that be within the strategy in terms of what you seek to do first?

01:48:31 - 01:48:55

Susannah Storey

I think it's helpful if we differentiate, as we've been trying to do earlier, between the work that's already in train on gov.uk One Login, and I'm sure the team can talk a bit about that and what they're prioritizing because they're already in those conversations. And I think the same on the trust framework, where they've done the work already on alcohol, as Rod was saying, and then there are other things in train. So is it, should we do a bit of that in case that gives you a sense?

01:48:55 - 01:48:57

Speaker 73

Yes, that would be helpful.

01:48:57 - 01:49:32

Natalie Jones

So I could start with One Login. So One Login has been rolling five years, one on the front of 264 services out of a total universe of what we estimate to be 500. The number of digital services government runs isn't a static number. And so our priority is to get to the point where One Login enables you to access all 500, which we think will be within the next 18 to 24 months. So that's the priority for One Login, is to get to the point where genuinely, to access any central service, you have one username and one password.

01:49:32 - 01:49:41

Speaker 74

And from a wallet perspective, our next priority is the digital driving license, and we're in conversations with ministers about what our priority will be after that.

01:49:41 - 01:50:10

Speaker 16

And we set out in the digital blueprint, which was published last January, that we would look at digital credentials over between now and 2027. We've publicly said we'll do the driving license, and we're working with departments now on the most important credentials to do next. But that was within the existing strategy. So any additional bills that we go onto in the new strategy, they will happen anyway. So the work we're doing on credentials, with credentials you already have, that work will continue.

01:50:10 - 01:51:16

Rod Latham

Yeah, thanks. To add on my side, so we've already got the Data Act that sets out a number of different requirements that we have to kind of now do, and we're in the process of rolling those out. So I think that's a kind of like in terms of the near term and what we're going to do. So we need to issue a code of practice to turn on the information gateway, which allows sharing between public authorities and the digital verification services, and that will be coming shortly. And as I'd set out in answer to a previous question, there's things around working out who we can best partner with around driving adoption in different use cases.

And tobacco and vapes and knives and crossbows and property are some of the ones that are on the horizon. And then looking at how we can get this system, which is still very, we've only just done the first version, full version one of the trust framework. So we're required to update that every year. So we'll be kind of engaging with stakeholders working out what do we need to change, what's working, what's the, what are the areas. So I think we've got some things from the Data Act that tell us what we have to do next, and that gives us a little bit of a roadmap, I think, through.

01:51:16 - 01:52:19

John Tristan Osborne

Just my last question, if I may. Thank you very much for those responses. Government IT services are very decentralized into each department. Clearly there's a, I understand it has been moved into DSIT and this functionality. Is there a, in terms of the wiring of government question, given the move in the future now where there's a public expectations about digital accessibility, and I know my colleagues have raised this, and also given around cybersecurity concerns and others, do we think the current model of management around this project, in the sense it's been passed to your department, I appreciate this might be a loaded question, but do we think that model of management is right?

Or do we think that perhaps it should have its own, that government IT perhaps should be more centralized into, into one function rather than having it bitty in each department? I know that's a, probably an open, again, it's a very open-ended question, but my worry is, is in a business this would be a function of a programme within an IT team which would fall into, report into a head of operations say, whereas in government it seems to be it's handed to a department who's managing this and they're trying to link in with other departments who've got other priorities.

01:52:19 - 01:53:21

Susannah Storey

No, I, I do appreciate the point you're making. So the, when the machinery of government change happened, DCMS has absorbed the Government Digital Service, but it keeps all of its approach to working with all the other departments that it had before. And that's why, as I was saying earlier, it's really important that we have this ability through the Digital ExCo to work with all of the others because it does need to be coherent. I think there is some benefit that we've seen already actually of having the Government Digital Service in DCMS because with our wider work on digital and tech, for example last week we, I was with the Secretary of State when we met, I think it was Microsoft and Google, and we were able to talk about some of the policy things but also some of the operational work around things like cloud. So there is a kind of benefit of being in the digital department, but it's really vital that we continue this close working with all of the relevant departments so that we can make sure, as colleagues have been saying, on the common areas we can have best practice and standards.

01:53:21 - 01:53:24

Speaker 75

And so that's, that's the way we're trying to organize it.

01:53:24 - 01:53:32

Geoffrey Robert Clifton-Brown

Okay. Thank you. Um, if nobody's got any further questions, I've got about three or four quick-fire questions. Uh, yes, go on then.

01:53:32 - 01:54:39

Chinyelu Susan Onwurah

I just on this point particularly, and thank you very much for your indulgence. So the, um, the Science, Innovation and Technology Committee last summer, I think it was, looked at the, um, the big, uh, data, uh, leak, um, from the Ministry of Defence and, uh, which, which was horrendous. And as part of that we took a look at some of the practices across government when it came to digital and data hygiene. And what we found was that, you know, there's no, each department effectively can do what it wants, you know, when it comes, you talked about building systems for their own reasons etc., but each department, you know, there, there, it can do what it wants when it comes to, um, what digital or data guidelines, you know, how big files it allows to be, um, forwarded or all, you know, but all the different aspects of data hygiene. So, so I'm just trying to understand how you can ensure a high level of data quality, and talk about the interoperability and all the great things you talked, you were talking about in your response to Tristan, if you've got no ability to set any standards.

01:54:39 - 01:55:17

Susannah Storey

Yeah. I mean, I think there are obviously legal standards and then, um, I know in your, um, really helpful report that we've responded to, there were 33 different recommendations and you've got as one of your building blocks, haven't you, information and data. And we have set out some of the things that we're seeking to do there. So our Government Chief Data Officer, um, who sits in GDS, is, uh, doing various bits of work about a strategic data roadmap, um, and making sure that we've got, um, you know, the various information we need. So we are seeking to make sure that there's a clear framework within which all the departments work.

01:55:17 - 01:55:23

Speaker 76

But you're right, there is a degree of autonomy for each individual vertical department.

01:55:23 - 01:55:30

Chinyelu Susan Onwurah

So, so there's no, so you're agreeing with me that there's no ability to, uh, impose high standards or require high standards on the department.

01:55:30 - 01:55:56

Susannah Storey

I mean, I think there's an appetite from departments to have high standards. And certainly when I talk to my colleagues, they're really focused, as we were saying earlier, on their worrying about cyber risks. They want to address their legacy problems. They want to make sure they're adhering to the data obligations. So there's a kind of a pull from the departments for wanting to adopt best practice.

And then we're trying to ensure we're setting out that best practice. But you might want to add on data, Philippa.

01:55:56 - 01:56:33

Philippa Rouse

Yes, I mean, I think you've covered it all, Permanent Secretary. I mean, the Data Standards Authority that sits within the Chief Data Officer's remit has recently worked with a whole range of departments, which I could list, but anyway, to produce things like standards for how information about people is stored and captured. They've also been doing a lot of work on a data asset management policy, so requiring each department to actually map out and set out what they're doing to improve data quality. And so I think there's a lot of work going on.

01:56:33 - 01:56:38

Speaker 77

Let me ask the question a different way. Will you name and shame departments that don't meet your standards?

01:56:38 - 01:56:54

Susannah Storey

Sometimes nudging can help, can't it? I mean, I'm nearly three months into the role and I'm really keen to work with colleagues and think a bit about what we do. Where is it mandatory, where is it not? So if it's okay, I'll come back to you on that.

01:56:54 - 01:58:35

Geoffrey Robert Clifton-Brown

Any other questions? Thank you. I slightly want to follow that question as one of my questions. It does seem to me that government departments are buying systems almost on a daily basis. And unless you start... I'm not advocating a digital ID system, but unless you start somewhere on common standards, it's going to take you years to get proper interoperability.

So it could be from the simplest thing. Philippa raised figure seven on page 18 of the NAO report. That is a brilliant table of illustrating a complicated problem very simply. So unless you started to introduce common standards of inputting into all government systems, you're never going to get total interoperability. And it seems to me that what you need is, even if you allow departments autonomy in buying their systems, you need to have compatible software so that one part of the system can talk to another part of the system.

I was with a GP practice the other day that was tearing its hairs out because the GPs couldn't communicate through their systems with the specialists in the hospitals. They were having to email each other. And then the poor GPs at the end were having to manually summarize that particular episode for the patient records, which it should be done digitally and then it can be summarized by AI. So there's got to be some form of government mandation on standards, surely.

01:58:35 - 01:59:19

Susannah Storey

I mean, I think we want to improve the coordination and the standardization. And that is why our Chief Data Officer is doing this work, as Philippa says, looking at the standards for data. But separately also, we are doing work on the Digital Commercial Centre of Excellence to think a bit about things like cloud procurement and not getting vendor lock-in. And then we're also thinking about the work on legacy. So we're trying on each of these areas where we know there are common problems to work on the best practice solutions, where we can standardize, where is it helpful for government to act as one big customer, even if there's then a call-off to different departments, so we can use our purchasing power.

01:59:19 - 01:59:31

Speaker 78

Because I mean, some of the numbers that I've read in the blueprint, they're absolutely enormous in terms of obviously the government spend across these areas. And I know that this committee and the Science and Tech Committee has been very front-foot on wanting more clarity on that.

01:59:31 - 01:59:50

Geoffrey Robert Clifton-Brown

With respect, quite a lot of thought is being given to cyber attacks and quite a lot of thought is being given to data lock-in in relation to the cloud, but not so much at least government sort of mandation in departments like the Department of Health so that one department at least can procure systems that communicate with each other.

01:59:50 - 02:00:04

Susannah Storey

Well, I think, so as I say, what we're trying to do is make sure there are frameworks and standardization so that departments can get those benefits where it makes sense. And we have not mandated them, so that's a sort of...

02:00:04 - 02:00:17

Geoffrey Robert Clifton-Brown

Maybe the fact that they haven't managed to do it maybe does indicate, and the Department of Health will never be totally efficient, and I'm coming onto productivity in a minute, unless it has all the systems can talk to all the other systems. It just won't.

02:00:17 - 02:00:28

Susannah Storey

I'm more than happy to talk to Sam Jones about specifically what she's doing. And as I say, I'm certain that her team will be connected with our team on these various areas across legacy IT, cyber, and data.

02:00:28 - 02:01:26

Geoffrey Robert Clifton-Brown

We'll leave that for now. I then want to come on to, I've talked about efficiency gains, and just to see where we are on efficiency gains, where you are from IT. Now, Dame Chi has helpfully put a WhatsApp on our system saying that they received a Minister of Government brief published in January, which found that over 45 billion pounds a year, representing 4 to 7 percent of public sector spend in unrealized savings. Now, that proved to be unrealistic, but the 2025 spending review did expect departments to deliver almost 14 and a half billions of efficiency gains by 28-29. Now, I imagine a lot of these efficiency gains are going to come from digital improvements.

Can you enlighten us on what government's efficiency target gains are and how much are going to be gained by digital?

02:01:26 - 02:02:07

Susannah Storey

Each department as part of the last spending review has got efficiency targets, and that's a matter for each department individually. I think the Science and Tech Committee has asked for a splitting out of digital money separately, and that is something that we have found hard to do. So at this stage, we're saying that it's difficult to disaggregate reliably. So I can't give you a specific number on digital, but I have already talked to the Treasury about the next spending review, and we want to make sure we've got a good program of work with them looking across the piece. So very happy to come back to you on that after that.

02:02:07 - 02:02:11

Speaker 79

So we can expect this in the next spending review, some form of...

02:02:11 - 02:02:23

Susannah Storey

I'm sure there'll be focus from the Treasury on what are the savings overall, and then specifically from transformation projects around digital and IT, what savings might come in that place as well.

02:02:23 - 02:02:25

Speaker 80

Productivity gains from IT.

02:02:26 - 02:02:38

Geoffrey Robert Clifton-Brown

Okay, well we'll have to wait till the spending review for that, I suppose. And then finally, we can't have a hearing like this without talking about digital exclusion. Who wants to speak to that and what you're doing about all of that?

02:02:38 - 02:04:15

Speaker 16

Yeah, with pleasure. We've talked about the 9 percent number quite often today, and that number sort only tells you people that can't readily prove who they are. The number we would quote is more like 20 percent, and that number is mixed up of people who find it hard to use digital services. They may be speaking in a different language, they may have no digital skills, and importantly, really importantly, they may be acting on behalf of somebody else, and so they can't get through the barriers, whether they're acting on behalf of a loved one or parent or child. And so it's quite an amorphous mass of folk that all need help.

We look at this in a few ways. There's an inclusion program that has moved into DSIT, and we can happily bring forward the sort of recommendations that they're working on at the moment.

We then think about it as inclusion for digital products, so what we can do within GDS to help it make it easier for people to get what they need from the state. And then we're thinking what we can do with routes that aren't digital. And so as an example, if you want a OneLogin account, you can get that from a post office in the country, you can present yourself at a post office and you'll get help from somebody there. And so what we want to try and do is think about inclusion at all levels and we're trying to sort of bring up, make it possible for everybody to get what they need from a, from a point of view of access to digital services. And if they can't, what are the other routes that they may need in order to get what they need from the state.

So that's the broad view of what we're doing on it and each of those has a sort detailed plan that we can happily share with, with, with you at a later date. Did you have any builds on it?

02:04:15 - 02:04:17

Speaker 81

No, I think I've got nothing, thank you.

02:04:17 - 02:04:33

Geoffrey Robert Clifton-Brown

So for those people that don't and can't or don't want to be digitally connected, will there always be an alternative route that they can obtain the government service that they want?

02:04:33 - 02:04:49

Speaker 16

The current, you can always go to a service and get it. We, you can make a phone call, if you needed to get a OneLogin so you could access digital services, you can do that at the post offices. If you want to apply for something, you could call a call centre. So there are always alternative routes.

02:04:49 - 02:05:14

Geoffrey Robert Clifton-Brown

Finally, I hope the call centre's not going to be like the civil service pension scheme, which took people at the height of the disunity an hour and a half, and even the HMRC who's got considerably better, we've had hearings on this committee where there've been far too long and unacceptable waits. Will you make sure that when you are designing these phone systems as an alternative to the digital systems that they will be within a tolerable wait?

02:05:14 - 02:05:28

Speaker 16

We always need to think about the call centre route. OneLogin does have a call centre, so we do operate a call centre within, in GDS and we've got good benchmarking about how that centre's performing, Natalie, haven't we, which we could share with committee.

02:05:28 - 02:08:38

Natalie Jones

Would you like me to explain a little bit more about the specifics of how OneLogin caters for people without? So, so OneLogin works tirelessly to improve our levels of inclusion year on year on year and we measure that. So we run a number of different channels. So the most popular way to prove your identity is exactly as set out in the NAO report, you use a phone, you check your passport or your driving licence and people, you know, digitally literate people with photo ID tend to sail straight through that route. But if you haven't got a mobile phone or you don't have photo ID we have alternatives.

So if you haven't got any photo ID we've got a web channel where we, the original route enabled you to check your national insurance number with HMRC and then answer knowledge-based verification questions. So they're questions that only you should know the answer to. And the original data set was a commercial data set. The challenge with that is that people who don't have cars and take foreign holidays quite often don't have a financial footprint. So we introduced knowledge-based verification questions using DWP benefits data because those people do tend to have a data footprint there.

And next year we're bringing in open banking. So we estimate that about 85% plus of the 9% of people without photo ID do have a bank account and so the open banking model we're hoping will increase the inclusion from that angle. For people who don't have mobile phones, there's a web route. For people who have low digital literacy, you start the journey on OneLogin and as Chris says, you then go to the post office and they will support you through the process. We also have specific guidance written for helpers.

So if you are elderly and you've nipped next door to their neighbour or you're a grandparent with a child, actually there's specific instructions like hold the phone like this, this is how it works, you know, check these documents. And then we have more traditional user support. So we have frequently asked questions, chatbots and then we have a call centre.

And it's the only call centre that I'm aware of in government that's designed to help you exactly the moment you need it. So they don't have access to all your personal data, so there's no privacy impact, but they've got a mock-up of the tech. So if you say to them, "I can see this button, I'm pressing here, it's not working," somebody can talk you through the process. And if all of that doesn't work, we have a specialist casework function for people who get truly stuck for one reason or another. So we try and make it as sort of multi-channel as possible to interact with people with different forms of exclusion that sometimes can be overlapping.

And we will continue to build on that. So every module we put live, we evaluate in terms of, "Is this actually moving the needle on the thing we intended it to do, and how can we move the needle further?" And so we will continue to iterate the service in subsequent years to push that inclusion further and further. And as a prerequisite for going live with One Login, services must maintain an alternative channel. So no identity verification service can ever be 100%, because if you're 100%, you're letting the fraudsters in as well.

So there's always going to be a set of people for whom either it's not the right channel or they can't make it through, and they need to be able to access services as well. So before they're allowed to go live with One Login, they have to demonstrate that they've got an alternative route. And so we will maintain those over time.

02:08:38 - 02:09:27

Geoffrey Robert Clifton-Brown

It sounds as though you're doing things that perhaps other parts of government may want to look at what you're doing. So, yeah, that's, that sounds very good. Can I thank you all very much today, and I'm sorry about the slightly disjointed hearing, which was slightly, partly due to parliamentary votes and partly due to technical problems, believe it or not. But thank you all very much. It's much appreciated you giving us evidence on this subject.

I am sure that digital and AI is something we are going to return many times to on this committee, because we attach a great deal of importance to it. So an uncorrected version of the transcript will be available in the coming days, whereafter we will produce a report, no doubt with recommendations, and we hope you will study those very carefully. And we look forward to seeing you in the future. Thank you very much, all of you.