Drainage Connection Management System

Drainage and water are different departments with different engineers, different charge structures and different technical requirements. Sharing one application form would have meant a form where half the fields were irrelevant to whichever connection you were applying for.

They are built as separate portals over the same workflow engine and the same citizen experience, each with its own file numbering series so the two departments' records never mix.

A drainage application captures what the inspecting engineer will need on site: the drain size, from 150mm through 600mm; the pipe material, whether RCC, PVC, stoneware or HDPE; and the estimated run length of the connection.

Capturing these at application time rather than at inspection means the AE arrives already knowing roughly what the job involves, and the estimate can be built against real parameters instead of assumptions.

Because AMC requires drainage before water, the water portal asks every applicant whether they already have a drainage connection. If they do, they upload the receipt and continue. If they do not, they are routed here first.

That policy rule is enforced by the software rather than remembered by an officer, which means an application that would have been rejected three ranks up the chain is stopped at the first step instead.

The rest is deliberately identical: the same five officer roles and thirteen tracked stages, the same site visit with photographs, the same six-head estimate feeding an itemised demand note, the same online payment and receipt.

The same trilingual interface, the same OTP sign-in, the same mandatory GPS capture, and the same officer processing desk with its urgency flags and clickable summary tiles.

Zone and ward auto-populate from Town Planning scheme data, so an applicant selects a zone and the ward fills itself rather than being typed in wrongly.