Designing the Escalation Ladder for Citizen Complaints

Executive Summary

An escalation ladder is the set of rungs a complaint climbs when the first officer does not resolve it, and the clock that moves it up. The Department of Administrative Reforms and Public Grievances (DARPG) set out the national version in its office memorandum of 23 August 2024 on handling public grievances in CPGRAMS: 21 days for redress, 3 days for urgent cases, appeals to a senior officer, 30 days to decide the appeal.

Read closely, that ladder is pulled by the citizen. It has rungs after the Grievance Redressal Officer (GRO) disposes of a case, and a nodal officer who monitors pendency, but the text sets no rung that fires by itself while a case is open and unworked. This guide is for the state IT department, district collectorate or chief minister's grievance cell that runs a portal and wants to add that push.

Executive Callout Design the ladder in two directions. A push rung moves an open case up because a clock ran out. A pull rung moves a disposed case up because the citizen said the problem is still there. Most portals have the second and lack the first. A voice layer can carry both, but it can only report and trigger; named officers still own every rung.

Introduction: Where the Ladder Stands Today

DARPG's 2024 circular is the clearest public statement of how a national grievance ladder works, so it is a useful baseline even for a state running its own portal. These are its rules, as written:

Rule	What the circular says
Redress time	Maximum of 21 days; an interim reply with reasons and expected timeline if longer (para 5.1)
Urgent cases	Priority grievances resolved within 3 days (SOP para 3.1.1)
Wrong officer	Forward within 48 hours; never close as "does not pertain to this office" (SOP 3.2.1, para 7.1)
Pendency	The nodal officer monitors it and sees GRO performance on a dashboard (para 3)
Appeal	Goes to the officer next senior to the GRO; a Nodal Appellate Authority of Additional or Joint Secretary rank, with Sub Appellate Authorities beneath (para 6, Annexure 4.2)
Appeal time	Ordinarily closed within 30 days; one appeal per grievance (para 6, Annexure 4.1)
Closure	A disposed case is closed unless the citizen appeals; if they do, it closes only after the appeal is decided (para 7.5)
Senior review	Secretary-level review in Senior Officers Meetings, and weekly examination of disposals by Secretary, Additional or Joint Secretary (para 13)

Two details matter for design. The circular lists the appeal channels as the portal, a chatbot, WhatsApp and DARPG's feedback call centre, so a phone route to appeal is already contemplated. And it says a case can be closed for insufficient information only after "genuine effort" to reach the citizen, which is a call-handling task, not a form-handling one.

State portals have their own timelines; read yours before borrowing any number here.

The Gap: Rungs After Disposal, None Before It

Put the rules on a timeline. For the first 21 days a case sits with one officer. The nodal officer can see it on a dashboard and the Secretary reviews disposals weekly, but nothing in the text moves a quiet case to anyone. The first rung that is certain to fire is the citizen's appeal, and only after the GRO has disposed of the case.

That produces a specific failure: a case that is neither resolved nor disposed. It sits open, the officer is inactive or overloaded, and the citizen has no rung to climb because there is nothing yet to appeal. The companion piece on SLAs explains why disposal figures hide this. The rungs below expose it.

The same pattern shows up in older helplines. An IIMA study of Kisan Call Centres in Gujarat (March 2018) asked call-centre advisers to rate how the escalation tiers worked, on a 1-to-5 scale where 1 means never. Passing a hard query to a colleague or supervisor rated 5 for frequency and escalation to Level 2 experts rated 4. Escalation to Level 3, handled by nodal officers, rated 1 for frequency and 1 for nodal officers responding to farmers, and the authors wrote that nodal officers "do not often attend to the questions even through SMS or other means." The study is old, covers one state and reflects the advisers' view, not the farmers'. The lesson holds: a tier that exists on the org chart and never answers is worse than no tier, because it makes the system look covered.

A Reference Ladder: Five Rungs, Three Clocks

The ladder below combines the circular's rules with recommended timers for the push rungs. The recommendations are design choices, not DARPG policy. The Day 7, 14 and 20 points are adapted from the follow-up schedule in the Aisewak Government Helpline Report (2026), which proposes Day 7, 14 and 20 callbacks for a CPGRAMS voice pilot. For a district cell, read Collector where the table says Secretary.

Rung	Owner	Clock	What moves the case	Citizen is told	Basis
0. Routing	Receiving GRO or nodal officer	48 hours to forward	Wrong department	Reference number and owning post	Circular
1. GRO	Named GRO	21 days; 3 for urgent	Assignment	Reference, current status	Circular
2. Pendency watch	Nodal officer	Day 7 nudge, Day 14 notice	Timer, no action recorded	"Still with Officer X; reminder sent"	Recommended
3. Senior review	Secretary or Collector	Day 20 listing, then weekly	Case about to breach	Interim reply with reason and date	Circular (review); recommended (listing)
4. Appeal	Appellate authority	30 days	Citizen is not satisfied	Appeal reference, one per case	Circular

