Over the last few months we’ve been investigating how GOV.UK Verify might be extended to local authorities. We recently kicked off our first pilot projects on concessionary travel and parking permit services.
A lot of local authorities, including many of our pilot participants, work directly with suppliers to provide aspects of their services. We want to collaborate with these suppliers and understand how industry can get involved in local authority reuse. In this blog we’ll share how we’ve been doing this, what we’ve found and what’s happening next.
On Monday 3 October we held a workshop jointly hosted with techUK for a range of local authority suppliers. Our aims were to:
- inform suppliers of our plans for extending GOV.UK Verify to local authorities
- understand their needs from GOV.UK Verify
- identify potential opportunities for product development and future market engagement
What we did
We issued open invitations to suppliers via techUK and the Local Digital Coalition and asked our contacts in local government to spread the word. In the end, we had 60 attendees representing 45 suppliers, who between them provide services to hundreds of local authorities.
We knew from feedback we received prior to the event that the attendees’ levels of knowledge about GOV.UK Verify varied a lot, so we spent the first part of the afternoon introducing the service and its architecture. We then went on to introduce our plan for the local authority pilots and explain how we engage with the private sector, through OIXUK, in a transparent and open way.
We were pleased to have Mark Harvey from GSMA, the trade association for the mobile industry, talk to us about his experience of working with GOV.UK Verify on the Mobile Connect project, which was coordinated by OIXUK. He explained how, through OIXUK, he worked across mobile network operators to allow users to sign into online services in a simple and safe way.
For the second half of the afternoon, we ran an ‘unconference’. This means that, rather than prescribing a fixed programme of events, we arranged the suppliers into interest groups and let them direct discussions about the topics that were most important to them, for example service components. Given the variety of suppliers in attendance, this was a good way of making sure we met their diverse needs without making any assumptions in advance.
What we found
The workshops provided lively discussion between suppliers.
These were some of our main findings:
- there is a clear appetite from suppliers of digital services to local authorities to integrate GOV.UK Verify with their services. They are keen to get involved in discoveries or alphas and would like to have access to a ‘sandbox’ environment (i.e. a testing environment), which would allow them to experiment with integrating GOV.UK Verify.
- suppliers had questions around the commercial model and they highlighted the high cost of change based solely on the integration of digital identity assurance. They noted that ‘attribute exchange’ would help to justify the investment needed for integration. This means the consensual exchange of relevant data (e.g. age) which could be used to check a user’s eligibility for a service (e.g. concessionary travel).
- many suppliers expressed an interest in using GOV.UK Verify with ‘reuse accounts’ i.e. the single account that gives users access to a number of local authority services with the same credentials. They also mentioned a number of specific services which they believed would benefit from GOV.UK Verify, including social care, council tax and licensing. We’re working with local authorities to explore the transformation of such services, starting with a discovery event on reuse accounts on 26 October.
- there is demand from suppliers for a project integration of supplier matching engines with the GDS Matching service adapter. This could test integration, the matching data payload and hub matching orchestration, but it would not require live use data nor study the best methods of undertaking matching within commercial products.
What happens next
We closed the day by talking about the next steps. There were four main propositions that came out of the day. These were:
- the supply of components (e.g. a hub) to local authorities
- explore how best to allow suppliers to experiment with integrating GOV.UK Verify
- the integration of GOV.UK Verify into a service
- the supply of data into the identity ecosystem for user verification
The main route to engage on all four is through the OIX process or, in the case of services, by engaging through the local authorities who signed up for our pilots. This would allow us to collaborate on discoveries or alphas that address these three propositions directly. You can read more about how OIX projects are run on their project process webpages.
Any suppliers who are interested in proposing an OIX project or participating in a potential ‘sandbox’ environment that allows them to test their proposition through an OIX Alpha should email email@example.com.
We will continue to share the progress of our local authority pilot projects openly on this blog and the Local Digital Coalition website.
If you've used GOV.UK Verify and would like to provide feedback or contact us for support, please submit a user support request.