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.
| Signal | Reference Value | Period / Population | How to Read It | Source 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.
Evidence coverage and review log (CSV) · Structured evidence register (JSON)
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
