Reading a Ward Development Record Without Getting Lost

A ward development record rarely arrives as a single document. It's spread across an approval minute, a budget line, a procurement notice, maybe a site visit report, and finally a completion notice — each filed at a different time, sometimes by a different office. The temptation is to grab whichever one is easiest to find and treat it as the whole story. It isn't.

The method we teach starts with picking one project and deciding, in advance, which stages you expect to find published. In most Kenyan counties that means the ward committee's initial resolution, the county assembly's budget allocation, and a procurement award. Not every stage will be public, and that gap is itself worth noting rather than glossing over.

Starting with the resolution, not the rumour

Residents will often tell you a project is stalled or has vanished before you've seen a single document. That's a useful lead, not a fact. Find the ward committee resolution first — it tells you what was actually approved, for how much, and under whose authority. Everything after that is measured against this starting point.

"The resolution is your anchor. If a claim about a project doesn't match what was actually approved, that mismatch is often the real story."

Following the money without assuming the worst

Once you have the approved figure, the budget and procurement stages tell you whether spending matches intent. Discrepancies happen for ordinary reasons — price changes, phased funding, contractor delays — as often as for troubling ones. Note every discrepancy, but hold off on a conclusion until you've asked the relevant office to explain it.

This is where sessions with reporters tend to slow down, and that's fine. Reading procurement notices takes patience. A single figure that doesn't reconcile is worth a phone call before it's worth a headline.

By the time you reach the completion notice, you should be able to lay the whole record out chronologically and see, at a glance, where documentation is thin. That gap map is often more useful to publish than a premature verdict on whether the project succeeded.