Simulated with sample data

Nagar Nigam and Development Authority

Complaints and applications, with an officer deciding

A streetlight complaint after office hours

Ward 14 of a Nagar Nigam (sample)

  1. 9:05 pm A resident calls about a dark streetlight. The assistant says it is automated, takes the landmark and reads it back in Hindi. Citizens are heard after office hours.
  2. 9:06 pm The complaint goes to the ward officer with a 48-hour deadline. Every complaint has an owner from the first minute.
  3. Day 3, 9:10 pm The deadline passes without action, so the complaint escalates to the zonal officer. Nothing sits unowned.
  4. Day 4, 6 pm The light is fixed. The resident gets an automated call confirming it. Citizens know their complaint was acted on.
  5. Day 5, 9 am The commissioner's morning view shows open complaints by ward and which ones escalated. Leaders see where service is slipping, every morning.

A building-plan file with a missing NOC

A development authority (sample)

  1. 11:00 am A building-plan application arrives with its documents. Each one is read and checked against the checklist. Incomplete files are caught on day one, not after weeks in a queue.
  2. 11:05 am The applicant is told exactly what is missing, and a reminder is scheduled. Applicants are not left guessing why their file is stuck.
  3. Day 9 The fire NOC arrives. The planning officer reviews the full file and recommends approval; a senior officer checks and signs. Every approval has two officers behind it.
  4. Day 9 The full file and every decision are in the record, ready for an audit or an RTI request. Transparency is built in, not reconstructed.

Request beta access