The three clocks are the 21-day redress clock, the push clock that runs inside it, and the 30-day appeal clock. Keep them separate in the system. A single "SLA timer" that restarts on every status change is how a pending case looks fresh.

Four decisions to make before configuring anything

Who gets each notice, by post and not by name. A nudge addressed to a transferred officer goes nowhere. Route to the post, resolve to the current holder at send time.
What counts as action. If opening a case resets the push clock, officers will open and leave. Define action as a recorded reply, a document request or an interim action-taken report.
What the citizen hears at each rung. A citizen told "your case has been escalated" with no name, date or consequence learns nothing. Tell them who holds it now and when to expect an answer.
Who may skip a rung. Threats to life, a woman or child in danger, or a fraud in progress do not wait for Day 14. They leave the ladder for 112, 1098, 181 or 1930 and a human.

Where a Voice Layer Sits on the Ladder

A voice layer does not own a rung. It reads the portal, tells the citizen where the case stands, and triggers notices that the system of record then owns. AiSewak builds this as a layer over the portal a department already runs, so the case, the reference and the ladder stay in that system. It handles four jobs:

Status at any rung. The citizen calls with a reference number and hears the owning post, the rung and the next date, read from the portal. This is a read-only integration, the same low-risk first step described in the voice-layer guide.
Push notices. At Day 7 and Day 14 the portal, not the agent, sends the nudge to the GRO and then the nodal officer. The agent can tell the citizen it has gone.
Reaching the complainant before an "insufficient information" closure. The circular requires a genuine effort to contact the citizen first. A call attempt, with time, number and outcome logged, turns that sentence into an audit record. Outbound calls fall under TRAI's TCCCPR if classified as commercial communication; the permitted window is 10:00–21:00 IST, and the nodal legal officer should confirm the classification for government service calls.
Pull by phone. When the citizen says the problem is not fixed, the agent files the appeal, or a reopen request where the portal uses one, with their words attached. The one-appeal-per-case rule means it must check for an existing appeal first.

What it must not do is decide a rung, close a case, or tell a citizen an outcome the officer has not recorded.

Three Ways Ladders Fail in Practice

The silent rung. The Kisan Call Centre pattern above. Send a real escalation through every rung and time the reply, reporting response time per rung rather than an average.

The bounce. A case closed as "does not pertain" or forwarded in a loop between two offices. The circular bans the first and sets 48 hours for the second. A routing table by jurisdiction and subject, reviewed monthly, removes most of it.

The double appeal. A citizen who appeals by portal, then phone, then the feedback call centre creates three cases for one problem. Enforce one open appeal per grievance in the system and give the same reference on every channel.

What to Measure in a One-Department Pilot

A pilot should show whether the push rungs change behaviour, not whether the agent answers calls. Run it in one department and one district, with the portal API read-only first.

Measure	Why it matters
Open cases past Day 14 with a recorded reply	Shows whether the nudge produced action, not just a notice
Median time from nudge to recorded action, per rung	Exposes silent rungs
Cases forwarded after 48 hours	Tests the routing rule
"Insufficient information" closures with logged call attempts	Tests the circular's genuine-effort requirement
Appeals decided within 30 days	Tests the pull rung
Citizen-confirmed closures against disposals	The measure the disposal-versus-resolution analysis argues for

Set the baseline from one month of the department's own closed cases first. No honest target exists until that baseline does.

Risks and Mitigation

Notice fatigue. An officer who gets a reminder for every open case stops reading them. Nudge only cases with no recorded action.
A ladder for show. Decide before launch who answers the Day 14 notice and give that person a dashboard. A rung with no owner reproduces the Level 3 result.
Promising outcomes. An agent that predicts a result creates a commitment the officer did not make. Script it to report status only.
Personal data. Call recordings and transcripts hold names, numbers and complaint details. Set the purpose, retention window and access roles in the pilot order. Parts of the DPDP Act, including its consent and penalty provisions, commence on 13 May 2027, so plan for them now.

Key Takeaways

The national ladder has rungs after disposal and a nodal officer watching pendency, but no push rung for a quiet open case. Add one.
Keep three clocks separate: 21 days for redress, a push clock inside it, 30 days for appeals. Define rungs by post and "action" narrowly.
Use the voice layer for status, call attempts and phone appeals. Keep assignment, escalation decisions and closure with named officers.
Test every rung by timing a real escalation. A silent rung is the main failure.

Conclusion

A grievance ladder is a set of promises about who will look at a complaint and when. DARPG's 2024 memorandum makes them clearly for the stage after disposal. The stage before it, where a case waits on a quiet desk, is where a department can add the most with the least change to its portal: two timers, two named recipients and a status answer that matches the system of record. A department can test this in a month by applying the Day 7 and Day 14 rules to its open cases in read-only mode and counting how many would have fired.

