Appendix I · Digital companion · all tools

Broken services in your ward

Appendix I: The Local Government Ward Ledger Template

Local government becomes real when citizens can see who is responsible for the street, drain, light, park, waste, market, road, water point, footpath, public toilet, school site, clinic site, and neighborhood complaint. Without a visible local ledger, the citizen is forced into rumor, patronage, repeated visits, and political brokerage. A ward ledger is the simplest practical instrument for making the republic visible at street level.

This template is for local governments, ward offices, municipal bodies, citizen groups, youth teams, journalists, universities, neighborhood associations, religious institutions, and reform teams. Its purpose is to create a public record of local responsibilities, budgets, projects, contractors, complaints, public spaces, and service performance.

A ward ledger should answer one question clearly: when a local service fails, where does the citizen go, what record is created, and who must respond?

Ward Profile Record

Every ward should have a basic public profile. Citizens should not have to guess the boundaries, population, offices, elected representatives, responsible departments, or service authorities.

• The ward profile should include:
• Ward name or number.
• Boundary map.
• Estimated population.
• Major neighborhoods.
• Elected representative.
• Ward office location.
• Responsible municipal department.
• Responsible officers by designation.
• Public schools in ward.
• Public clinics or health facilities in ward.
• Parks and playgrounds.
• Public markets.
• Major roads.
• Drainage assets.
• Waste collection routes.
• Streetlight zones.
• Water and sewerage responsibility.
• Public facility land.
• Complaint submission points.
• Monthly public meeting schedule, if any.

This profile should be posted publicly and updated regularly. A citizen cannot hold a ward accountable if the ward itself is not legible.

Ward Budget Record

Local democracy is weak when citizens cannot see local money. Each ward should publish a simple budget record showing what funds were allocated, received, spent, pending, or transferred.

• The ward budget record should include:
• Total allocation.
• Funds received.
• Funds spent.
• Funds pending.
• Source of funds.
• Salary and administrative cost where relevant.
• Maintenance budget.
• Development budget.
• Emergency budget.
• Project-specific funds.
• Ward-level revenue where applicable.
• Unspent funds.
• Reasons for unspent funds.
• Date of last update.

Citizens do not need a complex financial statement to begin. They need to know how much money was available and what was done with it.

Local Project Record

Every public project in the ward should have a record. A project should not exist only as a rumor, a political announcement, or a contractor's activity. The public should know what is being built or repaired, who is doing it, what it costs, and when it should be finished.

• The local project record should include:
• Project name.
• Location.
• Purpose.
• Approving authority.
• Budget.
• Contractor name.
• Beneficial ownership where legally required.
• Contract value.
• Start date.
• Expected completion date.
• Current status.
• Scope of work.
• Supervising officer.
• Inspection date.
• Payment status.
• Variation or cost increase.
• Citizen complaint route.
• Photographs before, during, and after where appropriate.
• A project without a public record is an invitation to leakage, poor quality, and abandonment.

Project Board Standard

Every visible project should display a project board at the site. The board should be large enough to read, written in public language, and placed where residents can see it.

• The project board should show:
• Project name.
• Public authority.
• Contractor.
• Cost.
• Scope.
• Start date.
• Completion date.
• Supervising officer or office.
• Complaint number or contact.

The project board is not decoration but a public notice that the work belongs to citizens. A missing project board should be treated as a warning sign.

Maintenance Record

Local government often prefers new projects because they can be inaugurated. Maintenance is less glamorous but more important for daily life. A ward ledger should show maintenance responsibilities and schedules.

• The maintenance record should include:
• Road maintenance schedule.
• Drain cleaning schedule.
• Streetlight inspection schedule.
• Waste collection schedule.
• Park maintenance schedule.
• Public toilet maintenance schedule.
• Market cleaning schedule.
• Footpath repair schedule.
• Tree maintenance or planting schedule.
• Water and sewerage maintenance coordination.
• Emergency maintenance requests.
• Maintenance contractor or responsible unit.
• Completion status.
• Maintenance protects public value. A city that builds but does not maintain is staging decay.

Drainage and Flood Risk Record

Drainage failure is one of the most visible forms of local government failure. It affects health, mobility, property, commerce, and dignity.

• The drainage record should include:
• Major drains in ward.
• Minor drains and channels.
• Cleaning schedule.
• Last cleaning date.
• Blockage points.
• Encroachment points.
• Flood-prone streets.
• Responsible department.
• Contractor or maintenance team.
• Complaints received.
• Complaints resolved.
• Pre-monsoon inspection status.
• Emergency response plan.
• If a ward floods every year at the same points, the problem is not surprise but recorded neglect.

Waste Collection Record

Waste collection is one of the basic tests of local government. A ward should publish its waste collection system in a way residents can verify.

