Digital Take-up

Digital take-up, in the GOV.UK Service Manual, measures completed digital transactions as a percentage of transactions across all channels in the same period. Assisted digital transactions are included: receiving help does not automatically make a completed digital transaction non-digital. The unit in the calculation is a transaction, not a distinct person. Define the service boundary and completion event so repeated visits or submissions do not silently become extra completed transactions.

Under the Service Manual’s requirements, measurement starts in public beta and data is measured and published monthly. Digital take-up is one of the specified KPIs alongside cost per transaction, user satisfaction, and completion rate. Those requirements belong to that guidance’s application context; another organization must establish its own reporting obligations and useful cadence. Completion rate asks how many attempts finish, whereas take-up compares use across channels.

Channel choice and internal workflow are different measures

A customer can complete an online claim submission while an assessor later processes it in an old application. That can count as a completed digital transaction within the defined submission service without establishing that the insurer’s entire workflow uses its new system. Both old and new applications may be digital. An internal end-to-end workflow measure therefore needs its own eligible cases, start and completion events, and classification of new, mixed, legacy, and unknown paths. Track partial adoption separately where it is informative, and disclose missing observations rather than silently excluding them. Define how a transaction crossing channels is classified and counted once within the reporting scope.

For example, a fictional insurer might report one-third of branches using a new workflow and 34 percent of completed claims following it end to end. The first denominator is branches and the second is claims; neither determines the other because branches handle different volumes. A supported assisted route or approved exception is not automatically a failed adoption. The metric should say what occurred before anyone judges whether the pattern is acceptable.

Use the baseline to review the transition

The Service Manual describes user research in discovery, an available baseline and channel-use model in alpha, and refinement with actual data in beta. The channel-shift plan identifies how users will move and what support they will need. During live operation the plan is reviewed every six months or annually; that is separate from monthly measurement and publication. A plan for an internal migration can borrow this discipline without copying the government metric or its schedule.

Set a target date for retiring redundant routes alongside readiness, access, support, dependency, retention, and recovery conditions. Confirm those conditions before closure and document exceptions or delays. Live for a Year, Used by a Third places these decisions alongside work redesign, skills, competing changes, and benefits. Data product adoption addresses verified consumer uses rather than channel share.

References:

• GOV.UK Service Manual: Measuring digital take-up (Open Government Licence v3.0).
• GOV.UK Service Manual: Using performance data to improve your service: an introduction (Open Government Licence v3.0).
• GOV.UK Service Manual: Data you must publish (Open Government Licence v3.0).