Disposal Is Not Resolution: Reading Grievance SLAs Honestly

Executive Summary

India's government grievance portals collectively report disposal rates above 95 percent. India's citizens report satisfaction rates below 51 percent. That gap — roughly 44 percentage points at CPGRAMS and larger at some CM helplines — is not measurement error. It is the direct consequence of SLAs written around the wrong event. When a grievance contract says "resolve within 15 days", it almost always means "mark the file closed within 15 days". The two are not the same, and writing them as though they are produces systems that hit every target while solving very little.

Executive Callout: The BSNL Feedback Call Centre surveys citizens after CPGRAMS marks their grievances "closed" and has consistently recorded 44–51 percent satisfaction against a claimed 95 percent disposal rate. The SLA was met. The citizen's problem was not. (Aisewak Government Helpline Report, 2026, citing DARPG and BSNL internal data)

This article is for the officials who write, negotiate, and sign grievance-system contracts: IT Secretaries, DMs, Municipal Commissioners, and the GRC heads of CM helplines. The argument is precise: your SLA almost certainly measures the Disposal Clock. It should also measure the Resolution Clock. Voice AI makes measuring both operationally and financially feasible.

Introduction: One Metric, Two Different Events

A grievance SLA governs two events that are easy to confuse: the moment a Grievance Redressal Officer (GRO) changes a status field, and the moment a citizen confirms their problem is solved. Government contracts historically track only the first event, which is auditable and entirely within the department's control. The second event — whether the road was actually repaired, the pension actually arrived, the electricity actually returned — requires talking to the citizen after the fact, which no existing grievance contract in India mandates at scale.

The result is a measurement architecture optimised for the wrong outcome. Rajasthan Sampark 181, India's largest state grievance helpline by volume, processes over 40 lakh grievances monthly, reports a 99.36 percent disposal rate — and carried more than one lakh pending cases as of late 2024 (Aisewak Government Helpline Report, 2026). The Chief Secretary visited the call centre daily to monitor performance. The disposal metric looked excellent. The pendency figure told a different story.

Understanding why this happens, and how to fix it, is the procurement question most RFPs still avoid.

The Three Things "Resolved" Can Mean

Before rewriting a grievance SLA, it helps to be precise about what "resolved" is being asked to mean. Three definitions circulate in government grievance work, and they do not agree with each other.

Definition 1 — Administrative closure. The GRO marks the case "disposed" in the system. This is the event nearly all grievance contracts measure. It is within the GRO's unilateral control and requires no contact with the citizen. This is what produces a 95 percent disposal rate.

Definition 2 — Action taken. A field officer visited the site, processed the application, or took a documented step toward resolving the underlying problem. More demanding than Definition 1, but still unilateral — the citizen may receive no notice that action was taken, and no independent verification exists.

Definition 3 — Citizen confirmation. The citizen who filed the complaint confirms, when asked after administrative closure, that the problem is solved to their satisfaction. This is the definition BSNL's Feedback Call Centre uses when it surveys CPGRAMS complainants. The gap between Definition 1 and Definition 3 is the 44–51 percent satisfaction figure.

Most grievance SLAs in India operate at Definition 1. Some aspire to Definition 2. Almost none enforce Definition 3 contractually. The AI-era grievance contract should enforce all three, sequentially, with each gate conditioning the next.

What the Data Says About SLA Compliance

The disposal-vs-resolution gap is not a hypothesis. It appears independently across different states, departments, and helpline types.

Platform	Disposal claim	Satisfaction / Resolution data	Source
CPGRAMS (national)	95% disposal	44–51% citizen satisfaction (BSNL survey)	DARPG / BSNL, cited in Aisewak Report 2026
Rajasthan Sampark 181	99.36% disposal	1 lakh+ pending; 7-day avg resolution time	RAS / Chief Secretary statement
UP CM Helpline 1076	—	25% redressal rate — three of four complaints unresolved	State government disclosures
Maharashtra CPGRAMS appeals	—	55% first appeals, 78% second appeals pending	CAG Maharashtra audit
Odisha Jana Sunani	—	69,532 grievances pending beyond their own SLA	CM's Assembly statement

In each case the SLA measures the Disposal Clock. The citizen satisfaction data, where it exists, measures something closer to the Resolution Clock. The two numbers diverge because the GRO's closure action and the citizen's resolution experience are separate events.

