The Indian state needs a better way to handle exceptions

An Indian citizen applying for a pension, correcting a land record or seeking a municipal certificate encounters the state as a sequence of small decisions. Is the document acceptable? Does the name match? Who can correct the entry? When will the application move? Constitutional commitments and budget allocations matter enormously. But their practical value often depends on whether someone at a counter—or behind a portal—can answer these questions.

India has spent considerable administrative energy digitising this encounter. Applications can increasingly be submitted remotely, payments made electronically and progress tracked online. These are real improvements. Yet putting a procedure on a screen does not necessarily make it intelligible, fair or capable of dealing with complications. The next frontier of reform is less glamorous than another platform: building a state that knows what to do when the standard process fails.

The citizen who does not fit the form

Most public-service workflows assume a reasonably orderly life. Names are spelt consistently. Addresses remain current. Documents agree with one another. Applicants possess the required proof and can obtain whatever is missing. These assumptions simplify administration. They also create predictable difficulty in a country where people migrate, households divide, property changes hands informally and older records may be incomplete.

Consider a hypothetical pension applicant whose name differs slightly between two official records. A clerk may recognise that both documents refer to the same person but lack authority to accept the discrepancy. A portal may reject the application without explaining which department must correct it first. Each institution can defend its own procedure while the citizen remains trapped between them. No spectacular misconduct is necessary. Ordinary fragmentation is enough.

Standardisation nevertheless has a strong justification. Clear requirements can reduce arbitrary demands, make decisions more consistent and limit opportunities for rent-seeking. The answer is not unrestricted discretion at every desk. It is structured discretion: explicit rules for common exceptions, documented reasons for departures and a review mechanism that can distinguish reasonable accommodation from favouritism. Administrative consistency should mean treating comparable circumstances comparably, not pretending that every circumstance is identical.

Digitisation needs an administrative owner

Digital systems work best when the underlying service has been simplified. Otherwise, they can preserve every old approval while adding new requirements for uploading, authentication and data matching. An applicant may gain an online acknowledgement but still need an offline visit to discover why nothing has happened. The visible interface improves; the distribution of authority behind it remains untouched.

The crucial question is therefore not simply whether a service is online. It is whether someone owns the outcome. For each frequently used service, a department should identify an office responsible for the case from receipt to a reasoned decision. That office need not perform every verification itself. It must, however, be able to seek information internally, identify the source of delay and tell the applicant what happens next. Coordination should be an administrative task, not unpaid work assigned to citizens.

This also requires distinguishing between information the state already holds and information it genuinely needs from the applicant. Departments should not repeatedly demand the same evidence merely because their systems do not communicate. But data sharing is not an automatic remedy. Access should be limited to a defined purpose, recorded and protected. A mistaken entry should not acquire greater authority simply because several databases reproduce it.

Every digital service also needs an assisted route. Help at a local office or service centre should form part of the service itself, with clear fees where applicable and receipts for payments. Citizens should not have to surrender passwords or depend on an informal intermediary to complete a public procedure. Convenience for confident users and accessibility for everyone else are complementary goals.

Measure resolution, not just disposal

Administrative dashboards favour what is easy to count: applications received, certificates issued, complaints closed and average processing time. These measures are useful, but incomplete. A complaint can be closed with a message advising the citizen to approach another office. An application can be rejected quickly because a document is missing. Both actions may improve reported performance without resolving the underlying problem.

A better scorecard would follow the citizen’s journey. How many visits were required? How often was an application returned for correction? What share of decisions was overturned on review? How long did difficult cases take, rather than only the average case? Departments should also examine applications that were started but never completed. Some abandonment reflects changed intentions; some reveals a process that applicants could not navigate.

India already has institutional foundations to build upon. Several states have enacted public-service delivery laws that specify timelines and provide appeal mechanisms for notified services. The Right to Information framework offers another route to scrutiny. These arrangements do not guarantee effective implementation, but they demonstrate that timeliness, reasons and accountability need not be treated as optional courtesies.

Measurement must avoid creating a new incentive to reject complicated applications. Reporting should separate approval, justified rejection, requests for additional information and unresolved cases. Small, independently checked samples can test whether recorded outcomes match citizens’ experience. Publishing aggregate results can support scrutiny without exposing personal details. The objective is not a perfect dashboard. It is a more truthful account of what the administration has actually delivered.

Give the frontline authority and support

Calls for accountability often settle on the employee nearest the citizen. Sometimes that is justified. But a frontline worker may be administering several schemes, using unreliable equipment and awaiting approval from an office with little reason to prioritise the case. Holding that worker responsible for every delay obscures the design of the system. Responsibility must follow actual authority.

Routine, low-risk corrections should therefore be delegated under clear rules. More consequential decisions—particularly those affecting property, eligibility or substantial public expenditure—may require additional verification. The appropriate balance depends on the service. What matters is that the distinction is deliberate. Requiring senior approval for every minor discrepancy does not eliminate risk; it can merely turn supervisory scarcity into a queue.

Training should be organised around recurring cases rather than only new circulars or software demonstrations. A district office could maintain an updated guide to common discrepancies, acceptable alternative evidence and escalation routes. Decisions on recurring problems should inform that guide, so each applicant does not trigger the same interpretive exercise. This would preserve institutional knowledge when personnel change.

Capacity also has a cost. Assisted counters, competent supervision and reliable maintenance require recurring expenditure, not just a technology procurement budget. Departments should assess workload before adding deadlines or launching another grievance channel. A promise of faster service becomes credible only when staffing, authority and operating resources support it. Otherwise, reform risks becoming another reporting obligation for offices that are already stretched.

Make correction part of the service

A usable appeal is essential because neither officials nor software will always get decisions right. Rejection notices should explain the substantive reason, the evidence relied upon and the route to review. The reviewing authority must be able to change the outcome, not merely forward the complaint to the original desk. Escalation without corrective power is correspondence disguised as accountability.

Reform should begin with a limited set of high-volume services in willing states, districts and urban local bodies. Teams could map the most common failure points, remove redundant requirements and test exception-handling rules before wider adoption. Evaluation should compare processing time, repeat visits, error rates and administrative costs. Local variation is useful here: different staffing arrangements and settlement patterns may require different delivery models, even where the entitlement is the same.

The larger principle is straightforward. Citizens should not need personal connections, exceptional persistence or technical fluency to obtain an ordinary administrative decision. India’s state will become more capable not only by executing standard transactions at scale, but by handling departures from the standard fairly. The decisive test of public service is what happens after the easy workflow ends.