GS-42026-07-08

The Warning Nobody Enforced — Accountability and the Duty to Not Cause Harm

Wayanad tunnel debris collapse — accountability of the doer and of the overseer

Accountability & responsibility Indian moral thinkers Strengthening ethical values in governance Case studies on above issues

Section A — Where We Are

Covered so far

So far we have covered 2 concepts across 1 session — Professional Ethics and Conscience (Voice of Conscience), both at Foundation depth, with an introduction to Kant's Duty Ethics. Today is session 2.

What's new today

Two fresh concepts: Accountability and Non-Malfeasance (the duty to not cause harm). Both from scratch. We'll also introduce one thinker — Kautilya — on the question of punishing negligent officials. Nothing from the Day 1 ledger is being repeated; we're adding new tools to the toolkit.

Section B — Today's Anchor

"Contractor's failure to remove debris led to tragedy, says CM" — The Hindu, 8 July 2026

At a tunnel construction site in Wayanad, Kerala, a massive pile of excavated mud — left uncleared despite repeated government warnings — collapsed during monsoon rains, killing three migrant workers and leaving five missing. The Chief Minister called it a disaster caused by "human error, abandonment of safety precautions, and sheer negligence." The district administration had issued an ultimatum to the contractor on June 20. The Public Works Minister had personally flagged the danger. The contractor — Dilip Buildcon Limited — claimed compliance with all safety protocols. The dead workers — Chandra Bahn from Madhya Pradesh, Bikash Kumar from Bihar, Anmol from Jharkhand — were migrants, far from home.

This is not just a governance failure story. It is an ethics question because people died not from an act of nature, but from a decision — or more precisely, from a non-decision. Someone chose not to act. Someone chose not to remove the mud. Someone chose not to enforce the warning. And three families in three different states will never be the same.

Section C — Let's Understand: Accountability

Picture this. You're in school. The teacher steps out for five minutes and tells the class monitor: "Keep things in order." The monitor nods. The teacher leaves. Within two minutes, three boys are throwing chalk at each other. A girl's glasses break. When the teacher returns and asks the monitor what happened, the monitor says, "I told them to stop." The teacher's response? "I didn't ask you to tell them. I asked you to keep things in order. You were responsible."

That exchange — small, everyday, unremarkable — is the seed of accountability.

Accountability means that when you are given a responsibility, you don't just hold the title — you own the outcome. If things go right, you were the one in charge. If things go wrong, you were still the one in charge. You can't claim credit for one and dodge the other. The class monitor cannot say, "I did my job — I told them to behave." If the classroom descended into chaos on their watch, the monitor is answerable. Not because they threw the chalk. But because it was their duty to prevent the chalk-throwing, and they didn't do enough.

Now let's move from the classroom to the real world — to Wayanad.

The Wayanad district administration told the contractor to clear the excavated mud by June 20. The Public Works Minister raised the alarm in a stakeholders' meeting. The District Disaster Management Authority flagged it formally. These are not vague suggestions over tea — these are official warnings from empowered authorities, documented and timestamped. The contractor didn't act. The mud stayed. The rains came. Three people died.

Here's the accountability question that matters: who is answerable?

The contractor, obviously — they ignored a direct order. But accountability doesn't stop at the most visible person. What about the officials who issued the warning on June 20 but didn't follow up when it wasn't complied with? An ultimatum without enforcement is just a letter. If you send a warning and then go back to your desk and wait, and someone dies in the interval — can you really say, "But I warned them"? That is the monitor saying, "But I told them to stop."

This is why accountability in public administration has two faces. There's the accountability of the doer — the person or entity that was supposed to act (the contractor, in this case). And there's the accountability of the overseer — the government official whose job is to ensure that the doer actually does their job. A District Collector who issues a warning but doesn't set up a mechanism to verify compliance is, in a meaningful ethical sense, partially accountable too. Not for the negligence itself, but for the gap between warning and follow-through.

Why does a civil servant need to understand accountability? Because a civil servant's entire career is built on delegated trust. The people of India cannot personally monitor every road, every hospital, every school, every construction site. They trust their elected representatives and appointed officers to do it for them. When an IAS officer signs off on a safety clearance, they're not filling a form — they're telling 140 crore people: "I checked. It's safe." If it turns out they didn't check, or they checked but didn't follow up, they have broken a trust that no apology can restore.

Accountability is not punishment. Accountability is the other side of the coin called authority. You cannot have one without the other.

Consider the elevated corridor case study that UPSC itself framed in 2021 — an inspecting team notices a crack in a pier, the Chief Engineer overrules them, the project manager is squeezed between truth and hierarchy. The ethical core of that case is accountability: who will answer if the bridge collapses? The officer who raised the red flag, or the one who ordered it to be ignored?

