Explore IndiaCurrent IndiaTomorrow IndiaSearchReport a problem
India For Tomorrow
[google-translator]Language / भाषा
← Governance library
From the IFT source library

Citizen Feedback System

Text from the existing IFT website. Sources and claims are still under editorial review.

Original source ↗

Section 01

Where the problem happens

Define the failure from the affected person’s journey.

Generic ratings cannot identify the failed stage, and vulnerable users may fear consequences.

Required local context

Record state/UT, district, city/block, village/ward or facility; service or incident; date and reference period; affected group; requested action; failed stage; delay, cost or harm; responsible authority; evidence source; privacy level; and what remains uncertain.

Data reference table

Evidence Snapshot

Read each value with its reporting period, population and limitations. A historical national reference is not a local baseline or proof that an IFT proposal works.

3 source-linked reference records. 3 measurement records still need data and a review of their relevance.

Data references for Citizen Feedback System
SignalReference ValuePeriod / PopulationHow to Read ItSource Status
New grievances received on CPGRAMS

26,15,321 grievances

Historical reference

January–December 2024

CPGRAMS portal; India administrative reporting

Annual new receipts shown in Annex 1 of the official answer.

Limitations: A portal count excludes problems not reported through that route. It is not prevalence of governance failure and should not be compared with disposals as if both represent one new-case cohort.

Ministry of Personnel, Public Grievances & Pensions / DARPG

Official government parliamentary release

Parliament question: Disposal rate of grievance redressal mechanism

Published: 2025-04-02

Publication checked: 2026-11-04

Value, period and coverage checked in publication

Grievances disposed on CPGRAMS

26,45,869 grievances

Historical reference

January–December 2024

CPGRAMS portal; India administrative reporting

Annual disposals include work on a stock of complaints, not only that year’s new receipts.

Limitations: Disposal does not prove satisfaction, service repair or prevention of recurrence. Do not derive a new-complaint success rate from receipts and disposals with different case cohorts.

Ministry of Personnel, Public Grievances & Pensions / DARPG

Official government parliamentary release

Parliament question: Disposal rate of grievance redressal mechanism

Published: 2025-04-02

Publication checked: 2026-11-04

Value, period and coverage checked in publication

Reported average grievance redressal timeline

15 days

Historical reference

February 2025

CPGRAMS; government-reported average redressal timeline

A reported average for the stated month can be a historical process reference.

Limitations: The release does not provide a full waiting-time distribution or an unresolved-case age profile. An average does not establish satisfactory remedy or equal treatment across groups.

Ministry of Personnel, Public Grievances & Pensions / DARPG

Official government parliamentary release

Parliament question: Disposal rate of grievance redressal mechanism

Published: 2025-04-02

Publication checked: 2026-11-04

Value, period and coverage checked in publication

Response coverage

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Problem stage

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Resolution confirmation

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Different surveys, administrative records, estimates and reporting years are not interchangeable. No combined IFT score is calculated from these rows.

Section 02

Why the problem happens

Test the system before blaming a person.

Vague questions

Check process records, capacity, incentives, law, technology, funding and user experience before confirming this hypothesis.

Sampling bias

Check process records, capacity, incentives, law, technology, funding and user experience before confirming this hypothesis.

Identity exposure

Check process records, capacity, incentives, law, technology, funding and user experience before confirming this hypothesis.

Immediate errors, structural constraints, institutional incentives and local conditions may interact. Correlation, a complaint count or a dashboard gap does not by itself establish cause.

Section 03

Evidence

Build a traceable decision record.

  • Question Required proof
  • What happened? Dated case, service or incident record
  • Where and to whom? Administrative level, facility and affected group
  • How large is it? Denominator, period and comparable definition
  • Why did it happen? Process trace, interviews and competing explanations
  • What already exists? Law, scheme, budget, staffing and implementation status
  • Did action work? Baseline, target, result, cost, equity and adverse effects

Official source ≠ verified conclusion. Data freshness, completeness, legal meaning, local resolution and independent review still matter.

Section 04

How the parts work together

What must work together.

Access received

Define owner, lawful authority, standard, capacity, data, public interface, escalation and review.

Time and effort

Unofficial payment

Staff behaviour

Actual resolution

Section 05

A solution suited to India

Design around rights, access and operating reality.

Ask transaction-specific questions through accessible channels and protect privacy.

BOUNDED PILOT

Survey a representative service cohort after closure and publish limitations.

Pre-register the target group, baseline, responsibilities, safeguards, cost, measurement period, escalation route and stop/redesign criteria. Include assisted and offline access where digital exclusion is possible.

Section 06

Roadmap

Move through evidence gates—not announcements.

  • 01 · 0–30 days
  • Map journey, law, owner and immediate harm
    02 · 30–90 days
  • Verify records, bottleneck and affected groups
    03 · 3–9 months
  • Run the bounded pilot with safeguards
    04 · 9–24 months
  • Evaluate outcome, cost, rights and equity
    05 · 2–5 years
  • Integrate capability, finance and institutions065+ years
  • Scale only after transfer and maintenance review

