What Accountability Actually Requires

Accountability is not the same as blame, and not the same as scrutiny. It has four components, and an arrangement missing any one of them will not produce it.

The four components

Accountability exists where somebody is obliged to explain and justify their conduct to someone with the standing to require it, and where consequences follow from the assessment. That definition contains four elements, and separating them is the most useful analytical move available on this topic because almost every real-world failure is the absence of one specific element rather than of accountability in general.

The first is a standard: something against which conduct can be assessed. Without a stated expectation there is nothing to be accountable for, and any subsequent judgement is arbitrary. This is why Chapter 19 insisted that service standards be capable of being failed, and why Chapter 16 argued that criteria should be settled before the pressure arrives rather than improvised under it.

The second is information: someone must be able to know what was actually done. Chapter 22 was entirely about this precondition, and the point bears repeating here because it explains why transparency and accountability are so often named together. They are not synonyms; transparency is the input and accountability is the process that acts on it.

The third is an answerability relationship: an identified person owes an explanation to an identified forum, whether a superior, a court, a legislature, an auditor or the public. Where nobody in particular owes an explanation to anybody in particular, the arrangement is monitoring rather than accountability.

The fourth is consequence. An assessment that produces nothing teaches the organisation that the assessment does not matter, and Chapter 16 identified this as the commonest failure in Indian accountability arrangements. An audit that finds the same irregularity every year, followed by nothing, is a documentation exercise wearing the vocabulary of accountability.

Why the missing element diagnosis works

Applying this framework to a failing arrangement almost always identifies the specific defect, and that is what an examiner is looking for when a question asks why accountability is weak.

Where officers are assessed against vague expectations, the missing element is the standard, and the remedy is to specify it. Where conduct cannot be observed because records are absent or unpublished, the missing element is information, and the remedy lies in disclosure and recording. Where many people contributed and nobody is answerable, the missing element is the relationship, and the remedy is named ownership as Chapter 20 described. Where everything is known and documented and nothing follows, the missing element is consequence, and no amount of further scrutiny will supply it.

The practical value is that these remedies are different from one another. An institution that responds to every accountability failure by commissioning more scrutiny will not fix a consequence problem, and will simply generate more evidence that nothing happens.

Accountability is not blame

A distinction worth drawing early in any answer, because conflating the two produces bad institutional design. Blame allocates fault after an adverse outcome. Accountability requires explanation and justification, which may conclude that the officer acted correctly and the outcome was nonetheless poor.

The difference has practical consequences that Chapter 16 identified. A system that treats every bad outcome as a fault to be attributed produces officers who avoid decisions, since inaction is rarely audited as harshly as action. A system that assesses the quality of the reasoning available at the time, rather than the outcome known afterwards, can hold officers to a high standard without producing paralysis.

This is why the separation of honest error from misconduct is not a softening of accountability but a condition of it. An arrangement that cannot distinguish the two will be resisted, evaded and eventually rendered ceremonial by people acting rationally to protect themselves.

Answerability and enforcement

A further distinction that sharpens an answer. Accountability has two limbs: the obligation to explain, and liability to consequence. They are separable, and much Indian machinery supplies the first without the second.

An officer summoned before a committee and required to explain an expenditure has been subjected to answerability. Whether anything follows depends on separate machinery. Both limbs matter and they do different work: answerability alone exposes conduct and creates reputational cost, while enforcement alone without explanation produces arbitrary punishment. A well-designed arrangement supplies both, and identifying which limb is missing in a given case is precisely the analysis a question rewards.

Who is accountable to whom

A public servant sits inside several overlapping relationships simultaneously, and these can genuinely conflict, which Chapter 15 treated as a source of dilemmas.

He is accountable upward to his superiors and through them to the political executive; outward to citizens, whose service he exists to provide; sideways to auditors, commissions, courts and regulators; and, in the sense Chapter 18 developed, to the standards of his own service. Ordinarily these point in the same direction. Where they diverge, the question of which prevails is the substance of most ethical dilemmas in public administration.

The ordering principle worth stating is that accountability to law and to the public interest is not displaced by accountability to a superior, since the superior’s authority itself derives from the same source. That is why an unlawful instruction creates no obligation, and why Chapter 18 could set out a sequence for refusing one. Part 2 develops the two directions in which accountability runs.

Accountability for omission

A gap that deserves explicit attention because it shapes behaviour more than any other feature of Indian accountability. Systems are far better at examining what was done than what was not.

An officer who takes a decision that turns out badly may face an inquiry. An officer who takes no decision at all, and allows a matter to remain pending for years, is rarely asked to account for it, because there is no event to examine, no file movement to audit, and no complainant unless the affected citizen persists. The harm may be greater and the scrutiny is less.

This asymmetry is the mechanism behind the defensive proceduralism described in Chapter 20, and it means an accountability system that examines only positive acts will systematically produce inaction. The corrective is to measure pendency and ageing as seriously as irregularity, to require explanation for matters exceeding a threshold, and to treat unexplained delay as a reportable failure rather than as an unfortunate background condition.

Collective and individual responsibility

A final structural point. Where a decision is taken by a committee or emerges from a chain of approvals, accountability disperses, and Chapter 20 identified this as a central pathology.

The answer is not to abolish collective decision-making, which exists for good reason and reduces the scope for individual capture. It is to record positions: who proposed, who concurred, who dissented and on what basis. A committee whose minutes show only that a decision was taken unanimously has protected everyone in the room from ever being answerable for it.

Recording dissent is therefore not an act of disloyalty but a condition of collective accountability functioning at all, and an officer who records his reservation has both discharged his duty and preserved the institution’s ability to learn from what follows.