Apply for duplicate log book (V5C) beta assessment report

May 2024 · 10 minute read

Service description

This service enables registered vehicle keepers to apply for a duplicate V5C registration document (log book) via an online channel as opposed to the current paper (form V62) and telephone processes. The information provided will be used to issue a replacement V5C to the registered keeper when the original has been lost, stolen or destroyed or when the vehicle has been involved in an accident and has been identified as Category S salvage. There are no changes to the legal requirements and the service is being built under the current regulations that require the registered vehicle keeper to be in possession of a V5C registration document (log book) for the vehicle on which they are recorded.

Service users

This service is for a keeper of a vehicle who needs to apply for a duplicate copy of their V5C registration certificate (log book) in compliance with the law.

1. Understand users and their needs

Decision

The service met point 1 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

2. Solve a whole problem for users

Decision

The service met point 2 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

3. Provide a joined-up experience across all channels

Decision

The service met point 3 of the Standard.

What the team has done well

The panel was impressed that:

4. Make the service simple to use

Decision

The service met point 4 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

5. Make sure everyone can use the service

Decision

The service met point 5 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

6. Have a multidisciplinary team

Decision

The service met point 6 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

7. Use agile ways of working

Decision

The service met point 7 of the Standard.

What the team has done well

The panel was impressed that:

8. Iterate and improve frequently

Decision

The service met point 8 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

9. Create a secure service which protects users’ privacy

Decision

The service met point 9 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

10. Define what success looks like and publish performance data

Decision

The service met point 10 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

Decision

The service met point 11 of the Standard.

What the team has done well

The panel was impressed that:

12. Make new source code open

Decision

The service met point 12 of the Standard.

What the team has done well

The panel was impressed that:

What the team needs to explore

Before their next assessment, the team needs to:

13. Use and contribute to open standards, common components and patterns

Decision

The service met point 13 of the Standard.

What the team has done well

The panel was impressed that:

14. Operate a reliable service

Decision

The service met point 14 of the Standard.

What the team has done well

The panel was impressed that:

ncG1vNJzZmirY2Ourq3ZqKWar6NjsLC5jq2fnp%2Bfq7Kzusyepa2rka7AbrLIpZysZ5Oku7Wxza1manBjZH55f5Fsb25mmKm6rQ%3D%3D