One exception is instructive. Rail Madad — the Indian Railways grievance system — reports a 99.98 percent resolution rate with a 26-minute average disposal time (Aisewak Government Helpline Report, 2026). Rail Madad works because the majority of its complaints are transactional: wrong coach, missing meal, broken AC. The citizen can verify resolution almost immediately because the resolution itself is observable. CM helplines, CPGRAMS, and municipal grievance systems handle structural problems — a road that floods, a pension that stopped, a ration card that never arrived — where the underlying fix takes days or weeks and the citizen has no way of knowing whether it happened unless someone tells them.

The distinction points to a rule: SLAs calibrated for transactional queries will systematically fail for structural complaints, because the resolution event is not immediate and requires post-hoc verification. Most grievance contracts apply transactional SLA logic to structural problem types.

What GRO Activity Data Reveals

The disposal-satisfaction gap has an additional structural cause that SLA design rarely addresses: a significant share of GROs are not processing cases at all. DARPG's own data shows that only 42.4 percent of Grievance Redressal Officers were active as of June 2024, well below the 100 percent mandate (Aisewak Government Helpline Report, 2026).

A grievance SLA that runs a 15-day clock without an automated early-warning mechanism for dormant GROs will consistently produce good disposal numbers and poor outcomes. The complaint is logged, routed to an officer, and ages in a dormant queue until the SLA clock expires — at which point the system auto-closes it or a supervisor does so manually. This is precisely how CPGRAMS achieves 95 percent disposal and 44 percent satisfaction simultaneously.

The corrective mechanism is an escalation SLA nested inside the resolution SLA: if a GRO does not acknowledge within 24–48 hours, the case escalates automatically. CPGRAMS's own DARPG design targets auto-escalation nudges at Day 7, Day 14, and Day 20, with automatic re-routing for dormant cases. The UP CM Helpline 1076 pilot design specifies a 48-hour acknowledgement rule (Aisewak Government Helpline Report, 2026). Neither helpline currently enforces these timers systematically at scale — because enforcement requires real-time monitoring that no human team can run at 135,000 calls per day.

The Two-Clock SLA Model

A properly designed grievance SLA governs two clocks, not one.

Disposal Clock — The time from complaint registration to administrative closure. This is the clock current SLAs measure. It should cover intake, classification, routing, and GRO action. Sub-clocks nested inside: time-to-acknowledge (24–48 hours), time-to-action (depends on complaint type), time-to-closure (the current contract SLA).

Resolution Clock — The time from administrative closure to citizen-confirmed resolution. This clock starts when the GRO closes the case and ends when a post-resolution survey records citizen confirmation. If the citizen says "no", the case re-opens automatically and the Disposal Clock starts again.

The two-clock model is not a theoretical construct. BSNL already runs something like a Resolution Clock manually for CPGRAMS — calling a sample of complainants after disposal. The difference between that and an AI-powered closed-loop system is coverage (sampled vs. 100 percent), speed (weeks later vs. hours), and feedback-loop integration (no automatic re-open vs. automatic re-open on dissatisfaction).

SLA element	Current contracts	Two-clock model
Primary metric	Disposal rate (% closed within X days)	Resolution rate (% confirmed resolved by citizen)
GRO accountability	Supervisor review (manual, delayed)	Auto-escalation if no acknowledge in 24–48 hrs
Closure verification	GRO unilateral	Citizen callback required before case closes
Re-open mechanism	Citizen must re-file	Automatic on negative callback
Reporting	Disposal volume, avg time	Resolution rate, reopening rate, CSAT
Penalty clauses	Disposal SLA breach	Resolution SLA breach, CSAT floor

Where Voice AI Changes the Calculation

Running the Resolution Clock at scale requires calling citizens after every case closure — a volume no manual team can sustain. At CPGRAMS volumes (over 26 lakh grievances in 2024), even a 10 percent post-closure call sample requires hundreds of calls per day in addition to existing inbound load. BSNL runs this manually as a sampled process, which is why its findings reach DARPG as a lagging indicator rather than a live control signal.

A voice AI agent handles post-resolution callbacks at marginal cost, runs the verification in the citizen's own language across 22 scheduled Indian languages via Bhashini, and feeds the result directly to the grievance system — triggering re-open if the citizen is unsatisfied. The CPGRAMS pilot targets CSAT ≥65 percent for the voice channel, compared to the 44–51 percent baseline on the human-only system (Aisewak Government Helpline Report, 2026). That 14–21 percentage point improvement is precisely the gap the Resolution Clock was designed to close.

