LO
Get told when a verified record lands on this occupation → · Mark which of these tasks are yours (VOLO Pro, free) → · For a team or a graduating class →
Government service clerk
Stands between a citizen and a rule — checking that an application is complete, and dealing with the person whose situation the form was not written for.
Count how many applicants last week were told to come back with something. Then check how many of those came back at all.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Written for front-line government service staff — the counter, the call line, the online back office — who take and check applications against published rules. It is not about the civil service as a whole: policy work, inspection, enforcement and public safety are different jobs with very different exposure. The rules and the pace of digitisation differ enormously by country, and this page is written mainly against mainland China and Singapore, where a national platform is the stated policy.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Each tile is one task. Its size is how much of the job it is; its colour is where the task is heading. Click a tile to see what the judgement does not establish.
A policy requiring adoption is not a measurement of adoption, which is why this site weights a mandate cautiously. The one implementation figure here is Singapore's ministry stating in 2021 that its target of 90–95% of government transactions completed digitally end to end had been met — an assertion, not an audited statistic; for China's platform nothing here shows how many counters closed or what share of applicants complete online.
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.
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.
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.
China's State Council now requires every bundled service to name a lead department and say who does what — but that assigns the work to departments, not to the counter, and nothing here measures whether the lead department actually settles disputes. Where it does not, the citizen still does the coordinating by visiting four counters, which is the failure this task describes.
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.
Is this your job? Say so and this page narrows to your share of it.
A job title is a bundle of tasks bought together, and no two people hold the same bundle. Nothing is sent anywhere — it stays in this browser.
Read all 6 tasks in full — direction, reasoning and limits →
Recent changes#
South Korea. Article 2(4)(ja) puts decisions by state bodies on eligibility, entitlement and charging for public services inside the definition of high-impact AI; Article 34(1) then requires a provider using such a system to run a risk-management plan, to be able to explain the result and the main criteria behind it, to protect users, to keep documentation — and, item 4, to place the system under human management and supervision. Read the verbs: Article 34 is a duty (shall implement, with the detail left to Presidential Decree), while the fundamental-rights impact assessment in Article 35(1) is only a best-efforts obligation (shall endeavour), and Article 35(2) merely tells state bodies to give priority to assessed products. So the hard requirement is supervision and explainability, not assessment. The Decree fixing the detail is where the real burden will be set and is not in this text. Nothing here says how many counter posts exist or what a clerk does; it fixes what may not be decided by a machine alone.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
A State Council opinion on bundling related government services into single 'one thing' services. It requires each bundled service to name a lead department and supporting departments with their respective duties, strengthening cross-department coordination of policy, business, systems and data sharing; it also requires an online and offline assisted-service system with defined staffing, duties and service content, including accompanied and proxy service for the elderly and people with disabilities. Coordination is assigned to departments, not to named clerks, and the opinion does not measure how well it works.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
The Australian Government's response to the Royal Commission into the Robodebt Scheme, an automated debt-raising programme, quoting each recommendation and the government's answer. It accepts recommendation 11.3: the benefits agency's processes should require staff to engage with a recipient before removing a vulnerability indicator from their file, and should remove any feature allowing such an indicator to expire automatically. It also accepts in principle that more face-to-face support should be available for vulnerable recipients, and accepts considering a legal framework for automated decisions with a clear path to review. The verbs in the recommendations are 'should'; this is the government's response, not the commission's report, which scripts could not retrieve.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Mainland China, issued by the State Council General Office. It requires adoption and sets a deadline for standardising the names, codes and legal bases of listed cross-provincial items; it also pushes mutual recognition of commonly used electronic certificates and adds 22 items in its annex. It is a requirement, not a report of what happened: it says nothing about how many counters closed, what share of applicants complete online, or staffing. The same document requires online and offline channels to be deeply integrated rather than counters closing.
Regulation, subsidy or public procurement is requiring or funding adoption — the mirror of a constraint. It shows adoption is being required, not that it has happened, so one mandate is never enough on its own; two independent ones are.
A State Council opinion addressed to provincial governments and ministries. It says services should be provided online and offline in parallel; that for services already available online an offline counter should in principle also be provided, with people choosing the channel; that people applying offline must not be required to book or submit materials online first; that assisted-service windows should serve the elderly and people with disabilities; and that a window for matters that cannot otherwise be handled should provide a fallback for difficult and complex cases. It sets the requirement, not how many counters exist or how well they work; 'in principle' leaves room for exceptions.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Singapore only, and it is the ministry's own assertion that a target was met — the answer does not publish what counts as a transaction, which agencies are in scope, or how it was measured, so the figure is a policy statement rather than an audited statistic. Note the date above all: May 2021, before generative AI existed as a public tool. What moved the routine counter transaction online in this market was ordinary digital government — forms, national identity, pre-filled data — and it had largely happened already. That matters for how the rest of this page reads: the open question for this occupation is not whether the routine application leaves the counter, but what happens to the cases that could not.
An employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
What this means for you#
The visible half of this job — taking an application and checking it is complete — is the half a national policy is explicitly moving onto a platform, with deadlines. What remains at a counter is the exception and the person the platform cannot reach, and both are harder than the routine work, not easier. If you are choosing this path for stability, look at what your local service centre is being measured on this year.
This occupation is unusual on this site: the automation is required rather than chosen, and the same policies that require it also require the counter to stay open for people the platform does not reach. That is a real protection and a narrow one — it protects the function, not the number of people performing it, and it protects it only where the policy is actually implemented that way.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
Own the exceptions counter
Routine intake is what policy is moving onto the platform. The applicant whose case has no box, and the one who cannot use the app, are what the counter is explicitly being kept for.
It is the harder work with the same pay, and in many services it is not a named role — you would be absorbing it rather than being assigned it.
Count how many applicants last week were told to come back with something. Then check how many of those came back at all.
Be the one who can say why the system refused
As decisions move into a shared platform, the right to reasons does not move with them — it stays with the agency. Someone has to be able to reconstruct a refusal, and in most services nobody can.
It requires access to how the platform actually decides, which front-line staff usually do not have.
Take one online rejection and try to explain it from the record alone. Note where you have to phone someone.
Move to the side that designs the service
The people writing the item lists and the forms rarely watch someone fail to complete them. Having stood at the counter is the qualification that side is short of.
It is a different kind of institution to work inside, and the distance from the applicant is the point of the job and also its cost.
Take the item your counter gets the most repeat visits for, and read its published requirement as if you were the applicant.
Common questions#
Unusually for this site, the direction is written down in policy rather than inferred from company behaviour: a national platform, standardised item lists with deadlines, and mutual recognition of electronic certificates. What the same policy also says is that online and offline channels must be integrated rather than the counter closing. A signal you can check yourself: what share of your counter's visits last month were people who had already tried online and could not finish. That number is what the counter is being kept for.
No, and keeping them separate is the whole method of this site. A policy establishes that adoption is required; it does not establish that it happened, how completely, or what happened to staffing. This site weights that kind of evidence cautiously for exactly that reason — a mandate describes something not yet completed, while a deployment record describes something that has. If you want to know what changed where you work, the number to look for is not in the policy.
Because the policy that moves services online also says the two channels must be integrated, and because of who is left over. Every service that goes online produces a group it does not reach — no smartphone, a name the system cannot render, documents that were destroyed, a situation with no box on the form. Those cases are harder than the routine ones, not easier, and they are the reason an administrative service is judged legitimate or not.
This site does not rate stability and a page that did would be worth less than one that shows you where to look. What it can tell you is the shape: the intake half has a policy with deadlines pointed at it, and the exception half is being kept by policy too, which requires assisted service with defined staffing, duties and service content. Ask what your service centre is measured on this year — if the target is the share of items completed online, that is the direction, stated in the only place it counts.
Studying towards this?
These majors lead here. Their pages break down which of their competencies transfer and what graduates typically lack.
What these judgements rest on#
6 of 6 task judgements on this page are backed by a verified event and 0 are platform inference, each labelled where it appears. Behind them sit 2 technology dimensions, a reconstructed trajectory since language models reached the public, and 6 verified events.
See which technologies, how it got here, and the method →
Where it sits in the official classification: skills, knowledge, related jobs →
Other roles in the same function#
A company divides its work into functions before it divides it into jobs. These sit in Administration alongside this one — a fact about org charts, not a judgement that they are similar or that they are changing in the same direction.
Administrative assistant · Data entry clerk · Receptionist / front desk · Medical coder