See the evidence across India
Bring available service indicators into a common view with their source, period and geographic coverage. A missing observation remains a visible gap.
Independent civic platform · Better India. Together
Loading JANNEEV…
Preparing this page and its available evidence.
JANNEEV FOR PUBLIC INSTITUTIONS
Civic observability, grouped issues and department comparisons—built around evidence that can be traced, questioned and improved.
Independent civic technology. Government partnerships and outcomes must be established through an agreed programme.
What is happening, where—and how do we know?
Which signals describe one problem, and who owns the response?
What changed, and does the evidence support the outcome?
A CLEARER VIEW OF CIVIC SERVICES
Help teams understand the problem, prioritise a response and explain the result. The pilot must demonstrate the value.
Bring available service indicators into a common view with their source, period and geographic coverage. A missing observation remains a visible gap.
Group reviewed reports about the same issue so repeated citizen signals add context without multiplying the issue count.
Compare like services, places and time windows. Show eligible case counts and keep measured outcomes separate from community feedback.
NATIONAL REACH · LOCAL DEPTH
Ask the same questions about Karnataka, Delhi, Punjab or Maharashtra. The answer should show what is known, what is comparable and what is missing.
Open a state’s stored measurements and reviewed issue evidence, or compare states side by side. Geographic coverage across all 36 states and union territories does not mean all services have comparable data.
Use suitable official indicators and published service conditions with a disclosed period, unit and coverage. Existing source readings, archives and reference statistics provide selected evidence; a complete comparable national baseline is still to be established.
Inspect available sourcesWhere reviewed cases exist, connect grouped issues to responsible departments, actual filing references and supported outcomes. Publish response measures only when the evidence qualifies.
Open the evidence-based dashboardRATINGS THAT CAN BE EXPLAINED
A useful rating needs a defensible denominator. More reports can reflect higher participation as well as more problems.
Service, jurisdiction, governance level and reporting window.
Case counts, source coverage, exclusions and data freshness.
Measured service response and community feedback side by side.
Insufficient evidence stays unrated; missing data never becomes a good score.
Current departmental outcomes are based on operator-recorded filings with receipt evidence. They are not official government rankings. National rankings require suitable comparable outcome data and an agreed method.
A TRACEABLE OPERATIONAL RECORD
Reporting supports the evidence base. Review, grouping and a shared timeline connect a local concern to the response without exposing the citizen's private original.
Follow a fictional issueOperators prepare a public summary and check whether reports describe the same problem.
With citizen consent, an operator files through an approved channel and records the actual government reference.
Track status, receipt evidence, citizen feedback and disputes in one history.
Current delivery model: government filing and status recording are manual operator actions. Automatic government connections, emergency dispatch and social publishing are not activated integrations.
PROPOSED DEPARTMENT OFFERING
Citizen participation is intended to remain free. Departments would fund the software and agreed implementation services.
Configure the services, jurisdictions, grouped-issue views and rating definitions that a department needs.
Agree source permissions and coverage, then connect suitable exports or APIs with traceable import records.
Agree hosting, rollout, staff training and ongoing support with the responsible team.
Scope, commercial terms and service commitments would be agreed with the partner.
LIVE SERVICE CHECK
Checking the current service configuration…
These checks describe service configuration. They do not certify national data coverage, government integration, security compliance or readiness for a particular department. Review source access and coverage
A PROPOSED 90-DAY VALIDATION
Validate deeper evidence in one city, a few wards and two services. The national product remains the broader ambition; the pilot establishes whether its methods support real decisions.
Select one city, a few wards and two services. Confirm the sources, reporting period, coverage, comparison rules, responsible teams and baseline.
Review and group recurring issues, connect verified filing references, and follow departmental response. Check missing data and disputed outcomes every week.
Assess evidence quality, whether the insights changed decisions, and how response compares with the baseline. Publish the limits alongside the findings.
| Question | Measure | Proposed success criterion |
|---|---|---|
| Evidence quality | Source traceability, freshness, missing fields and coverage by service and area. | Agreed coverage and quality thresholds are met; gaps remain visible. |
| Grouping quality | Operator-reviewed duplicate groups, false merges and time spent reviewing repeated reports. | Related reports are grouped accurately without hiding distinct problems. |
| Fair comparisons | Comparable jurisdiction, service, reporting window, eligible case count and outcome evidence. | Every published comparison has a disclosed basis; weak samples remain unrated. |
| Actionability | Decisions or work prioritisation linked to a documented insight and a named owner. | Teams can demonstrate how the evidence informed a real action. |
| Service response | Time to acknowledgement, overdue cases, handling effort and supported resolution records. | Results improve against the agreed baseline or explain why they did not. |
| Citizen experience | Resolution confirmation, disputes, reopening and feedback response rates. | Community feedback is visible separately from measured service outcomes. |
Set numerical targets, exclusions and evaluation ownership with the pilot partner before starting. No percentage improvement, government endorsement or purchasing commitment is assumed.
BEFORE LIVE GOVERNMENT USE
The current deployment is a pilot architecture. Each buyer's requirements need explicit assessment and agreement.
Permitted source reuse, consent, retention, deletion, audit access and handling of personal information.
Required hosting location, capacity, backup and recovery, incident handling and independent security review.
Named departments and operators, approved filing channels, support, escalation and exit/export arrangements.
Field validation on mobile devices, assistive technology, local languages and slow connections.
These are items to verify, not certifications or promised service levels. Read the current privacy notice.
TAKE THE DISCUSSION FORWARD
Use the brief to agree the services, evidence, responsibilities and evaluation. No sign-in is required to explore the example or download the proposal.