• The waste record should include:
• Collection routes.
• Collection days.
• Collection times.
• Vehicles assigned.
• Staff or contractor responsible.
• Waste transfer point.
• Missed collection complaints.
• Complaint response time.
• Illegal dumping points.
• Market waste arrangements.
• Special waste handling where applicable.
• Monthly performance summary.
• When residents know the route and schedule, failure becomes visible. Without a schedule, every complaint becomes anecdote.

Streetlight Record

• Streetlights affect safety, mobility, women, children, elderly citizens, businesses, and public confidence.
• The streetlight record should include:
• Number of streetlights.
• Locations or zones.
• Functional lights.
• Non-functional lights.
• Last inspection date.
• Repair requests.
• Average repair time.
• Contractor or responsible unit.
• Budget for repair.
• High-risk dark spots.
• Complaint route.
• A broken streetlight should not require a political call. It should require a complaint number and a repair timeline.

Road and Footpath Record

• Roads and footpaths are public mobility infrastructure. A ward ledger should track their condition and repair status.
• The road and footpath record should include:
• Road name or segment.
• Condition rating.
• Potholes reported.
• Repair date.
• Repair contractor.
• Cost.
• Inspection status.
• Repeated failure locations.
• Footpath encroachment.
• Footpath damage.
• Accessibility issues for disabled citizens.
• Pedestrian safety concerns.
• Public complaints.

Footpaths should not be treated as leftover space. They are essential public infrastructure, especially for the poor, elderly, children, and women.

Public Space and Park Record

Parks, playgrounds, libraries, community halls, public toilets, open spaces, and public squares are the physical form of common citizenship. They must be inventoried and protected.

• The public space record should include:
• Name of public space.
• Location.
• Legal status.
• Size.
• Current use.
• Maintenance responsibility.
• Budget.
• Encroachment status.
• Lease or private use, if any.
• Facilities available.
• Lighting.
• Safety complaints.
• Accessibility.
• Last inspection.
• Citizen committee involvement where applicable.

A public park that exists only in a plan but not in usable condition should be recorded as a service failure.

Encroachment Record

Encroachment should be recorded with care and proportion. The ward ledger should distinguish between different types of encroachment and avoid selective enforcement.

• The encroachment record should include:
• Location.
• Type of public asset affected.
• Nature of encroachment.
• Residential, commercial, political, religious, institutional, or mixed.
• Date first recorded.
• Whether vulnerable households are involved.
• Whether organized commercial benefit is involved.
• Whether public safety, drainage, footpath, road, park, or facility use is affected.
• Notice issued.
• Action taken.
• Court status.
• Regularization or relocation issue.
• Responsible authority.
• The purpose is not to criminalize poverty but to stop public space from being quietly captured.

Local Complaint Record

• Every ward office should maintain a complaint record. A complaint without a tracking number is easily ignored.
• The complaint record should include:
• Complaint number.
• Date received.
• Complainant reference, with privacy protection where needed.
• Complaint category.
• Location.
• Description.
• Responsible department.
• Expected response time.
• Action taken.
• Status.
• Completion date.
• Reason for delay.
• Appeal or escalation route.

Complaint categories may include waste, drains, streetlights, roads, parks, water, sewerage, encroachment, building safety, public toilets, market management, animal control, noise, unsafe construction, public space misuse, and other local issues.

Complaint Response Standards

• Different complaints require different response times. A ward ledger should publish response standards.
• Possible categories:
• Emergency public safety issue.
• Drain blockage causing flooding.
• Open manhole or dangerous road hazard.
• Streetlight failure in high-risk area.
• Waste missed collection.
• Park damage.
• Routine road repair.
• Footpath obstruction.
• Encroachment complaint.
• Building safety concern.
• Water or sewerage overflow.

Each category should have an expected first response time and expected resolution time where feasible. If the issue belongs to another department, the ward office should refer it with a record, not dismiss the citizen.

Building and Safety Record

• Unsafe construction and building violations can become disasters. Local government should track building-related complaints and approvals where within its jurisdiction.
• The building and safety record should include:
• Building complaint number.
• Location.
• Nature of complaint.
• Unsafe structure.
• Illegal construction.
• Blocked drain or footpath.
• Fire safety issue.
• Setback violation.
• Public land issue.
• Inspection date.
• Notice issued.
• Action taken.
• Court status.
• Responsible authority.
• Building control should not be used only against the weak. High-risk and high-capacity violations must be visible.

Public Facility Site Record

Many wards have sites reserved for schools, clinics, parks, markets, libraries, public toilets, or community centers. These sites can be quietly lost if not tracked.

• The public facility site record should include:
• Site location.
• Reserved purpose.
• Legal status.
• Current use.
• Encroachment status.
• Conversion proposal, if any.
• Responsible authority.
• Community need.
• Last inspection.
• Complaint route.
• Public facility land should not be treated as vacant land waiting for private use; it is future public capacity.

Ward Public Meeting Record

