https://gdsdata.blog.gov.uk/share-driving-record-service-assessment/

Share Driving Record - Service Assessment

Share Driving Record is a new service that will provide access to driver data for Third Party users and will act as an enabler for  DVLA to abolish the paper element of the driving licence. The aim of this service is to provide users who currently use the paper part of the driving licence with a new digital version that can be easily accessed. The service will display the information currently available on the paper counterpart and make it available to all those who have a right to see it.

Department / Agency:
DfT/DVLA

Date of Assessment:
7 July 2014

Assessment Stage:
Alpha Review

Result of Assessment:
Pass

Lead Assessor:
A. Newton

Service Manager:
R. Gye

Digital Leader:
B. Etheridge


Assessment Report

The Share Driving Record Service has been reviewed against the 26 points of the Service Standard at the end of the Alpha development.

Outcome of service assessment

After consideration the assessment panel have concluded that the Share Driving Record Service is on track to meet the Digital by Default Service Standard at this early stage of development.

Reasons

It was clear from the assessment that the team are using an agile approach to meeting the user needs for Share Driving Record through prototyping and regular user research. Since this service is being built on the IEP platform, on which the View Driving Record Service is soon to be live, the panel were satisfied that appropriate technology and security choices were being made, and the team have the ability to rapidly iterate the service. The team already have a lot of benchmarking data for a service at alpha stage and are talking to the performance platform about measuring this new service.

Recommendations

For the service to succeed at Beta assessment, during the Alpha it will be vital that the team:

  • work to publish the service’s code openly as soon as possible
  • take action on GDS’s design recommendations made for both ‘View Driving Record’ and ‘Share Driving Record’ (to be provided as a separate document)
  • develop and test the feature which informs users that someone has looked at their driving record
  • ensure that appropriate levels of assisted digital support are in place for the beta, including:
    • demonstrating if there is no assisted digital requirement with sound user research
    • researching the needs of users (including businesses of all sizes and citizens) who cannot use the service independently, to give a full picture of who needs what kind of support
    • Explicit and adequate assisted digital expertise must be either embedded within or available to the team.

do further work to discover whether offering an API would be valuable. It was suggested that an API was desired by customers, but there did not appear to have been much exploration of this. One of the objectives of an alpha should be to validate user needs. An API feels like a new area ripe for discovering whether it is a viable solution for meeting those user needs.


Digital by Default Service Standard criteria

Criteria Passed Criteria Passed
1 Yes 2 Yes
3 Yes 4 Yes
5 Yes 6 Yes
7 Yes 8 Yes
9 Yes 10 Yes
11 Yes 12 Yes
13 Yes 14 Yes
15 Yes 16 Yes
17 Yes 18 Yes
19 Yes 20 Yes
21 Yes 22 Yes
23 Yes 24 Yes
25 Yes 26 Yes