What does public
documentation state?

The question is: for one clearly scoped public-service route, how many of six practical expectations are stated in public evidence?

The one number: cells stated out of six, per service and jurisdiction.

Benchmark version 0.1

Cross-city pilot

Same scope, different public records.

Rows are grouped by service. State words and symbols make the distinctions readable without relying on colour.

● stated◐ mentioned○ absent

Birth certificate

Jurisdiction	Cost	Documents	Eligibility	Time	Owner	After submission	Stated of 6	Source	As of	Links
Bengaluru, Karnataka, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Bengaluru, Karnataka, IndiaMethod comparison	mentioned	absent	mentioned	mentioned	mentioned	absent	0of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-28	Scorecard JSON ↗Atlas entry →
Chennai, Tamil Nadu, India	stated	mentioned	stated	stated	stated	mentioned	4of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Delhi, NCT of Delhi, India	stated	stated	stated	stated	stated	mentioned	5of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Hyderabad, Telangana, India	stated	mentioned	stated	stated	stated	stated	5of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Mumbai, Maharashtra, India	stated	mentioned	stated	mentioned	stated	stated	4of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗

Birth certificate across the pilot jurisdictions.

The authored and reviewed-regex source values measure different things; the reviewed-regex row is retained as a method comparison rather than dropped.

Property-tax payment

Jurisdiction	Cost	Documents	Eligibility	Time	Owner	After submission	Stated of 6	Source	As of	Links
Bengaluru, Karnataka, India	stated	absent	stated	mentioned	mentioned	stated	3of 6	Comparable · authored	2026-09-05	Scorecard JSON ↗Atlas entry →
Chennai, Tamil Nadu, India	stated	mentioned	stated	mentioned	stated	stated	4of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Delhi, NCT of Delhi, India	stated	mentioned	stated	stated	mentioned	stated	4of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Hyderabad, Telangana, India	mentioned	absent	stated	mentioned	stated	stated	3of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Mumbai, Maharashtra, India	stated	mentioned	stated	mentioned	stated	mentioned	3of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗

Property-tax payment across the pilot jurisdictions.

Water connection

Jurisdiction	Cost	Documents	Eligibility	Time	Owner	After submission	Stated of 6	Source	As of	Links
Bengaluru, Karnataka, India	mentioned	stated	stated	mentioned	mentioned	stated	3of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Bengaluru, Karnataka, IndiaMethod comparison	stated	stated	mentioned	absent	absent	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →
Chennai, Tamil Nadu, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Delhi, NCT of Delhi, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Hyderabad, Telangana, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗
Mumbai, Maharashtra, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗

Water connection across the pilot jurisdictions.

The authored and reviewed-regex source values measure different things; the reviewed-regex row is retained as a method comparison rather than dropped.

Bengaluru directory

All seventeen Bengaluru services.

This directory is not the headline comparison. It keeps the original and later scorecards reachable, with each row marked by its source.

Jurisdiction	Cost	Documents	Eligibility	Time	Owner	After submission	Stated of 6	Source	As of	Links
Bengaluru, Karnataka, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-05	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	mentioned	stated	absent	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-31	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	absent	mentioned	mentioned	mentioned	absent	0of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-28	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	mentioned	stated	mentioned	mentioned	2of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-31	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	mentioned	stated	stated	stated	stated	4of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-28	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	stated	stated	mentioned	absent	mentioned	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	mentioned	stated	absent	absent	absent	1of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-31	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	absent	absent	stated	mentioned	2of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-31	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	mentioned	stated	absent	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	stated	stated	stated	stated	5of 6	Comparable · authored	2026-09-06	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	stated	stated	stated	stated	stated	stated	6of 6	Comparable · authored	2026-09-04	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	stated	absent	mentioned	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-31	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	stated	absent	stated	mentioned	mentioned	stated	3of 6	Comparable · authored	2026-09-05	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	mentioned	stated	mentioned	stated	mentioned	2of 6	Comparable · authored	2026-09-05	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	stated	mentioned	stated	mentioned	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	mentioned	mentioned	absent	mentioned	absent	mentioned	0of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →
Bengaluru, Karnataka, India	stated	stated	mentioned	absent	absent	stated	3of 6	Reviewed extraction over deep ledger · reviewed-regex	2026-08-30	Scorecard JSON ↗Atlas entry →

All Bengaluru scorecards, marked by source.

Method and limits

Bounded public-source legibility.

Grid-only

Grid-only mode uses one official-source pass, a light audit of the six cells, and a scorecard.

It is the scaling and cross-jurisdiction unit.

Deep ledger

Deep-ledger mode uses official-source, public-workflow, citizen-evidence, integration, and a separate fresh audit.

It includes nodes, edges, roadblocks, journeys, and portal records; use it for pilot sites and disputed services.

Login boundary

Personal case data behind login is private by right, not a documentation failure.

Desk research, no counter visited.

A structured, preregistered comparison, not a statistical study.

Read the benchmark specification ↗