Why Every Digital Service Should Be Measured by Completion Rate

Many government digital services are measured against a launch date. A portal goes live, and the project is considered a success. What happens afterward (whether residents can actually move through the process) can often go untracked.

That gap reflects a deeper assumption: that launching a digital service is the same as delivering one. However, a service is only truly delivered when a resident can move through it from start to finish, without hitting a wall, switching channels, or giving up. Launch puts the tool in front of people. Delivery means it actually works for them. The distance between those two things becomes visible in completion rates.

The Number That Tells the Truth

Completion rate is the percentage of residents who start a digital service and finish it without abandoning, getting stuck, or needing to switch to a phone call or in-person visit.

It may be the most revealing metric in government service delivery because it captures several things at once: the quality of the user experience, the integrity of the underlying data, and the soundness of the process design. A service with strong adoption but a 40% completion rate still has work to do. High traffic without high completion often means the friction has shifted further into the process, where it's less visible but no less real for the people experiencing it.

As What “Digital Transformation” Really Means for Government makes clear, surface-level changes (new portals, mobile forms, updated branding) don't deliver lasting modernization on their own. A fresh interface can make a process look modern while the same friction points persist underneath. Completion rate is the metric that looks past the surface and measures whether residents can actually get through.

Why Completion Rates Are Low

The good news is that low completion rates tend to follow familiar patterns. The same friction points appear across agencies, program types, and states, and because they're recognizable, they're addressable. In most cases, they trace back to infrastructure. Below are a few examples of common friction points.

The form asks for information people don't have on hand

A resident sits down to apply for a benefit or permit. Halfway through, the form asks for a document number they don't have memorized, a tax figure buried in last year's records, or an account identifier from a letter they received months ago. Without that information at hand, most people close the tab and don't come back.

This is where verified data at intake makes a difference. If an agency already has the information it's asking for, the resident shouldn't need to supply it again. Credential-based intake, built on standards like ISO 18013 and W3C Verifiable Credentials, can confirm identity and fill in known fields automatically. That means fewer questions residents have to answer from memory, and fewer reasons to abandon the process.

Document uploads fail silently

File upload fields are among the most common abandonment points in government digital services. Residents run into file-size limits that aren't communicated upfront, format restrictions that reject readable documents, and upload interfaces that sometimes fail without explanation. Many don't realize the upload didn't go through. They submit and wait, or they give up.

The path forward is structured, validated intake: clear file requirements surfaced before the upload attempt, real-time feedback when something doesn't meet specifications, and, at times, integrating verifiable digital credentials that remove the need for manual file handling altogether.

Sessions time out, and progress is lost

A resident spends twenty minutes working through a complex application, carefully entering information, uploading documents, and moving step by step through the process. Then the session times out. The form clears, and the work they've done disappears. They're left starting over or trying to reach someone by phone to recover their progress.

This kind of experience is discouraging, but the solutions are well within reach. Sessions that save progress as a resident goes, authenticated pathways that let them pick up where they left off, and shorter flows that don't require completing everything in one sitting - these are structural improvements that agencies can layer into existing services without rebuilding from the ground up.

The digital flow still requires a phone call to complete

Some processes appear to be fully online, but in practice, they still depend on manual steps. A resident fills out a form, submits it, and then receives a notice telling them they need to call to confirm their identity, provide additional documentation, or complete something the portal wasn't built to handle. What started as a digital experience ends with a phone call or an office visit.

This pattern is among the most expensive to maintain for agencies and residents alike. It reduces the efficiency gains that digital services are meant to deliver, and it often reflects a process that was moved online without being fully rethought.

Moving Beyond "Launch = Success"

A go-live date is a useful project management milestone. But it isn't a measure of service quality, and it works best when treated as a starting point rather than an endpoint.

How to Measure Digital Transformation Success with Verifiable Digital Credentials: KPIs Beyond 'Go Live' makes the case for tracking resident-facing outcomes across the full service lifecycle. Not just whether the system is online, but whether it's working for the people who use it. Completion rate clearly expresses that principle. It can be benchmarked, trended, and improved, and it naturally draws attention to the parts of the process where residents get stuck.

What Completion Rate Actually Measures

There's a reason completion rates can be uncomfortable to confront: a low number often points to decisions made before the portal ever launched. It reflects the form design, the data model, the intake process, and the identity verification approach, all at once.

That's also what makes it the right metric. As Designing Digital Services People Actually Complete explains, completion is a systems outcome. When a resident drops off, it's not simply a UX issue in isolation. It's a signal that the service design, the data infrastructure, or the process logic encountered a breakdown at that point. Improving the interface without addressing the data and process underneath it is unlikely to move the number.

This is why treating completion rate as a primary metric shifts the investments agencies make. When go-live is the goal, investment tends to concentrate in the visible front-end layer. When completion rate is the goal, investment follows the actual drop-off points, which are almost always rooted in data, identity, or process design.

Residents deserve services that work the first time. Agencies that measure whether they do (and act on what they find) are better positioned to deliver on that promise.

The Agencies That Will Lead

Agencies that set completion rate targets before launch, track where residents drop off, and use that data to guide ongoing improvements are well-positioned to deliver strong outcomes over time. The benefits show up across the board - in shorter backlogs, fewer errors, lower support volume, and deeper resident trust.

When case processing times improve, it's because the infrastructure underneath the experience has been strengthened, not just the surface of the form. Trusted identity at intake, reduced form burden through credential reuse, and structured data flows that simplify manual steps all contribute to services that residents can actually complete.

Completion rate is a metric that reveals how well a digital service is truly working. The technology to improve it is available now, and agencies that start measuring it will be better equipped to deliver services residents can rely on. That progress builds over time, and the best moment to begin is before the next portal goes live.

If you're ready to explore what completion-driven infrastructure looks like for your agency, get in touch with SpruceID.

About SpruceID: SpruceID builds digital trust infrastructure for government. We help states and cities modernize identity, security, and service delivery — from digital wallets and SSO to fraud prevention and workflow optimization. Our standards-based technology and public-sector expertise ensure every project advances a more secure, interoperable, and citizen-centric digital future.