Select Page

Completion rate

Your service’s completion rate is the number of digital transactions that your users complete as a percentage of all digital transactions that your users start.

This includes transactions where the user receives support from someone to use the digital service (called ‘assisted digital support’).

Calculating completion rate

To calculate your completion rate:

  1. Count the number of completed transactions – the numerator.
  2. Divide it by the total number of transactions (including partially completed or failed ones) – the denominator.
  3. Show the result as a percentage.

Make sure you count only genuine users, ie. you need to exclude internal users, test users and web robots from your data.

What to include as a transaction

A transaction is an exchange of:

  • money
  • information
  • permission
  • goods or services

Transactions on your service will have clearly defined start and end points. They will also result in a change to a system, eg someone’s personal information or the details of an interaction are stored in a register or database.

The following activities don’t have clearly defined start and end points and are not recorded in a government system, so they are not transactions:

  • general advice or enquiries
  • informal complaints
  • visits to websites

When a transaction is completed

A transaction is completed when someone finishes the task that your digital service provides. For example, when a user:

  • submits an application
  • submits a service request
  • makes a payment
  • makes a booking

The service should tell the user that the transaction is complete with a confirmation or ‘thank you’ message.

A user’s application doesn’t have to be successful for you to consider the transaction complete.

For example, the Apply for a procurement exemption is considered complete when the user has submitted an application, regardless of whether the application is successful.

When a transaction has failed

A failed transaction is when a user gives up before reaching a defined end page (often called a ‘confirmation page’). This includes when a user abandons the service from an error page.

Measure from the start of a transaction

Most services will have a start page, this should be the only way to access the service. You should usually only consider a transaction to have started when the user continues from your service’s start page.

Make sure users can’t bypass the start page via links or search engine results.

Some services don’t have a start page. In these cases it helps to understand the whole user journey so you can identify the exact points at which the user starts the service.

Counting users who ‘save and return’

If your service allows users to save a transaction and finish it later, make sure you can match transaction starts to their subsequent completions.

Services with both digital and non-digital steps

For legal reasons, some services require users to carry out steps digitally and non-digitally, for example starting and finishing a transaction online, but sending a paper copy of a form in the middle.

To measure the 2 parts of the service as a whole is complicated. Users complete the second part of the service much later, which can lead to misleading completion rates. You can resolve this in analytics.

However, if your service doesn’t need to match the 2 digital parts of the user journey, you can treat them as separate transactions and measure completion rates for each.

Completion rate through each service phase


In discovery, explore any data from legacy and offline systems.

You should consider:

  • the data that’s available
  • where you can get the data, eg an existing online service, a digital database that supports an existing offline service, contact centre data, search terms in web analytics
  • whether you can calculate completion rates from these to use as a baseline


In alpha, start work on your performance framework. In the framework, specify the user journeys you’ll measure, including start and end points for them.


In beta, map all possible user journeys through your service. You won’t be able to measure completion rates until your service goes into public beta.

Record data to the Performance team

You must measure your completion rate data and share it the Performance team.