In Wayanad, the same architecture of failure played out in real life. And the people who paid the price were the ones with the least power — migrant labourers from Madhya Pradesh, Bihar, and Jharkhand, thousands of kilometres from home, with no union, no political patron, and no one to speak for them after they're gone.

Section D — Non-Malfeasance: The Duty to Not Cause Harm

This section is part of the full analysis.

2 more sections below are locked too.

Upgrade to Basic to read

Section E — Thinker Link: Kautilya on the Accountability of Officials

Section F — Mains PYQ Bridge

PYQ 2014Explain10 marks · 150 words

What does 'accountability' mean in the context of public service? What measures can be adopted to ensure individual and collective accountability of public servants?

How to approach

This question is tailor-made for today's learning. Define accountability using the authority-accountability coin framework: accountability is not punishment, it is the other side of authority, and you cannot hold one without the other. Then use the Wayanad example to show that accountability operates at TWO levels — the doer (the contractor who ignored the June 20 ultimatum) and the overseer (the officials who issued the warning but never closed the enforcement loop). For measures, distinguish individual mechanisms (performance appraisal, disciplinary proceedings, citizen's charters, RTI) from collective ones (social audit, parliamentary oversight, judicial review). Close with Kautilya's insight from the Arthashastra: systems don't enforce themselves — if officials know there is no consequence for inaction, inaction becomes the default.

Source: UPSC Mains GS4, 2014, Q7

PYQ 2021Examine20 marks · 250 words

An elevated corridor case study — an inspecting team notices a crack in a pier, and the Chief Engineer overrules them. What are the ethical dilemmas involved, and what are the consequences of overlooking the inspecting team's observations?

How to approach

Today's concepts are directly applicable. The project manager's dilemma is a NON-MALFEASANCE question: if you stay silent and the bridge collapses, you have violated the duty to not cause harm — and the fact that you did not personally build the faulty pier does not absolve you, because you had the knowledge and the standing to prevent the harm. The ACCOUNTABILITY analysis then asks who bears the moral weight — the one who noticed the crack, or the one who overruled them? Argue both: the Chief Engineer bears primary accountability as the decision-maker, but the project manager who acquiesces becomes complicit in a foreseeable harm. Bring in Kautilya's prayoga: knowing the risk and failing to act on it is as culpable as causing the damage.

Source: UPSC Mains GS4, 2021, Case Study 3

PYQ 2022Discuss10 marks · 150 words

A whistle-blower reports corruption and illegal activities. What policy measures would you suggest to strengthen the protection mechanism to safeguard the whistle-blower?

How to approach

Today's framework helps you see the whistle-blower as the person trying to ENFORCE accountability when the system has failed to enforce it on itself. The Wayanad officials who flagged the danger were doing something structurally similar — raising an alarm within the system. The ethical failure happened not because nobody spoke, but because the alarm was never followed by action. Whistle-blower protection, seen in this light, is about making sure accountability loops are CLOSED, not merely opened. Measures: strengthen the Whistle Blowers Protection Act, 2014 (still largely unoperationalised), guarantee anonymity, create an independent authority outside the reporting chain, protect against transfer and adverse ACR entries, and mandate a time-bound outcome so that a complaint cannot simply be absorbed and forgotten.

Source: UPSC Mains GS4, 2022, Q6(a)

Section G — Practice Question

1 practise question — written for this article, not found in any PYQ paper.Unlock with Basic

Section H — Today's Case Study

This section is part of the full analysis.

Upgrade to Basic to read

Section I — Today's Takeaway

Today you added two powerful new concepts to your toolkit — Accountability and Non-Malfeasance — and saw how Kautilya's ancient insistence on holding officials to account is alive and relevant in a 2026 tunnel collapse.

This means you can now handle questions about official negligence, oversight failures, the ethics of development-versus-safety, and the moral responsibility chain in infrastructure projects. Combined with Professional Ethics and Conscience from 07-Jul-26, you already have four concepts that cover a wide range of UPSC GS4 territory.

Concept Ledger

07-Jul-26 — Professional Ethics; Conscience (Voice of Conscience); Kant — Duty Ethics (intro). Foundation. Anchor: Bar Association refusal to represent accused.

08-Jul-26 — Accountability; Non-Malfeasance (Duty to Not Cause Harm); Kautilya — Official Negligence (intro). Foundation. Anchor: Wayanad tunnel debris collapse kills migrant workers.

Concepts covered

accountability non-malfeasance (duty to not cause harm)primum non nocere authority-accountability coin accountability of the overseer negligence as ethical failure Kautilya — prayoga (negligent discharge of duty)delegated trust vulnerability of migrant labour