• Ward-level public meetings should produce records, not only speeches. A meeting without minutes becomes performance.
• The public meeting record should include:
• Date.
• Location.
• Officials present.
• Citizens present.
• Issues raised.
• Records requested.
• Commitments made.
• Deadlines.
• Responsible officer.
• Follow-up status.
• Next meeting date.
• Public meetings should focus on ledgers: complaints, projects, budgets, maintenance, public spaces, and service performance.

Contractor Performance Record

Local contractors should have performance histories. A contractor who repeatedly delivers poor work should not keep receiving public money without scrutiny.

• The contractor record should include:
• Contractor name.
• Projects awarded.
• Project values.
• Completion status.
• Delays.
• Variation orders.
• Quality complaints.
• Inspection results.
• Payment status.
• Worker wage complaints.
• Blacklisting or warning status.
• Repeat poor performance.
• This record protects citizens and honest contractors. It reduces the ability of connected firms to survive poor delivery.

Ward Scorecard

• A ward scorecard should summarize performance in a simple public format.
• The scorecard may include:
• Complaints received.
• Complaints resolved within time.
• Projects completed.
• Projects delayed.
• Waste collection reliability.
• Drain cleaning completed.
• Streetlights functional.
• Road repairs completed.
• Park maintenance status.
• Public space encroachments recorded.
• Budget spent.
• Budget unspent.
• Citizen meeting held.
• Service failures pending.
• The scorecard should not become propaganda. It should report both progress and failure.

Citizen Evidence Guide

• Citizens should be trained to collect evidence responsibly.
• Useful evidence includes:
• Photographs with date and location.
• Short videos where safe and lawful.
• Complaint numbers.
• Copies of written complaints.
• Project board photographs.
• Before-and-after photos of local work.
• Witness statements.
• Maps or location pins.
• Public notices.
• Budget or project documents.
• Dates of visits or calls.

Citizens should avoid false claims, personal harassment, exposure of vulnerable people, or dangerous confrontation. Evidence should be used to create accountability, not mob pressure.

Youth Ward Audit Program

• Youth teams can help maintain ward ledgers if trained properly. A youth ward audit program should be structured.
• Youth teams can document:
• Project boards.
• Streetlight failures.
• Drain blockages.
• Waste collection routes.
• Park conditions.
• Public facility sites.
• Complaint response times.
• School and clinic visible conditions.
• Public toilet condition.
• Footpath obstruction.
• Road damage.

The program must include safety rules, privacy standards, verification discipline, and supervision. Young people should not be sent into confrontation with local power without protection.

Model Ward Complaint Form

A translated version of any form or letter is a draft for your understanding. Submit in the office’s official language, and have the final text checked by someone you trust.

Complaint number: [Insert]
Date: [Insert]
Ward: [Insert]
Location: [Insert]
Complaint category: [Insert]
Description: [Insert]
Photograph attached: [Yes or no]
Responsible department: [Insert]
Expected response date: [Insert]
Status: [Pending, in progress, resolved, referred, delayed]
Reason for delay: [Insert]
Escalation route: [Insert]
Completion evidence: [Insert]

Model Local Project Entry

Project name: [Insert]
Ward: [Insert]
Location: [Insert]
Purpose: [Insert]
Budget: [Insert]
Contractor: [Insert]
Scope: [Insert]
Start date: [Insert]
Completion date: [Insert]
Project board displayed: [Yes or no]
Supervising officer: [Insert designation]
Inspection date: [Insert]
Payment status: [Insert]
Citizen complaints: [Insert]
Current status: [Planned, ongoing, completed, delayed, abandoned]

Model Public Space Entry

Public space: [Insert name]
Ward: [Insert]
Location: [Insert]
Legal status: [Insert]
Size: [Insert]
Current use: [Insert]
Maintenance authority: [Insert]
Encroachment: [Yes or no]
Lighting: [Adequate, weak, absent]
Condition: [Good, fair, poor, unusable]
Complaints received: [Insert]
Last inspection: [Insert date]
Required action: [Insert]

Implementation Sequence

Start with one ward. Do not try to build a citywide ledger immediately if capacity is limited. Choose a ward where citizens, students, local officials, or civil society are willing to participate.

First, build the ward profile. Then add public projects. Then add complaint tracking. Then map public spaces. Then track maintenance schedules. Then publish a monthly ward scorecard. After the model works, expand to nearby wards.

The first ledger does not need to be perfect. It must be honest, usable, and updated.

Safeguards

• A ward ledger can be misused for political rivalry, selective targeting, extortion, or public shaming. Safeguards are necessary.
• The ledger should distinguish verified facts from complaints.
• Personal data should be protected.
• Vulnerable residents should not be exposed.
• Officials and contractors should have a chance to respond.
• Photographs should not invade private homes unnecessarily.
• Encroachment records should distinguish survival from organized privilege.
• Youth monitors should avoid unsafe confrontations.
• The purpose is public repair, not factional warfare.