CITIZEN
The storyCitizen GraphProblemTry itSharing
How Citizen works
Open demo

What if public services worked the first time?

Your verified documents stay connected. Services open with your details already filled in. Every result returns to the same record. No form starts from zero.

Open demoGitHub

How this started

I did not know UMANG existed.

The government does many things, and each thing arrives with its own name: a scheme, a portal, an app, a deadline. Names pile up faster than anyone can learn them. By the time a message reaches you, it has often changed shape or lost its meaning.

UMANG already puts hundreds of services behind one door. It still asks you to arrive knowing what you need: recognise the scheme, find the department, decide whether it matters to you. Most people never get that far.

Citizen is our answer: a gazette with an audience of one. Everything happening in your name, from payments to notices to applications and benefits, lands in one brief, with suggestions for what could help you next.

  1. 01

    What changed?

    Notices, payments, applications and document updates.

  2. 02

    What applies to me?

    Relevant obligations, benefits and services, with the reason shown.

  3. 03

    What should I do next?

    The right action, using records already connected to you.

Home in this demo already works this way. It shows what changed and what could help you before you ask.

A personal public-service gazette is a private brief for one person, not an official government publication.

Independent prototype. Not affiliated with or endorsed by UMANG, EPFO, DigiLocker or any government authority. All service responses are simulated.

The Citizen Graph

One citizen. Every connected fact.

This is Arjun's record shown as a graph. Identity sits at the centre. Family, work, assets, documents and government history connect around it.
Citizen recordArjun Sharma24 active connections
Family2
Property1
Address1
Work1
Business1
Vehicle1
Documents7
Benefits2
Applications1
Obligations5
Notices3
Identity arrives with evidence.One address and seven documents. Later services reuse them instead of asking again.
The record expands into a life.Family, employment, business, vehicle and property relationships give each fact context.
Services read the same context.Benefits, applications, payments and notices reuse the same details.
Every result lands back in your record.A payment removes a due amount, creates a receipt and joins the same history that Home shows.
  1. Identity arrives with evidence. One address and seven documents. Later services reuse them instead of asking again.
  2. The record expands into a life. Family, employment, business, vehicle and property relationships give each fact context.
  3. Services read the same context. Benefits, applications, payments and notices reuse the same details.
  4. Every result lands back in your record. A payment removes a due amount, creates a receipt and joins the same history that Home shows.
Arjun's record · 11 groups · 24 linksScroll to build the graphGraph built

Where design stops

Day 40

A claim can still be pending behind a beautiful status screen.

A better screen cannot clear a backlog.

If the cause is a queue of officers, a policy, limited staff or a department database, a redesign cannot fix it. So Citizen sticks to what a record can do.

An interface cannot

  • Change policy or eligibility rules
  • Add officers or processing capacity
  • Repair a department database
  • Approve a claim waiting on human judgment

What Citizen changes

  • Carry verified evidence into the next service
  • Show the current state and next available action
  • Stop each task from restarting at zero
  • Return receipts, permissions and history to one record

Built for the Build What Moves India hackathon by Varun Mayya.

The obvious fixes only go so far.

Cleaner screens, chat boxes and dashboards each help a little. None of them fixes the real problem: every service still starts from zero.

Simpler interfaceMakes one screen easier
Ask in your own wordsTakes you to the right service
DashboardSummarises tasks that already exist
What holds it together

Citizen Graph

Your documents, records and permissions follow you from one service to the next. Each service picks up where the last one ended.

Visit the Build What Moves India hackathon

Choose a problem. Watch the graph respond.

This is the Citizen Graph working. Your details are entered once. The right service uses them. Every screen that needs the result gets it.

Situation

My July EPF contribution is missing.

Connected evidence

  • UAN XXXXXX7890
  • Meridian Tech employment
  • ₹21,600 contribution notice
Citizen record
ASArjun Sharma
Identity, relationships, work, assets, obligations and permissions stay connected.
Service actionRegister an EPFO grievance

Graph updates

  • Home shows Submitted
  • Grievance reference saved
  • Activity records the change

Now watch it work.

Each demo below works on the same record. Change one thing and every screen shows the result.

  1. 01A missing EPFO contribution becomes a grievance. Home shows it as Submitted.
  2. 02A PAN mismatch reuses Aadhaar evidence instead of asking for it again.
  3. 03A paid challan leaves Money and creates a receipt in Documents.
  4. 04Sharing needs consent, and family access can be removed anytime.

All people and records are fictional. Government responses are simulated.

How Citizen works

You control what gets shared.

You decide who sees what, and for what purpose. Consent stays visible and you can take it back anytime.

  • Ask before sharing records
  • Use approved government connections
  • Show who accessed what
  • Let people correct mistakes

Open a profile and try it.

Open demo

Not affiliated with the Government of India or any state authority.

How Citizen worksGitHubMusic: Bombay Summer