IRAH
GRAMSETU / GOVERNMENT PLANNING

Plan better.
Track delivery.

A shared platform for ministries to compare what people need, what already exists and what still needs to be delivered.

FIELDVerified evidence
DEPARTMENTAccountable action
CITIZENService outcome
ONE PLATFORM / DEPARTMENT-SPECIFIC ACCESS

Need. Existing provision. Gap.

Connect ministry APIs and legacy records. Check them against citizen feedback and officer surveys, then plan and track the next action.

ILLUSTRATIVE DATA · NOT GOVERNMENT RECORDS

Compare household surveys, connection records and sanctioned works.

Required120households
Already served80Recorded provision
Delivery gap40Includes 25 pending / sanctioned

Next decisionVerify the 25 funded connections before proposing work for the remaining 15 households.

01 / SHARED DATA

Connect and verify

APIs, legacy records and field surveys feed a common data foundation with source history and department permissions.

02 / DIGITAL TWIN

Plan together

Map existing assets and proposed work using available GIS and drone imagery. Flag service gaps and possible duplicate funding for review.

03 / DELIVERY

Track the result

Assign an owner, deadline and evidence requirement. Compare completion with citizen feedback and the original need.

Citizen360 is the household module: family profiles, benefits received, pending applications and citizen demands within the broader GramSetu platform.

Proposed platform and illustrative examples. Onboarding requires authorised data access, mapping, rule validation and survey checks; integrations and outcomes must be verified in a pilot.

02 / SPATIAL SERVICE STORYHOUSEHOLD · VILLAGE · DEPARTMENT

A citizen's story is also a geographic story.

Follow one illustrative rural household across scheme benefits and field verification. Citizen360 is GramSetu’s household module. No real citizen data is shown.

HOUSEHOLD 004 ● DEMO
GEO-TAGGED HOUSEHOLD / DEMO

What has been received? What is still pending?

Water connectionVerification recorded
Housing supportReview needed
Field visitPending verification
Open Citizen 360 journey ↗
THE PUBLIC-SERVICE JOURNEY

A service request should not vanish between offices.

The citizen needs an answer, the field worker needs an assigned action, and the department needs verified evidence to close the case.

CITIZEN / FIELD STAFF
→
CASE & ELIGIBILITY
→
DEPARTMENT WORKFLOW
→
VERIFIED OUTCOME
GEOGRAPHIC DELIVERY

A national architecture must work in the last village.

Create a common core for security and records, but allow state rules, local languages, offline visits and departmental ownership to vary.

ILLUSTRATIVE · NETWORK MODEL

Multi-region deployments

Configurable language, policy rules, user permissions and operating models.

Offline-first field applications

Capture evidence, verify records and synchronise safely when connectivity returns.

Operational command views

Find service delays, geographic bottlenecks and exceptions without losing the underlying evidence.

PROCUREMENT-READY THINKING

Procurement, ownership and operations matter as much as code.

Proposals should define data custodians, hosting, interoperability, accessibility, security reviews, training, operating support and transition obligations.

01

Problem note

Define the gap and current systems.

02

Technical discovery

Confirm existing platforms, data and integration permissions.

03

Controlled PoC

Evaluate capability under agreed safeguards.

04

Scale pathway

Support procurement, rollout and service continuity.

CITIZEN SERVICE JOURNEY

Follow one request from doorstep to resolution.

Government systems need more than beautiful dashboards. Each application should maintain eligibility evidence, field verification and a traceable resolution status.

01 / INTAKE

Capture a request

Collect the citizen's request through a web, mobile or assisted channel. Verify consent and required details.

02 / CHECK

Match official records

Check against existing schemes or registers before opening new tasks or duplicating benefits.

03 / FIELD

Verify the reality

Route exceptions for authorised field checks with evidence, timestamps and review.

04 / CLOSE

Explain the outcome

Record action ownership, dates, service status and a citizen-readable next step.