Your client hasn't had drinking water in three weeks. The municipality says the pipe is old, the contractor vanished, and nobody's in charge. So you draft a PIL—a Public Interest Litigation petition asking the court to step in and fix it. Sounds reasonable, right? The court sits there with the power to order the state. Why shouldn't it?
Because, increasingly, it won't. And the Karnataka High Court's recent sharp rebuke to state inaction—"courts can't be mulcted with managing drinking water and building bridges"—signals something important: judges are drawing a clearer boundary between ordering accountability and running the show. That shift changes how you should counsel clients when they want judicial intervention in state failure.
The Line Courts Are Drawing: Accountability vs. Micromanagement
Here's the distinction judges are now making. A court can tell the state: "Your water department must publish a repair schedule by next Friday." It can demand why the superintendent of engineers hasn't filed an affidavit. It can pull up the collector for sitting idle on a ₹50 lakh bridge project.
What a court increasingly won't do is appoint itself the de facto chief engineer. It won't say: "Contractor A is better than Contractor B—award the tender to A." It won't monitor daily progress. It won't step into decisions that need real-time technical expertise, budgeting calls, or political trade-offs among competing infrastructure needs across a district.
Why? Because judges aren't trained in hydrology or construction scheduling. They don't have the staff or institutional bandwidth. And the moment a court does, it has crossed from judicial review—checking whether the state acted lawfully—into judicial governance—acting like the state itself.
The Karnataka court made this visceral: courts can slam inaction. They can't become the infrastructure ministry.
What Changed: The Shift From "We'll Oversee It" to "You Own It"
Ten, fifteen years ago, PIL benches were readier to assume quasi-administrative roles. A court would direct detailed monitoring, appoint amici curiae (friends of the court) to inspect sites, set monthly review dates, and effectively supervise implementation. The idea was that if the state wouldn't act, judicial muscle could push it forward.
But courts have learned three hard lessons:
- It doesn't actually fix things. A court order saying "repair the water main by June 15" doesn't find the contractor, unblock budgets, or remove a district official's incompetence. The order sits there; the water doesn't flow.
- It clogs the judicial docket. When judges become project managers, they have less time for actual trials. Criminal cases pile up. Civil disputes wait years. The system atrophies.
- It creates perverse politics. State officials know a court order can shield them from voter anger. They stop feeling accountable and start blaming the judge. "The court won't let us hire that contractor." Responsibility evaporates.
So courts are now saying: We'll hold you accountable for your decisions. We won't make the decisions for you.
What This Means for Your PIL Practice Right Now
If you're advising a client on a potential PIL, the old playbook no longer works:
Old approach: "Let's file a PIL asking the court to supervise the entire water project. They'll appoint a monitor, hold monthly hearings, and make sure it gets done."
New approach: "Let's file a PIL asking the court to order the state to: publish a timeline, explain delays in writing, and report every 60 days. If they miss those deadlines, we come back to court with contempt charges."
The second one works because it doesn't ask the judge to do the job—it asks the judge to keep score on whether the state is doing it.
Here's what matters now:
- Specificity, not open-endedness. Don't ask for "immediate repair of the water pipeline." Ask for "the state must submit an engineer's survey within 10 days, followed by a tendering timeline within 20 days, with weekly progress updates posted on the municipal website."
- Measurable milestones, not court-run projects. The state owns the project. You ask the court to verify the state is meeting its own stated milestones. The court doesn't pick the contractor; it checks whether the state's own process was fair.
- Contempt as the consequence, not court orders as the solution. A PIL that succeeds today is one where the state misses court-set deadlines and contempt powers kick in. That's painful for the collector—far more so than a vague "improve water supply" order.
- Exit strategy. Don't structure your PIL to need eternal court supervision. Phrase it so that compliance = case closed. "Once the state publishes the repair schedule and meets it for six consecutive months, this petition stands disposed." That's clean. That works.
The Hard Conversation With Your Client
When a client comes to you with a PIL idea, they're often angry and exhausted. The system has failed them. They want a judge to make it right. That's a human, legitimate feeling.
But you now need to be honest about what a PIL can and can't do:
"A court can order the state to explain itself, to meet deadlines, and to answer for delays. But a court can't become your water department. The goal isn't to make the judge your project manager—it's to make the state accountable enough that it fixes the problem itself, or you can cite contempt. That takes longer, and it's less satisfying. But it's what works now."
If your client says, "I just want this fixed, I don't care about accountability," that's a sign a PIL might not be the right tool. They might need to lobby the municipal election, file a Right to Information request to expose who's responsible, or take the story to a journalist. Sometimes court is part of the answer; sometimes it isn't.
When a PIL Still Makes Sense
Don't misread this. PILs aren't dead. They work when:
- The state has broken a law (like dumping untreated sewage, which violates the Bharatiya Nyaya Sanhita and Environmental Protection Act). You're not asking the court to build a treatment plant; you're asking it to order the state to stop breaking the law—and report compliance.
- The state is sitting on a decision it's already supposed to make (e.g., a municipal corporation approved a repair budget six months ago, and nothing's happened). You ask the court to order the superintendent to explain why and execute it within a set period.
- A vulnerable group is systematically harmed (children without schooling, women denied government shelter, homeless people denied food during a heat wave). Courts will act because it involves constitutional rights, not just efficiency.
- The issue is eminently justiciable—meaning a court can actually measure success. "Did the state conduct a caste census?" Yes or no. "Did it publish the results?" Yes or no. Not "Is our water system perfect?"—which is vague and never truly achieved.
The Takeaway for Your Clients
Courts are stepping back not because they've stopped caring—but because they've learned that real change happens when executives feel accountable, not when judges run things. A PIL that extracts a written, court-enforced timeline and public progress reports is often more powerful than one that asks the judge to micromanage.
When you're counseling a client frustrated by state inaction, the message is this: We can make them answer. We can't make them competent. But making them answer—in writing, under oath, with consequences for contempt—often works better than you'd think.
And if it doesn't, at least you've built a public record of who failed and why. That's useful ammunition for the next election.
Found this useful? Share it.