The same AI infrastructure that runs verification callbacks also enforces escalation SLAs — monitoring GRO acknowledgement times and triggering automatic re-routing when the 24-hour or 48-hour window passes without action. This makes the Disposal Clock enforceable in real time rather than retrospectively.

For departments evaluating whether to add an AI layer to their existing grievance portal, the integration question matters: read-only access is sufficient for status queries, but closing the Resolution Clock requires write access to re-open cases and update satisfaction records. See the AI grievance redressal system page for the integration architecture that supports both clocks.

Rewriting the SLA: What Procurement Officers Should Change

1. Add a Resolution Rate KPI. Alongside or instead of disposal rate, specify a minimum citizen-confirmed resolution rate. CPGRAMS's own DARPG pilot design targets CSAT ≥65 percent for the voice channel. A state CM helpline contract should target similar floors and tie AMC renewal to meeting them.

2. Build escalation triggers into the contract. The GRO acknowledgement window should be a contractual SLA element, not an operational guideline. Specify: if a GRO does not acknowledge a grievance within 24 hours (or 48 for complex cases), the system auto-escalates to the GRO's supervisor, logged and auditable.

3. Define re-open conditions contractually. If a post-resolution callback records citizen dissatisfaction, the case must re-open automatically. This should be a contract-level requirement, not a configuration option the vendor can disable.

4. Penalise on Resolution Clock, not just Disposal Clock. A vendor that hits 95 percent disposal and 44 percent satisfaction is meeting the letter of most current contracts while failing the public. Penalty clauses — typically 0.5–1 percent AMC per SLA breach point — should apply to the Resolution Clock metrics.

5. Require GRO-level reporting. Aggregate department-level disposal figures can hide a pattern where three GROs handle 80 percent of cases while seven are dormant. The contract should require GRO-level response rate reports, making individual accountability visible without requiring manual audits.

Expected Impact: Before and After

Metric	Current (Disposal Clock only)	Target (Two-Clock model)
Primary SLA metric	Disposal rate (95% CPGRAMS claimed)	Citizen-confirmed resolution rate (target ≥65%)
GRO active rate	42.4% active (CPGRAMS June 2024)	100% tracked via auto-escalation
Post-closure verification	Manual, sampled, no re-open	100% voice callback, automatic re-open
Appeals pendency	55% first appeals pending (Maharashtra CAG)	Reduces as re-open captures dissatisfied citizens before they appeal
CSAT baseline	44–51% (CPGRAMS BSNL survey)	Target ≥65% for AI-supported channel

Risks and Mitigation

Risk: The Resolution Clock creates new gaming incentives. If departments are penalised on CSAT, staff may selectively call cooperative citizens for the verification survey. Mitigation: Use random sampling for the verification cohort, selected by the AI system before the GRO closes the case, with results inaccessible to the officer whose case it is.

Risk: Citizens who cannot be reached inflate dissatisfaction counts. A citizen who does not answer the callback phone should not be counted as dissatisfied. Mitigation: Count only reached-and-responded citizens; track separately the not-reached rate as an accessibility metric.

Risk: DPDP Act compliance on post-resolution calls. Voice recordings and satisfaction data are personal data. Mitigation: The DPDP Act's consent and penalty sections commence 13 May 2027. Systems procured now must build documented consent for post-resolution calls into the intake flow, so deployment is compliant before commencement.

Risk: Departments resist the re-open mechanism as it inflates pendency. Mitigation: Frame the Resolution Clock as a quality-assurance tool, not a performance penalty — and note that the current alternative (BSNL survey data showing 44 percent satisfaction) is already public. A live re-open rate is easier to manage than a lagging satisfaction survey.

Key Takeaways

Most grievance SLAs measure administrative closure (the Disposal Clock). They should also measure citizen-confirmed resolution (the Resolution Clock). The two clocks track different events.
The CPGRAMS data is the clearest evidence: 95 percent disposal rate, 44–51 percent satisfaction. The gap is a measurement design choice, not an operational failure that more staff can fix.
GRO dormancy — 42.4 percent active as of June 2024 — is the enforcement failure the Disposal Clock cannot see. Auto-escalation SLAs make it visible in real time.
Post-resolution voice callbacks, run by AI at full coverage, convert the BSNL manual sampling process into a live control signal that the grievance system can act on automatically.
Procurement officers should add Resolution Rate and reopening rate to contractual KPI schedules, and tie penalties to them — not only to disposal volume.

