India needs a state that can correct its own mistakes
Digitising applications is not enough. Public services need clear ownership, workable appeals and room to resolve ordinary errors.
The quality of the Indian state is often judged by the scale of its programmes: beneficiaries enrolled, connections provided, certificates issued. These are necessary measures. But a different test reveals how government works in daily life. What happens when an otherwise eligible person’s application fails because two official records spell a name differently?
The answer frequently involves another visit, another document and another instruction to approach a different office. A service may be available online while its correction process remains stubbornly physical. The application travels electronically; the citizen travels by bus.
India’s next administrative reform should therefore be less concerned with adding digital entrances and more concerned with building reliable exits from error. A capable state is not one that never makes mistakes. It is one that can recognise, explain and correct them without making citizens organise their lives around its internal divisions.
The burden hidden inside a service
Administrative performance is usually measured from the department’s side of the counter. How many applications arrived? How many were processed? How many remain pending? These figures say little about what obtaining a service required from the applicant.
For a worker paid by the day, an office visit carries a wage cost. For an elderly pension applicant, it may require a relative’s time and transport. A request to upload a clearer scan sounds trivial until it requires another paid visit to a service centre. Individually modest demands can become a substantial barrier when repeated.
Digitisation can reduce these costs. Online applications, direct payments and searchable records have changed how many Indians interact with government. The mistake is to assume that moving a transaction online automatically removes the administrative burden behind it. Sometimes it merely relocates that burden from a clerk’s desk to a citizen’s phone.
Consider a scholarship application held up by a mismatch between school records, bank details and identity information. Each institution may regard its own database as authoritative. Each correction may depend on another correction happening first. None necessarily owns the task of getting the student through the entire process.
This is not simply poor customer service. It is a coordination failure with distributional consequences. Applicants with money, familiarity or influential contacts can navigate fragmented procedures more easily. Those without them face a higher effective price for the same entitlement. Administrative complexity becomes an unlegislated means of rationing access.
Measure resolution, not digital activity
A dashboard can make an administration more legible to its managers while leaving it opaque to citizens. Counting applications disposed of is especially misleading when disposal includes rejection, transfer or closure without a remedy. An office can improve its numbers without improving anyone’s circumstances.
The central measure should be successful resolution of a legitimate request, accompanied by indicators that expose the effort involved. Departments should track repeat visits, requests for additional documents, applications returned more than once and the time spent between offices. Such measures would not replace expenditure or coverage data. They would explain why those achievements sometimes fail to translate into dependable services.
Service clocks also need honest definitions. A department should not be able to restart the clock whenever it asks for information that could reasonably have been requested at the beginning. Nor should a file cease to count as pending merely because it has moved to another department. Citizens experience elapsed time, not administrative accounting.
India need not invent an entirely new framework. Several states already have laws guaranteeing specified public services within stated timelines, with appeal mechanisms and, in some cases, penalties. Their practical value depends on the services covered, public awareness, staffing and enforcement. The next step is to examine where these arrangements secure remedies, rather than treating notification of a deadline as the reform itself.
Public reporting should distinguish straightforward cases from exceptions. Otherwise, offices handling difficult populations or messy historical records may appear less competent than offices with easier workloads. A useful performance system must reveal obstacles without rewarding avoidance of the people most likely to encounter them.
Give somebody responsibility for the whole problem
Most recurring service failures cross organisational boundaries. A local official may identify the problem but lack permission to amend a record. A technical team may control the software but have no authority to interpret eligibility rules. A grievance office may forward complaints without being able to compel action.
The remedy is not to give every official unlimited discretion. That would create fresh opportunities for arbitrary treatment. Instead, frequently occurring exceptions should have published resolution pathways: who can act, what evidence is acceptable, how long a decision should take and where a refusal can be challenged.
For services involving several departments, one designated office should retain responsibility until the case is resolved. It need not perform every task. It must coordinate them. A citizen should receive a case number that survives transfers, a comprehensible explanation of the blockage and the identity of the authority responsible for the next decision.
Frontline staff need bounded powers to resolve minor discrepancies, supported by recorded reasons and reviewable decisions. A spelling variation should not automatically be treated like a substantive dispute over eligibility. Equally, genuinely contested claims require careful examination. Good administration distinguishes risks instead of imposing the same evidentiary burden on every applicant.
This approach requires investment in people as well as software. Training must cover exception handling, not merely data entry. Supervisors need time to review difficult cases. Where workloads exceed staffing, ambitious deadlines become incentives to reject, defer or conceal. Administrative capacity cannot be downloaded with a new portal.
Make appeals a route to a remedy
A grievance mechanism is valuable only if it can change an outcome. A message stating that a complaint has been forwarded is an acknowledgement, not relief. Repeated forwarding can reproduce the original fragmentation under a different label.
An effective appeal should provide a reasoned decision, access to the evidence used and review by an authority capable of reversing an error. Rejection notices should identify the relevant rule and the specific deficiency. Generic phrases such as “invalid details” tell applicants almost nothing about what to do next.
Appeals must also remain accessible beyond smartphones. Assisted counters, telephone support and authorised representatives matter for people facing literacy, disability, connectivity or language barriers. These channels should feed into the same case-management system. An offline applicant should not enter an inferior administrative queue simply because digital access is difficult.
There is a legitimate concern that easier correction could weaken safeguards against fraud. But rigidity is a poor substitute for verification. Risk-based checks, documented overrides and audits can preserve controls while allowing genuine errors to be fixed. The relevant choice is not between perfect security and effortless access. It is between explicit, reviewable judgement and opaque improvisation.
Departments should analyse overturned decisions and recurring complaints as evidence about process design. If many applicants fail at the same field or document requirement, the problem may lie in the form or rule rather than in the applicants. Appeals should improve the original service, not operate permanently as its expensive second attempt.
Reform the routine before announcing the next platform
A practical starting point would be a small group of high-volume state and municipal services: pensions, scholarships, birth and death certificates, and water connections. Each participating administration could map the most common failure points, identify unnecessary evidence requirements and publish a correction standard alongside its delivery standard.
Pilots should be assessed through independent sample checks, including conversations with unsuccessful applicants. Official records alone cannot reveal people who abandoned a claim or paid an intermediary after repeated failures. Evaluation should ask whether resolution became faster and fairer, not merely whether portal usage increased.
Reform will also require restraint. Linking more databases can spread an error as efficiently as it spreads accurate information. Data sharing should have a defined purpose, appropriate access controls and a clear route to correction. Interoperability is useful only when institutions agree on responsibility as well as technical standards.
The promise is modest but consequential: fewer avoidable visits, clearer decisions and less dependence on personal intervention. For India, administrative reform need not always arrive as a grand restructuring. It can begin with a rule that every unresolved case has an owner, every rejection has a reason and every correctable mistake has a workable remedy.



