There’s a phrase almost every Indian who has ever dealt with a government office has heard: “It’s still under process.”
You hear it when a pension check is late, when a property transfer is stalled, when an income certificate never shows up, or when a complaint about some public service has been gathering dust for weeks. You file your paperwork, get a receipt, and then the waiting starts.
One trip, you’re told the file is with a clerk. Next time, it’s moved to a section officer’s desk. A while later, it’s “pending approval.” Ask when it’ll actually be resolved, and nobody seems to know.
Come back tomorrow. So you do.
It might look like a minor annoyance on its own. But multiply it by millions of citizens, and it reveals something much bigger about how the Indian state thinks about accountability.
When something gets held up in government, who’s actually on the hook for the delay?
India’s administrative system has always leaned heavily on hierarchy, procedure, and rule-following. Files pass through set channels. Every decision needs a note, then a sign-off. Rules spell out who can act and when.
There’s a real reason for that. No government can run purely on individual judgment calls. Rules bring consistency, guard public money, and prevent arbitrary decision-making. In a country as vast and complicated as India, procedural discipline matters. The trouble starts when following the procedure becomes the whole point, instead of a means to an end.
A certificate that takes three months might have gone through every required approval, perfectly in line with protocol. A complaint might get logged, forwarded, and reviewed — and the actual problem might still be sitting there, unsolved.
From the department’s point of view, the file moved.
From the citizen’s point of view, nothing changed.
That gap deserves a lot more attention than it gets.
Still, the answer isn’t to paint bureaucrats as lazy or careless — that story is too easy, and usually wrong.
Government officers work inside a system where every choice can be second-guessed from multiple directions. Rules are often tangled, staffing is thin, responsibilities overlap, and a decision made in good faith can be picked apart years later.
In that kind of environment, it makes sense to play it safe.
If deciding something carries more personal risk than putting it off does, delay becomes the logical move. Passing a file upward feels safer than deciding on it. Asking for “one more clarification” feels safer than using judgment. Waiting on a superior’s sign-off feels safer than being the one who owns the call.
Over time, that builds a culture where playing it procedurally safe gets rewarded more often than taking initiative.
That’s the piece of India’s accountability model that needs to change.
The goal isn’t more oversight — it’s smarter oversight.
First, responsibility needs to be clearer. A citizen shouldn’t have to decode an internal chain of command just to find out who’s handling their case. If something is pending, people deserve to know its current status, who’s responsible next, and roughly when to expect resolution. A published timeline shouldn’t be treated as optional — and when delays are unavoidable, the reason should be stated plainly. That single shift would make administrative delay something you can actually trace back to a source.
Second — and just as important — performance shouldn’t be judged solely on whether the rulebook was followed. It also has to account for whether the outcome was actually achieved. That doesn’t mean scrapping procedural safeguards. It means treating procedure as the tool, not the goal itself.
If a pension gets approved correctly on paper but reaches an elderly person months late, that’s not really a success story. If a grievance gets marked “resolved” in the system while the underlying issue is still unfixed, a closed file isn’t the same thing as a solved problem.
For the person on the other end, this isn’t an abstract distinction. It touches their income, their access to basic services, their property, their job, and sometimes just their dignity.
But shifting toward outcome-based accountability needs a safety net too: officers have to be free to make honest calls without living under constant threat of being punished after the fact. A system that comes down hard on every mistake doesn’t necessarily produce better governance — it might do the opposite. Officers stop wanting to decide anything. Files keep getting bumped upward. Choices get postponed. Responsibility gets spread so thin nobody really holds it.
The end result: a bureaucracy that looks accountable on paper but is functionally stuck.
So there needs to be a real distinction between deliberate wrongdoing, repeated failure to act, and an honest decision that simply didn’t pan out the way anyone hoped. Accountability should build a sense of ownership — not fear.
There’s also a strong case for putting the citizen’s actual experience closer to the center of how government performance gets judged.
Departments already track plenty of data — applications received, disposal rates, targets hit. But numbers can hide more than they reveal. A department might report that it “disposed of” thousands of applications. That’s a data point. It doesn’t tell you whether those cases were handled fairly, resolved in a reasonable time, or whether people had to keep showing up in person to get anything done.
But shifting toward outcome-based accountability needs a safety net too: officers have to be free to make honest calls without living under constant threat of being punished after the fact. A system that comes down hard on every mistake doesn’t necessarily produce better governance — it might do the opposite. Officers stop wanting to decide anything. Files keep getting bumped upward. Choices get postponed. Responsibility gets spread so thin nobody really holds it.
The end result: a bureaucracy that looks accountable on paper but is functionally stuck.
So there needs to be a real distinction between deliberate wrongdoing, repeated failure to act, and an honest decision that simply didn’t pan out the way anyone hoped. Accountability should build a sense of ownership — not fear.
There’s also a strong case for putting the citizen’s actual experience closer to the center of how government performance gets judged.
Departments already track plenty of data — applications received, disposal rates, targets hit. But numbers can hide more than they reveal. A department might report that it “disposed of” thousands of applications. That’s a data point. It doesn’t tell you whether those cases were handled fairly, resolved in a reasonable time, or whether people had to keep showing up in person to get anything done.
Because behind every stalled file is more than paperwork. There’s someone waiting on a pension. A family waiting on a certificate. A farmer waiting on approval. A citizen waiting on an answer.
The system sees a file number. The person sees a piece of their life stuck on pause.
That’s why this conversation needs to move past the old back-and-forth over rules versus discretion. The real question is simpler than that:
Can a government system really call itself accountable if no one is clearly responsible for solving the citizen’s problem?
India’s next model of bureaucracy shouldn’t just ask whether the process was followed correctly. It should also ask whether the process actually delivered what it was meant to.
Because in the end, good governance isn’t just about pushing files through the system correctly — it’s about moving people’s lives forward.
So where should the line actually be drawn? Should officers be judged mainly on how faithfully they stick to procedure — or on whether the citizen’s problem got solved? And if we move toward judging by outcomes, how do we make sure honest officers aren’t punished just for making tough calls?
Most people have run into a government process where the file seemed to move everywhere except toward an actual solution. Has this happened to you? What happened, and what do you think should have gone differently?
@Rohit Manral