Conclusion

The Indian state has invested heavily in measuring whether grievances are disposed. It has invested almost nothing in measuring whether they are resolved. The consequence is a system that can prove it processed a complaint and cannot prove it fixed the problem — visible in the satisfaction gap at CPGRAMS, the pending backlog at Rajasthan Sampark, and the 25 percent redressal rate at UP's CM helpline.

Rewriting grievance SLAs to include the Resolution Clock is a contract-design choice, not a technology choice. The technology — voice AI, Bhashini, automated escalation — makes it operationally feasible to run that clock at scale. But the change starts in the RFP, where procurement officers specify what "resolved" will mean and which clock the vendor's AMC will be penalised on.

The citizen grievance management evaluation guide sets out how to select a system that can run both clocks. Why traditional government helplines fail traces the structural reasons the Disposal Clock dominates.

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 — including the AI-enabled grievance redressal infrastructure that state and district administrations are procuring now.

FAQ

Q: What is a grievance SLA in government context? A grievance SLA (Service Level Agreement) specifies the time within which a government body must process and close a citizen complaint. Most SLAs in India define "closed" as administrative disposal — the moment a GRO marks a case resolved in the system — rather than citizen-confirmed resolution.

Q: Why do government grievance systems show high disposal but low satisfaction? Because disposal measures when a file is marked closed and satisfaction measures whether the underlying problem is actually fixed. These are separate events. CPGRAMS records 95 percent disposal against 44–51 percent citizen satisfaction because administrative closure is within the GRO's unilateral control, while genuine resolution depends on field action the system cannot verify (Aisewak Government Helpline Report, 2026, citing DARPG and BSNL data).

Q: What is the "two-clock SLA model"? A framework that distinguishes the Disposal Clock (time from complaint registration to GRO closure) from the Resolution Clock (time from GRO closure to citizen confirmation that the problem is solved). Current contracts measure only the Disposal Clock. A properly designed SLA governs both and requires citizen confirmation before a case is permanently closed.

Q: How does GRO dormancy affect grievance SLA compliance? Only 42.4 percent of Grievance Redressal Officers were active on CPGRAMS as of June 2024 (DARPG data, cited in Aisewak Government Helpline Report, 2026). A dormant GRO's caseload ages in queue until the SLA clock expires, at which point cases are closed without any action. This produces high disposal rates from the system's perspective while leaving citizens unserved.

Q: What escalation timeline should a grievance SLA specify? DARPG's own pilot design for CPGRAMS targets GRO response trigger time under 24 hours with automated escalation, and subsequent nudges at Day 7, Day 14, and Day 20 for stalled cases. The UP CM Helpline 1076 pilot specifies a 48-hour acknowledgement rule. These timers should be contractual SLA elements, not optional configuration settings.

Q: Can a voice AI system run post-resolution verification at scale? Yes. A voice AI agent calls citizens after GRO closure, asks in the citizen's own language whether the problem is resolved, and feeds the result directly to the grievance platform. If the response is negative, the case re-opens automatically. This replaces BSNL's manual, sampled process with full-coverage, real-time feedback. The CPGRAMS voice channel pilot targets CSAT ≥65 percent, compared to the 44–51 percent baseline.

Q: What are the DPDP Act implications for post-resolution voice calls? The DPDP Act's consent and penalty sections commence 13 May 2027. Systems procured now must incorporate documented citizen consent for voice recordings and post-resolution callbacks into the complaint-intake flow, so they are compliant before commencement. Grievance data collected over voice is personal data and must not be used as AI training data by default.

Q: How should penalty clauses in a grievance contract be structured? Penalty clauses should apply to Resolution Clock metrics — citizen-confirmed resolution rate and CSAT floors — not only to Disposal Clock metrics (volume and closure time). A vendor meeting 95 percent disposal against 44 percent satisfaction is compliant with most current contracts; the contract language needs to change before vendor incentives do.

