Government service clerk — tasks, one by one

Taking the application

This step is a checklist against a published rule, and every item on it exists in a database somebody already runs. It is also the step policy explicitly targets: the State Council's 2022 opinion requires cross-provincial services to run through the national integrated platform, with the names, codes and legal bases of listed items standardised nationwide by mid-2023, and pushes mutual recognition of electronic certificates — which removes the document the counter used to check.

A policy requiring adoption is not a measurement of adoption, which is why this site weights a mandate cautiously. It says nothing about how many counters actually closed, nothing about the share of applicants who complete online, and nothing about markets without a national platform. Implementation evidence would be a deployment record, not another policy document.

Checking it against the rule

Where the rule is explicit and the data is structured, a system applies it more consistently than a person at the end of a long queue. What does not transfer is the judgement a written rule leaves open on purpose — most administrative rules have a margin, and the margin is where citizens with unusual circumstances live.

Says nothing about whether the margin is used well: consistent application of a bad rule produces consistent harm, and discretion at a counter is also where unequal treatment lives. Neither has been measured publicly.

The case the form was not written for

A system can only refuse what does not fit; it cannot decide that the rule should bend, or find the other route through. This is also the case where the state's legitimacy is actually tested — a citizen who cannot get a document they are entitled to does not experience it as a software limitation.

A judgement about where the work sits, not a measurement of how many cases are exceptions. It also does not claim counters handle exceptions well — being told to come back with a document you cannot obtain is the ordinary experience of this failure.

The person who cannot use the app

Every policy that moves services online creates this category, and the same policies say so: the 2022 opinion requires online and offline channels to be deeply integrated rather than the counter simply closing. So the counter survives specifically for the people the platform does not reach — which makes this task a consequence of automation rather than a survivor of it.

It establishes that the category exists and that policy acknowledges it, not how many counters are actually kept open for it or how well they are staffed. Where a service closes its counter anyway, this task does not become human-led; it stops being done.

Getting departments to move together

The platform moves the data; it does not settle whose rule wins when two agencies disagree about what a resident is. That is negotiation between institutions, and it is exactly what the 'one thing, done once' policies are asking for and exactly the part a platform cannot supply.

Nothing here says who does this coordination today, and in many places nobody is assigned to: the citizen does it, by visiting four counters. That is the failure this task describes, not evidence against it.

Answering for what the platform decided

New work created by moving services onto a platform. An administrative decision carries a right to reasons and a route to challenge it in most systems, and those attach to the agency regardless of what produced the decision. Somebody local has to be able to say why this application failed — and when the reason is inside a shared national system, that is harder than when it was a form on a desk.

New work appearing is not new headcount, and how such challenges are actually handled is not published by any administration this page covers. It also does not establish that a reason is actually available — in several systems the answer a counter can give is the same code the applicant already saw.