Why 'Completed' Isn't Enough: The User Experience Gap in Digital Government Services

"Completed" Is a Necessary Record, Not the Whole Experience

Systems must record acceptance, review, and issuance nodes; otherwise progress cannot be tracked and responsibility cannot be assigned. However, these states describe what happened in the processing workflow , not whether the user understands the result or can use it in the next step.

For example, after an application is approved, the user may still not know where to collect the electronic credential, whether offline verification is still required, or which entry point to use for follow-up matters. Repeated inquiries at this stage do not necessarily indicate a system failure; they may simply reflect a missing explanation between the case result and the next action.

The 2025 State Council General Office opinion on establishing a normalized mechanism for "efficiently completing one matter" explicitly calls for shifting key items from "can be handled" to "handled well and easily," and requires combining "good-or-bad reviews," "cannot-be-handled" windows, the 12345 hotline, online monitoring, and case data analysis to discover problems. This provides a public basis for observing the gap described above, but it cannot be used to infer that any specific region universally suffers from such issues.

The Second Call Often Reveals Cross-Channel Breakpoints

Imagine a user submits materials online, receives a "completed" notification, then calls the hotline to ask how to use the result. If the hotline can only see the three characters "已办结" (completed), the response easily falls back to "please refer to the platform display"; the user receives only a status, not actionable information to continue.

In this hypothetical flow, there are at least three different kinds of completion:

Business processing completion

Result delivery completion

User task completion

The three are related but cannot be automatically equated. Business processing has legal boundaries and professional judgment; user perception cannot replace a lawful processing conclusion. However, if only the first kind of completion is monitored, the problems of the latter two tend to remain in another hotline or another window.

The 2023 State Council General Office opinion on improving government service effectiveness already proposed linking complaint suggestions, "good-or-bad reviews," 12345, and "cannot-be-handled" feedback windows, and verifying whether bottlenecks are truly resolved through follow-up visits and "look-back" reviews. Cross-channel repeated requests for help are themselves service signals worth reviewing.

More Useful Than "Satisfaction" Is Seeing Where the User Gets Stuck

"Satisfied" and "dissatisfied" can alert service teams, but if only a rating is left, it is hard to know whether the problem lies in result delivery, textual explanation, or follow-up item connection. A follow-up call asking "Are you satisfied with this handling?" may yield only a vague evaluation; if the team can identify whether the user is looking for a credential, asking about scope of applicability, or unable to start the next service, the improvement direction becomes much clearer.

The focus here is not to add unlimited manual follow-up visits for every case. A more feasible observation method is to map signals already present in existing channels— repeat inquiries, result views, subsequent jumps, re-submissions —to specific matters and processing stages, then have business staff verify the causes. This is a product and service analysis based on public documents, not an official unified indicator, nor can a single click datum determine whether the public has "truly completed" the matter . When personal information is involved, corresponding data use and security requirements must also be observed.

The UK Government Digital Service Standard also advocates combining online and offline channel performance data with user research to judge whether a service solves the original problem. It serves as a reference for observation methods, not as an applicable rule for Chinese government services.

After the Page Ends, the Service Should Still Provide One Clear Sentence

If, when the user receives the "completed" result, they can simultaneously understand "what the result is, where to use it, and who to contact if problems arise," many subsequent inquiries could be resolved before they arise. Conversely, a repeated call is also worth treating as product feedback: is the page wording ambiguous, do channels lack shared context, or do the business rules themselves need clearer explanation?

"已办结" (completed) deserves to be retained; it makes the process auditable. But when evaluating digital services, the gaze can move beyond this status to see whether the person handling the affair has already connected to the next step. What deserves continuous observation next is whether different service channels can form a coherent explanation around the same matter, so that users do not have to start over again and again.

Sources and References

State Council General Office Opinion on Establishing a Normalized Mechanism for "Efficiently Completing One Matter" Key Items (Guo Ban Fa [2025] No. 24): verification of expressions on "can be handled" to "handled well and easily," user experience, and multi-channel feedback.

State Council General Office Opinion on Establishing a Normalized Working Mechanism for Government Service Effectiveness Improvement Relying on the National Integrated Government Service Platform (Guo Ban Fa [2023] No. 29): verification of requirements for multi-channel linkage, completion follow-up, and bottleneck re-check.

UK Government Digital Service Standard Item 10: Define Success and Publish Performance Data: used only as a reference for cross-channel evaluation methods, not as a Chinese regulation.