Strategies That Work, and the Sevottam Model

The strategies that actually move service quality, and the Indian framework built to tie them together. Sevottam is the one model examiners expect you to know by name.

The Sevottam model

Sevottam is the service delivery excellence framework developed by the Department of Administrative Reforms and Public Grievances for use by government organisations. Its importance for an answer lies less in the name than in the reasoning behind its structure.

It rests on three pillars. The first is the citizen charter, which states what the organisation undertakes to deliver, as Chapter 19 examined. The second is public grievance redressal, which provides the route when the undertaking is not met. The third, and the one usually omitted from student answers, is service delivery capability: the internal systems, people and processes that make the promise deliverable in the first place.

The insight in combining them is that each pillar is useless alone. A charter without redressal is a press release, as Chapter 19 argued. Redressal without capability produces complaints that are acknowledged and cannot be resolved, which teaches citizens that the mechanism is theatre. And capability without a published standard produces an office that could deliver well but is accountable to nobody for whether it does.

An answer that explains this interdependence, rather than listing the three pillars, demonstrates that the model has been understood rather than memorised.

E-governance, treated with balance

Digital delivery is the most-cited strategy and deserves the qualified treatment given in Chapter 16. Its genuine gains are structural: direct transfers remove the intermediary who could extract a share, tracked applications remove the discretion to let a file sit, and digital records make patterns visible across thousands of transactions.

The qualifications matter equally. Digitisation relocates discretion rather than removing it, typically toward whoever controls data entry, verification or the exception queue. It can exclude the citizens least equipped to use it, which is the regressive failure Chapter 14 warned about. And automated refusals are opaque, so a citizen may be denied by a system nobody in the office can explain.

The disciplined position is that technology reliably reduces petty extraction at the point of service while creating new concentrations of discretion further back, and that an assisted channel must survive alongside the digital one.

Decentralisation and the point of decision

Moving decisions closer to the citizen shortens the journey, reduces elapsed time and improves the fit between the decision and local circumstances that a distant office cannot see.

Two conditions determine whether it works. Authority must move with the function, since an office that must refer every non-routine matter upward has been given work rather than power. And capability must move with it too, because a decision devolved to staff without the training or systems to take it will be taken badly or not at all. Decentralisation without those two is simply relocation of the queue.

Measure the right things

Chapter 16 established that organisations act on what is measured and that a badly chosen indicator causes active harm. Applied here, three rules follow.

Measure outcomes rather than activity: applicants who received the entitlement, not files disposed. Measure the citizen’s experience rather than the department’s record, through sample verification, callbacks or exit feedback. And use several indicators together, because any single measure can be improved by degrading something it does not capture.

Add one further discipline that costs almost nothing: disaggregate. A district average conceals the block that fails, and an overall figure conceals the community that is under-served. Most of the useful information in service data lies in its distribution rather than its mean.

Participation, and the limits of feedback

Citizen feedback improves service by supplying information the organisation cannot generate internally, and Chapter 16 explained why external perspective is structurally necessary. Social audits, user committees, exit surveys and public hearings all serve this function.

The limitation deserves acknowledgement. Feedback mechanisms are used disproportionately by the confident and the connected, which means they can systematically under-report the experience of exactly those the service most often fails. Chapter 19 made the same point about complaints. Feedback should therefore be supplemented by proactive verification that does not depend on the citizen initiating it, and by outreach to groups that are not appearing in the responses.

Sequencing the strategy

Given limited attention, order matters more than completeness, and this is what a constructive answer should offer.

Begin with process simplification, because it costs nothing and produces visible early results. Follow with information at the point of service, which removes a large share of repeat visits. Then fix grievance redressal, which is what makes every other commitment credible. Then measurement and publication, which sustains attention. Technology should follow rather than lead, because digitising a badly designed process preserves the bad design and makes it harder to change. And capability building runs throughout rather than as a phase.

Part 4 turns from systems to the officer, and to the attributes that determine whether any of this is actually delivered.

Single window, and what makes it real

Chapter 20 identified the silo as the source of most citizen-facing failure, since the difficulty usually sits at the joins between departments rather than inside any of them. The single-window arrangement is the standard remedy and is frequently implemented in name only.

A genuine single window changes who owns the outcome. The citizen submits once, and responsibility for obtaining what is needed from other offices passes to the administration rather than remaining with him. A counter that merely accepts the application and then tells the applicant to pursue the other departments himself has relabelled the problem.

The test worth applying, and stating in an answer, is simple: after the reform, does the citizen still have to visit the other offices? If he does, the window is a reception desk. If he does not, the administration has internalised its own coordination problem, which is what the reform was for.

Public-private delivery, with the conditions

Contracting delivery to private operators can improve reach and speed, particularly for standardised transactions, and it is a legitimate strategy rather than a betrayal of public purpose. It carries conditions that answers routinely omit.

Accountability does not transfer with the function. When a contracted operator fails or overcharges, the citizen’s complaint is still against the state, and the contract must therefore carry service standards, penalties and the state’s right to inspect. Chapter 17 supplies the underlying principle: interests a private operator has no structural reason to protect must be protected from outside.

Two further conditions matter. Coverage obligations must be explicit, or the operator will serve the profitable locations and leave the remote ones, which converts a service improvement into a new form of exclusion. And the state must retain enough internal capability to specify, supervise and if necessary resume the function, since an administration that has lost the ability to do the work cannot meaningfully hold anyone to account for doing it badly.