Water Connection Management System

A water connection application is not a simple request. It has to be checked against Town Planning records, the property has to be physically inspected, charges have to be estimated from pipe size and property classification, and the whole thing has to be signed off by five officers in sequence before anyone can pay for it.

Done on paper, each of those steps is invisible from outside. A citizen who applied in March had no way to learn whether their file was sitting with the Assistant Engineer awaiting a site visit or with the Deputy Municipal Commissioner awaiting signature. The only way to find out was to visit the office and ask. Payment meant a second visit, and collecting the receipt often a third.

Inside the department the picture was no better. There was no way to see which files had been sitting untouched for a fortnight, which officer was carrying the heaviest load, or where in the chain applications were consistently stalling.

The system had to serve two audiences whose needs barely overlap. A citizen uses it perhaps once in their life, on a phone, possibly in Gujarati, and needs to be guided through a process they do not understand. An officer uses it every working day, on a desktop, and needs to move through dozens of files quickly without the interface getting in the way.

We built them as two distinct experiences over one workflow engine. The citizen side is a guided, step-by-step application. The officer side is a split-panel processing desk built for speed — file list on the left, full detail on the right, and an action panel that changes to show only what this officer can actually do at this stage.

The application moves through thirteen tracked stages and five officer roles. The Assistant City Engineer receives it and delegates to an Assistant Engineer. The AE schedules a site visit, records findings with photographs, and builds a technical estimate from six separate charge heads. The ACE reviews that report and forwards it up. The Deputy City Engineer applies technical review, the Additional City Engineer administrative review, and the Deputy Municipal Commissioner gives final approval.

Every one of those transitions is recorded with the officer's name, a timestamp and their remarks, and every one of them is visible to the citizen as a coloured step on a progress tracker. Returns are handled as first-class transitions rather than exceptions: any reviewing officer can send a file back down the chain, and remarks are mandatory when they do.

One deliberate asymmetry: the citizen is not notified when a file moves backwards between officers. Internal review churn is normal and telling an applicant their file was returned twice would alarm them without informing them. They are notified on the things that affect them — receipt, demand, approval, rejection.

The interface runs in English, Gujarati and Hindi, switchable at any moment from the header. Every label, menu, validation message and error string is translated — not just the marketing surface.

Data entered by people stays in the language it was typed in. An officer's remark written in Gujarati is not machine-translated for an English-language reader, because a mistranslated remark on a statutory file is worse than an untranslated one.

Sign-in uses a one-time password rather than a password, for both citizens and officers. Nobody has to remember credentials for a portal they use once, and there is no password for an officer to write on a desk pad. Attempts are rate-limited and the account locks after repeated failures.

GPS capture is mandatory on the application. The applicant taps a button, confirms the browser prompt, and drags a pin to the exact connection point — which is what lets the inspecting engineer find the property without a phone call.

Payment happens against an itemised demand note showing every charge head separately: base charge, supervision, stimulus, contingency, reinforcement and refundable security deposit. The citizen pays through the gateway and downloads a receipt. No counter, no queue.

Officers open a dashboard showing exactly what is waiting for them, with files pending more than seven days flagged in red. Every summary figure is clickable and opens the exact list behind it, so the number on the tile and the files it counts can never disagree. A stage-distribution chart shows where work is piling up across the ward.

Because every action was already recorded as part of doing the work, reporting came free: applications by stage, by zone, by ward, by date, and officer-wise pending workload across the zone.