Why Citizen Charters Fail in India

Chapter 19 · Citizen Charter · Part 3

Thousands of charters exist and few operate. The reasons are specific and mostly structural, which means they are addressable.

Chapter 19 · Citizen CharterPart 1 · The Idea and Its Principles
Part 2 · What an Effective Charter Contains
Part 3 · Why They Fail in India ← you are here
Part 4 · Making Charters Real

Straight from the syllabus

Citizen’s Charters.

This is the most frequently examined aspect of the topic. Diagnose causes rather than listing complaints.

The original sin: charters written to comply

Most Indian charters were produced because a central instruction required departments to produce one. That origin explains most of what follows, and stating it early organises the whole answer.

A document created to satisfy an instruction is written by whoever can be spared, copied substantially from another department’s version, approved without the involvement of the staff who must deliver it or the citizens who will rely on it, and filed. It commits to nothing checkable because nobody drafting it intended to be checked. Everything below is downstream of this: the vagueness, the ignorance of frontline staff, the absence of monitoring and the lack of consequences are not separate failures but symptoms of a document nobody ever meant to operate.

Citizens do not know they exist

The first practical failure is awareness. A charter that citizens have never heard of exerts no pressure, because the entire mechanism depends on someone invoking it.

The causes are ordinary: publication on a website that the relevant citizens do not use, language and register that assume education, absence of any display at the point of service, and no mention in the routine interaction where it would matter. The effect is regressive in exactly the way Chapter 14 described. A literate, connected citizen may find and cite the charter; the person most likely to be failed will not know a standard exists, so the instrument is least available where it is most needed.

Standards that cannot be breached

Part 2 set out the test, and it is failed extremely widely. Indian charters are full of undertakings to act promptly, to endeavour, to ensure satisfaction and to process expeditiously. None of these can be missed, so none creates any obligation.

Where numerical standards do appear, three defects recur. They may cover only the simplest services while the difficult ones are described in general terms. They may be internally inconsistent with the department’s own procedures, promising a timeline shorter than the mandatory steps allow. Or they may measure the wrong thing, committing to acknowledge an application within three days while saying nothing about deciding it.

The staff have not read it

A charter that frontline staff do not know about cannot be delivered, and this is more common than any other single failure. Officers at the counter frequently learn a charter exists when a citizen produces it.

Two causes are worth separating. The first is simple non-communication: the document was circulated to senior officers and never taught to the people bound by it. The second is more serious. Where staff were not consulted, the standards may be genuinely unachievable given staffing, systems or workload, and staff who know a commitment is impossible will disregard the whole document rather than fail visibly against part of it. Participation in drafting is therefore not a democratic nicety, it is what makes the resulting standard credible to the people who must meet it.

No monitoring, no consequence

The decisive failure is that performance against charter standards is usually neither measured nor reported, and breach carries nothing.

Where nobody records whether the seven-day standard was met, the standard exists only in the document. Where it is recorded internally but never published, citizens cannot use it. And where a breach produces no consequence for the office, no entry in an appraisal, no compensation, no requirement to explain, then meeting the standard is optional and will be treated accordingly by anyone under pressure.

Chapter 16 supplied the governing principle and it applies exactly: scrutiny without consequence teaches an organisation that scrutiny does not matter. A charter with no monitoring is a charter with no scrutiny at all.

Resistance, resources and the honest objection

Staff resistance is usually presented in answers as obstruction, which is unfair and analytically weak. Some of it is genuine and should be acknowledged.

A charter imposes a measurable obligation on people who may already be short of staff, working with systems that fail, and dependent on other offices they do not control. An officer required to issue a certificate within seven days when the verifying agency routinely takes three weeks is being held to a standard he cannot meet by any effort of his own. Publishing commitments without addressing capacity converts a resource problem into an individual performance failure, which is both unjust and ineffective.

The legitimate part of the objection therefore points to the remedy rather than away from it. Standards must be set with the people who will deliver them, must account for dependencies outside the office, and must be accompanied by whatever change in staffing, process or system the commitment actually requires. Where that is impossible, the honest response is a lower standard published truthfully, not a higher one published and ignored. Part 4 turns to what makes charters work.

Weak redressal, and what citizens learn from it

Part 2 argued that redressal is the enforcement arm of a declaratory document. In practice it is the component that fails most completely, and the consequences run deeper than a single unresolved complaint.

Typical defects are easy to list and worth naming precisely: no acknowledgement, so the citizen cannot tell whether the complaint was received; no tracking reference; complaints routed to the office complained against; no timeline, or a timeline with nothing following its breach; and closure recorded without any communication of the outcome or its reasons.

The deeper damage is educational. A citizen who complains once and receives nothing concludes, accurately, that the mechanism does not work, and he does not complain again. Others learn the same lesson from him. The organisation then observes a low volume of complaints and reports it as evidence of satisfaction, which is the same misreading Chapter 13 identified when exclusion appears in the data as adequate coverage. Low complaint volumes in a poorly performing office are a warning sign, not a reassurance.

The social context that answers usually omit

A charter assumes a citizen willing to assert an entitlement against an official. That assumption does not hold uniformly, and an answer that notices this is doing genuinely useful analysis.

Where there are wide gaps of literacy, caste, class or gender between the counter and the queue, invoking a written standard requires a confidence many applicants do not have and cannot safely display. A person who expects to return to the same office repeatedly, in a small town where the officer is known and locally powerful, has a rational reason not to complain about him. The charter is an instrument of assertion, and assertion is not equally available to everyone.

Two implications follow. Charters cannot be the only accountability mechanism, and must be paired with proactive monitoring that does not depend on the citizen initiating it, such as sample verification and social audit as discussed in Chapter 16. And complaint channels must include routes that do not require face-to-face confrontation with the official concerned, since an anonymous or remote channel may be the only one a vulnerable complainant can use.

A charter written to satisfy an instruction commits to nothing checkable, because nobody drafting it expected to be checked. Every other failure follows from that origin.

Where candidates lose marks

Listing failures without a common cause. Trace them to the compliance origin; it organises the whole answer.

Dismissing staff resistance as obstruction. Much of it is a genuine capacity objection, and conceding it makes your remedies credible.

Missing the regressive effect. The charter is least available to the citizens most likely to be failed.

Revision checklist

  • Most Indian charters were produced to comply with an instruction; that origin explains the rest.
  • Low awareness makes the instrument regressive: unavailable precisely where most needed.
  • Unbreachable wording, coverage of only easy services, internal inconsistency, and measuring acknowledgement rather than decision.
  • Frontline staff often unaware; non-communication plus non-participation in drafting.
  • Unachievable standards cause staff to disregard the entire document.
  • No measurement, no publication, no consequence for breach.
  • Scrutiny without consequence teaches that scrutiny does not matter.
  • Capacity objections are legitimate; standards must account for dependencies outside the office.

“India has thousands of citizen charters and very little charter-driven service improvement.” Analyse the reasons for this gap and identify which of them you consider decisive. (10 marks, 150 words)

Approach: organise around a single cause, that charters were produced to satisfy an instruction rather than to be used, and present the familiar failures as symptoms of it: unbreachable standards, low citizen awareness, uninformed frontline staff, no monitoring. Identify the decisive factor explicitly, the absence of measurement and consequence, and justify the choice, since a specific standard with no cost for breach still changes nothing. Concede the genuine capacity objection. Recommend participative standard-setting, published disaggregated performance, automatic escalation and statutory backing where feasible.

Comments are closed here on purpose — so that every question lands in one place where I actually reply. Drop yours under the latest ethics lecture and I will answer it there.

Ask under the latest lecture →All ethics lectures

You may also like...