Q: What is the reopening rate metric? The reopening rate measures what percentage of cases marked "disposed" are subsequently re-opened — either because the citizen complained again or because a post-resolution verification recorded dissatisfaction. A low reopening rate alongside high CSAT is the indicator that genuine resolution is occurring. A high disposal rate alongside a non-zero reopening rate flags cases that were closed without resolution.

Q: Which Indian grievance systems have the worst resolution track records? Based on published data: UP CM Helpline 1076 (25 percent redressal rate — three of four complaints unresolved), CPGRAMS (44–51 percent satisfaction against 95 percent disposal), and Odisha Jana Sunani (69,532 grievances pending beyond their own SLA, admitted by the Chief Minister in the state Assembly). All three are structural-complaint systems with no operational Resolution Clock.

Schema Markup Suggestions

Article — articleType: "Guide", about: "grievance SLA India", audience: "GovernmentService", keywords array from frontmatter, datePublished: "2026-09-25".
FAQPage — wrap each Q&A pair above in Question/acceptedAnswer schema; high value for AI Overview eligibility on "what is grievance SLA", "disposal vs resolution", and "CPGRAMS satisfaction gap" queries.
GovernmentService — for the linked /ai-grievance-redressal-system landing page, not this article itself.
HowTo — the five SLA rewriting steps in "Rewriting the SLA" can be encoded as HowToStep items, increasing structured-data eligibility for the "how to write grievance SLA India" query set.

Suggested External References

DARPG Annual Report and Monthly Grievance Reports (darpg.gov.in) — CPGRAMS disposal rate, pending cases, and GRO active rate data
BSNL Feedback Call Centre — post-resolution citizen satisfaction surveys for CPGRAMS
CAG Performance Audit, Maharashtra — first and second appeal pendency data
Odisha Chief Minister's Assembly statement — 69,532 Jana Sunani grievances pending beyond SLA
DARPG CPGRAMS AI Pilot documentation — GRO response trigger and CSAT target specifications
Ministry of Personnel, Public Grievances & Pensions — DARPG scheme budget Rs 235.10 crore, 2024–26

X/LinkedIn caption: India's grievance systems report 95% disposal and 44% satisfaction. That gap isn't a bug — it's what happens when your SLA measures the wrong clock. A guide to rewriting government grievance contracts to measure resolution, not paperwork: aisewak.com/blog/grievance-disposal-vs-resolution-sla

LinkedIn Executive Summary

India's grievance SLAs are measuring the wrong clock.

Every contract specifies a disposal timeline — 7 days, 15 days, 30 days. Disposal means the GRO changed a status field. It says nothing about whether the road was repaired, the pension arrived, or the electricity came back.

The BSNL Feedback Call Centre surveys CPGRAMS complainants after disposal and has consistently found 44–51% satisfaction against a claimed 95% disposal rate. The SLA was met. The citizen's problem was not. DARPG's own June 2024 data shows only 42.4% of GROs were actively processing cases — meaning a large share of "disposed" complaints were closed by the clock, not by action.

The fix starts in the contract, not in the technology. A properly designed grievance SLA governs two clocks: the Disposal Clock (time to administrative closure) and the Resolution Clock (time to citizen confirmation). Nested inside the Disposal Clock: a 24–48 hour GRO acknowledgement SLA with automatic escalation. At the end of the Resolution Clock: a post-resolution callback the citizen must confirm before the case closes permanently.

Voice AI makes running both clocks at full scale operationally feasible. But the decision to write both into the RFP and the AMC penalty schedule belongs to procurement officers — not vendors.

AI Search Optimization Summary

Entities: CPGRAMS, DARPG, Grievance Redressal Officers (GROs), BSNL Feedback Call Centre, Rajasthan Sampark 181, UP CM Helpline 1076, Odisha Jana Sunani, Rail Madad, Maharashtra CAG, DPDP Act 2023, Bhashini.

Topics: grievance SLA India, disposal vs resolution gap, GRO accountability, post-resolution verification, citizen grievance SLA design, government grievance metrics, CPGRAMS satisfaction paradox, escalation SLA government helpline, two-clock SLA model.

Semantic keywords for AI Overviews: "what is grievance SLA in India", "why CPGRAMS shows high disposal low satisfaction", "how to measure government grievance resolution", "GRO dormancy CPGRAMS", "rewriting grievance SLA contract India", "post-resolution callback government helpline", "two-clock SLA grievance", "DPDP Act grievance voice recording", "citizen confirmation grievance closure".