Case study

Building a citizen app for a ward councillor: lessons learned

Notes from building the Parshad Council App — Voter ID + OTP login, a ward feed, complaint tracking and an admin dashboard — on a tight budget and timeline.

By Anand Dubey8 min read

Building a citizen app for a ward councillor: lessons learned — featured image

A ward councillor wanted one official channel to every registered voter in the ward — somewhere to post work updates and events, and somewhere for citizens to raise complaints that would not get lost. The budget and timeline were fixed, so every decision had to earn its place.

Only real voters can sign in

There is no public sign-up. A citizen enters their Voter ID; if it exists in the ward's voter list, a one-time password is sent and they are in. If not, the app shows the office contact number instead. This kept the community trusted and removed the need for moderation of fake accounts.

Complaints become trackable enquiries

Every complaint gets a number, a category and a status: Received, In progress or Resolved. Citizens see the timeline and the office's replies. For the office, a filtered inbox replaced scattered phone calls and WhatsApp messages.

  • Category, subject, details and an optional photo
  • A visible three-step status timeline
  • Office replies inside the enquiry
  • Push notification when the status changes

A web dashboard for the office

The councillor's staff publish work posts, announcements and events, choose the audience, schedule posts and send push notifications. They also import the voter list from CSV and approve citizen posts before they appear in the feed.

What I would repeat

  1. Write the PRD before writing code — it settled most debates early.
  2. Keep non-goals explicit: no chat between citizens, no payments, no maps in v1.
  3. Ship a demo mode with sample data so stakeholders can try it on day one.
  4. Design for low-cost Android phones first.

FAQ

Can this be adapted for other wards or organisations?

Yes. The same pattern — verified members, a feed, trackable requests and an admin dashboard — fits housing societies, schools and associations.

How is voter data protected?

Access is restricted by role, secrets never ship in the app, and citizens can only read their own details and requests.

Need help with this?

The same thinking from this article, applied to your project — starting with requirement analysis.

Contact

Tell me what you're working on.

A rough outline is enough to start. I'll reply with a thoughtful next step.

Hi! Who am I talking to?

What do you need help with?

Service needed

What's your estimated budget?

Project budget

What kind of team are you?

Team type

Tell me a little about your project.

Your project details are only used to respond to your enquiry.
If form delivery is unavailable, your details will stay in the form.