Government leaders exploring AI-powered citizen engagement can begin with a focused pilot in one department or constituency to validate impact before scaling statewide. Aisewak helps public institutions deploy multilingual Voice AI solutions designed specifically for Indian governance. For an evaluation checklist before procurement, see the buyer's guide.

FAQ

What is a grievance escalation matrix? It is a table of who handles a complaint at each stage, how long they have, and what moves the case to the next person. A good one names posts rather than people and states what the citizen is told at each stage.

How long should a government body take to resolve a citizen grievance? DARPG's August 2024 circular advises a maximum of 21 days for CPGRAMS, with an interim reply if more time is needed and 3 days for urgent cases. State portals set their own limits, so check the order that governs yours.

Who hears an appeal against a CPGRAMS decision? The appellate authority, an officer next senior to the GRO. Each ministry appoints a Nodal Appellate Authority of Additional or Joint Secretary rank and may appoint Sub Appellate Authorities beneath. Appeals are ordinarily closed within 30 days.

Does CPGRAMS escalate a case automatically if the GRO does nothing? The 2024 circular does not set such a rung. It makes the nodal officer responsible for monitoring pendency and requires senior review, and it provides appeals for disposed cases. The portal software may contain other prompts that the circular does not describe.

Can a citizen file an appeal by phone? The circular lists the portal, a chatbot, WhatsApp and the DARPG feedback call centre as appeal channels. A state department adding its own phone route should follow its portal's rules and allow only one appeal per grievance.

What should an escalation notice to an officer contain? The case reference, the date it was filed, the days remaining, the last recorded action and the citizen's own description. It should go to the post, not a named individual.

Does a voice agent make escalation decisions? No. It reports status, logs contact attempts and files the citizen's appeal or reopen request. Assigning, escalating and closing remain with named officers.

When should a complaint skip the ladder? When someone is in danger. Fire, medical emergency, violence, a child or woman at risk and active financial fraud go to 112, 1098, 181 or 1930 and a human, not to a Day 14 timer.

Schema Markup Suggestions

TechArticle — headline, description, datePublished, dateModified, author (Organization: AiSewak Editorial), publisher
FAQPage — each Q/A above as Question + acceptedAnswer
HowTo — for the reference ladder: name: Design a Citizen Grievance Escalation Ladder, five HowToStep items matching the table rungs
GovernmentService — on the linked /ai-grievance-redressal-system landing: serviceType: Citizen Grievance Redressal, areaServed: India

Suggested External References

DARPG Office Memorandum on handling public grievances in CPGRAMS, F.No. S-15/21/2021-(PG)-DARPG(e-7085), 23 August 2024 — pgportal.gov.in
Gandhi and Johnson, Decision-Oriented Information Systems for Farmers, IIM Ahmedabad, March 2018 — iima.ac.in
Aisewak Government Helpline Report, 2026 — Day 7, 14 and 20 follow-up design for a CPGRAMS voice pilot
TRAI TCCCPR 2018, as amended 12 February 2025 — outbound calling window

India's national grievance ladder has rungs after a case is disposed and none that fires while it sits unworked. DARPG's 2024 rules set 21 days, 3 for urgent cases and 30 for appeals. A design guide for adding the missing push rung, and where a voice layer fits.

LinkedIn Executive Summary

DARPG's August 2024 circular on CPGRAMS sets a clear ladder: 21 days for a GRO to resolve, 3 days for urgent cases, an appeal to the officer next senior, 30 days to decide it.

Read against a timeline, the ladder is pulled by the citizen. It starts working after disposal. A nodal officer watches pendency and the Secretary reviews disposals, but the text sets no rung that fires on a case that is open and untouched.

For a state IT department or district cell, the fix is small. Add two timers inside the 21 days, route notices to posts rather than names, define "action" narrowly, and tell the citizen who holds the case and by when. Test every rung by timing a real escalation; an older IIMA study of Kisan Call Centres found a top tier that nodal officers rarely answered.

A voice layer can read status, log the call attempts the circular requires before an "insufficient information" closure, and take a phone appeal. Named officers keep every decision.

AI Search Optimization Summary

Entities: DARPG, CPGRAMS, Grievance Redressal Officer, Nodal Appellate Authority, Sub Appellate Authority, Nodal Officer for Public Grievances, IIM Ahmedabad, Kisan Call Centre, TRAI TCCCPR, Aisewak

Topics: grievance escalation matrix, citizen complaint escalation design, CPGRAMS appeal process, government grievance SLA timers, appellate authority India, voice layer for grievance portals

Semantic keywords: escalation ladder for citizen complaints, grievance redressal timeline 21 days, CPGRAMS appeal 30 days, push and pull escalation, nodal officer pendency monitoring, interim action taken report, single appeal per grievance, status call by reference number