Section 07

How to measure improvement

Measure public outcome and system integrity together.

Response coverage
Baseline → target → actual → difference → decision

Problem stage
Baseline → target → actual → difference → decision

Resolution confirmation
Baseline → target → actual → difference → decision

Retaliation reports
Baseline → target → actual → difference → decision

Corrective actions
Baseline → target → actual → difference → decision

Scale

Outcome improves, safeguards hold and receiving capacity exists.

Modify

Some benefit appears but design, equity, cost or reliability needs repair.

Stop

No credible benefit, unacceptable harm or a better alternative exists.

Section 08

Rights & safeguards

Efficiency cannot erase due process.

  • No high-impact automated decision without accountable human review and appeal
  • Collect and share only purpose-necessary data
  • Protect complainants, witnesses, children and vulnerable people
  • Publish definitions and limitations; never use ranks as political shaming
  • Separate allegation, verification, finding and final legal outcome
  • Keep accessible physical alternatives where digital-only service would exclude

15 questions, answered clearly

Questions about Citizen Feedback System

What does Citizen Feedback System focus on?

Generic ratings cannot identify the failed stage, and vulnerable users may fear consequences.

What changes does the page propose?

Ask transaction-specific questions through accessible channels and protect privacy. Survey a representative service cohort after closure and publish limitations.

Which parts need to work together?

The proposed system connects Access received; Time and effort; Unofficial payment; Staff behaviour; Actual resolution. Assign a responsible team, service standard, handoff and maintenance plan for each part

What local information is needed before taking action?

Record state/UT, district, city/block, village/ward or facility; service or incident; date and reference period; affected group; requested action; failed stage; delay, cost or harm; responsible authority; evidence source; privacy level; and what remains uncertain.

What could be causing the problem?

Possible causes to investigate include Vague questions; Sampling bias; Identity exposure. Treat these as questions to test against local records and experience, rather than confirmed causes in every location.

What evidence should researchers collect?

Keep a dated record of the location, the service or asset that failed, who was affected, the possible cause, the existing owner or project, and the result after action. Link each observation to its source and method. Official source ≠ verified conclusion. Data freshness, completeness, legal meaning, local resolution and independent review still matter.

What could a first trial of Citizen Feedback System look like?

Survey a representative service cohort after closure and publish limitations. Agree the place, responsible team, comparison, safety checks and measurement period before starting. The trial described here is a proposal, not a reported result.

How should improvement be measured?

The page proposes tracking Response coverage; Problem stage; Resolution confirmation; Retaliation reports; Corrective actions. Define each measure, record the starting value and reporting period, then compare later results using the same method. Report who benefits and any harm or uncertainty.

What risks and safeguards need attention?

No high-impact automated decision without accountable human review and appeal. Collect and share only purpose-necessary data. Protect complainants, witnesses, children and vulnerable people. Publish definitions and limitations; never use ranks as political shaming. Separate allegation, verification, finding and final legal outcome. Keep accessible physical alternatives where digital-only service would exclude.

What is the suggested order of work?

Move through evidence gates—not announcements. 0–30 days. Map journey, law, owner and immediate harm; 30–90 days. Verify records, bottleneck and affected groups; 3–9 months. Run the small, controlled trial with safeguards; 9–24 months. Evaluate outcome, cost, rights and equity; 2–5 years. Integrate capability, finance and institutions; 5+ years. Scale only after transfer and maintenance review. These stages are planning ranges. Actual timing depends on local conditions, resources, permissions and delivery capacity.

Who should take responsibility for delivery?

Information Required: the named organisation and accountable local team. Responsibilities must cover Access received; Time and effort; Unofficial payment; Staff behaviour; Actual resolution. Assign an owner for each handoff, record how problems will be escalated, and agree who will fund and maintain the work.

What costs should be checked before approval?

Record state/UT, district, city/block, village/ward or facility; service or incident; date and reference period; affected group; requested action; failed stage; delay, cost or harm; responsible authority; evidence source; privacy level; and what remains uncertain. Some benefit appears but design, equity, cost or reliability needs repair. Information Required: a local cost estimate, funding source and ongoing operating and maintenance budget. Include costs shifted to households or other services when comparing options.

How should access and fairness be checked?

Some benefit appears but design, equity, cost or reliability needs repair. Compare access, costs, safety and results across the groups affected in this location. Record missing information and correct exclusion before expanding the proposal.

When should the approach expand, change or stop?

Scale: Outcome improves, safeguards hold and receiving capacity exists. Modify: Some benefit appears but design, equity, cost or reliability needs repair. Stop: No credible benefit, unacceptable harm or a better alternative exists.

Does this page establish that the proposal has succeeded?

No verified local result should be inferred from the proposal alone. Information Required: a dated starting measurement, later results, costs, affected groups and an independent assessment. The proposed review should examine Response coverage; Problem stage; Resolution confirmation.