How Local Authorities Can Digitise Service Requests

Every Zimbabwean council already runs a service request system; it just runs on phone calls, walk-ins, councillors’ WhatsApp messages and paper. The problem is not intake — residents will always find a way to report a burst main. The problem is what happens next: no single queue, no ownership, no clock, and no way for anyone to know whether the issue was resolved.

Start With the Queue, Not the App

The transformation is a single, shared queue: every request, from every channel, in one place, with an owner, a category and a clock. A portal or mobile channel matters, but it is the third step, not the first. Councils that launch an app without the queue behind it simply digitise their backlog.

A Practical Sequence

1. One Register of Requests

Consolidate intake into one system, even if staff key in phone and walk-in reports manually at first. Assign every request a reference number residents can quote.

2. Categories, Owners and Clocks

Define the request types that matter — water, roads, refuse, street lighting, billing — and give each a responsible section and a target response time. SLA tracking is what turns a list into management information: which requests are at risk, which are breached, and where the bottlenecks actually are.

3. Resident-Facing Channels

Once the queue works, open it up: a mobile-first portal where residents log requests and check status. In the Zimbabwean context, design mobile-first and lightweight — most residents will arrive on a phone, often on constrained data.

4. Close the Loop

The step most systems skip: telling the resident the job is done. Closure notifications are what convert a complaints channel into visible service delivery — and what changes how residents talk about their council.

Pitfalls to Avoid

Launching channels before the internal queue exists; buying a system nobody in the council can administer after the vendor leaves; and treating the project as an ICT purchase rather than an operational change with a technology component. Training and handover matter as much as software.

What This Looks Like in Practice

The service workspaces we build give council teams live SLA dashboards — open cases, at-risk requests, intake by channel, resolution by team — while residents see a simple portal. The technology exists and is deployable in-country; the decisive factor is a council leadership that wants the queue to be visible.