Section 01
Where the problem happens
Define the failure from the affected person’s journey.
Country labels oversimplify institutions and can hide trade-offs, history and implementation capacity.
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.
5 measurement records still need data and a review of their relevance.
| Signal | Reference Value | Period / Population | How to Read It | Source Status |
|---|---|---|---|---|
| Evidence comparability | 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 |
| Legal fit | 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 |
| Capacity fit | 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 |
| Safeguards | 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 |
| Adopt/modify/reject | 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.
Headline benchmarking
Check process records, capacity, incentives, law, technology, funding and user experience before confirming this hypothesis.
Non-comparable evidence
Check process records, capacity, incentives, law, technology, funding and user experience before confirming this hypothesis.
Legal/context mismatch
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.
Singapore and Estonia
Define owner, lawful authority, standard, capacity, data, public interface, escalation and review.
Denmark and New Zealand
Finland and Japan
Germany and Netherlands
United Kingdom and Switzerland
Section 05
A solution suited to India
Design around rights, access and operating reality.
Compare a precise problem, mechanism, enabling conditions, cost, rights safeguards and Indian alternatives.
BOUNDED PILOT
Run one India-fit comparison before any cross-country recommendation.
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.
Evidence comparability
Baseline → target → actual → difference → decision
Legal fit
Baseline → target → actual → difference → decision
Capacity fit
Baseline → target → actual → difference → decision
Safeguards
Baseline → target → actual → difference → decision
Adopt/modify/reject
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