Local Government KPI Dashboard Example

City Government Performance Dashboard

It's March, the freeze-thaw cycle has done its work, and the 311 queue is mostly potholes. At the same council meeting, a homebuilder stands up to ask why a deck permit takes a month. Both complaints are about time, and both land on the city manager, who has to answer for two departments that keep their numbers in completely different systems.

This is ordinary work for a lot of governments. The 2022 Census of Governments counted 3,031 county governments and 35,705 municipal and township governments, as the Federal Reserve Bank of St. Louis summarized it in 2024.

The streets are the hard part. The ASCE 2025 Infrastructure Report Card gave US roads a D+ and found 39% of major roads in poor or mediocre condition. Trust is holding up better than the pavement: Gallup's September 2025 Governance poll found 65% of Americans have a great deal or fair amount of trust in their local government to handle local problems. That goodwill gets spent one slow repair at a time.

The city in this example is made up: about 95,000 residents, a council-manager government, and a fiscal year that runs July to June. The figures are modeled; none come from a real city. Where a KPI has a standard definition in ICMA's Open Access Benchmarking key indicators, the board uses it. One target is tied to a published national median. The rest are starting points to replace with your own history.

What is a Local Government KPI Dashboard?

Overview

A local government KPI dashboard puts the services residents can see, from potholes to permits to library doors, next to what they cost and what residents think of them, so a council can tell a slow department from an overloaded one.

Most of the work starts as a request. 311 requests per 1,000 residents shows how much is coming in, and 311 median resolution time shows how long residents wait for an answer that actually closes the ticket.

Then the two departments that take most of those requests. In Public Works, pothole repair time tracks the street crews and park maintenance work orders completed tracks the parks crews, who often share trucks and people with them. In Development Services, residential permit turnaround tracks the plan reviewers, and code enforcement days to voluntary compliance tracks the inspectors chasing overgrown lots, junk vehicles and unpermitted sheds.

Library visits per 1,000 residents is the steadiest number on the board.

Three numbers sit over the top. Public Works overtime as a share of hours shows when crews are being stretched to hold a service time. General fund budget utilization shows what that stretch cost. Resident satisfaction with city services is the slow verdict on all of it.

Who benefits from this dashboard?

1. City Manager: One screen that shows whether a slipping service time is a performance problem or a capacity problem, before it reaches the council agenda.
2. Public Works Director: Pothole repair time, park work orders and overtime together make the case for crews at budget time, with numbers instead of anecdotes.
3. Development Services Director: Permit turnaround and code compliance times are what builders and neighborhood associations complain about. Watching them weekly gets ahead of the public comment period.
4. Finance Director: Budget utilization by month catches an overtime-driven overrun in the fall, while there's still time for a mid-year amendment instead of a year-end surprise.
5. Council members: When a resident asks why their street is still waiting, they can see the queue, the crews and the trend, not just a promise to look into it.

Count potholes, not reports. Once residents can drop a pin from a phone, one bad pothole on a busy road can arrive as 20 separate 311 tickets. Merge duplicates by location before you calculate repair time, and time each pothole from its first report. Otherwise repair time looks better than it is (20 tickets closed at once) and request volume looks worse.

Dashboard Example Overview

The example city has about 95,000 residents and a general fund of $119.5 million in fiscal 2026. Public Works, roughly 220 staff, covers streets and parks. Development Services handles building permits and code enforcement. The city reports ten KPIs to the council monthly:

• 311 Median Resolution Time: Median calendar days from a 311 request being logged to its closure as resolved, all request types. The median, so a few months-old drainage cases don't distort it.
• 311 Requests per 1,000 Residents: Requests logged in the month divided by population, times 1,000. The one demand number on the board, with no target, because more reporting isn't bad news on its own.
• Pothole Repair Time: Average calendar days from the first report of a pothole to the repair, with duplicate reports merged. Lower is better.
• Park Maintenance Work Orders Completed: Scheduled park work orders (mowing, trash, playground checks, irrigation repairs) completed in the month, divided by those scheduled.
• Residential Permit Turnaround: Average calendar days from application to issuance for residential building permits, the way ICMA defines it. Calendar days, not business days, because that's how the homeowner counts.
• Code Enforcement Days to Voluntary Compliance: Average calendar days from first inspection to the owner fixing the violation, for cases that reached voluntary compliance in the month. Another ICMA indicator. Cases that end in a citation or a city abatement are tracked separately.
• Library Visits per 1,000 Residents: In-person visits counted at the door, divided by population, times 1,000. The IMLS Public Libraries Survey put the median at 2.8 visits per person in fiscal 2023, about 233 a month per 1,000 residents.
• Resident Satisfaction with City Services: Share of monthly pulse survey respondents, about 400 a month, rating the quality of all city services excellent or good. It's the same question ICMA benchmarks, asked monthly instead of once a year.
• Public Works Overtime % of Hours: Overtime hours divided by all Public Works hours paid. It rises before service times do when crews are covering more than they're staffed for.
• General Fund Budget Utilization: Fiscal year-to-date spending divided by year-to-date budget. 100% means on plan. Running above it in the first half of the year is a warning, not a rounding error.

In October 2024 the two departments are in very different shape. Pothole repair time is 3.4 days and park work orders are 92.3% complete, so Public Works is on top of its fall workload. Development Services isn't. Residential permits take 29.8 days from application to issuance, and code cases take 44.3 days to reach voluntary compliance.

By spring 2025 both are under pressure. Freeze-thaw season pushes pothole repair time to 5.8 days in February, and building season pushes permit turnaround to 34.6 days in March. The council asks both directors to come back with a fix.

Both launch in April 2025. Development Services moves to online applications with electronic plan review, so building, fire and zoning review the same set of plans at the same time instead of passing paper down a hall. It also opens an express lane for simple residential permits like fences, water heaters and re-roofs, and gives inspectors tablets to issue compliance letters from the curb. Public Works launches a 311 app where residents can photograph a pothole and drop a pin.

Development Services gets what it wanted. Permit turnaround falls to 21.0 days in June 2025, 14.9 in September and 12.6 by September 2026. Days to voluntary compliance drop from 42.0 in April 2025 to 31.6 in September 2026.

Public Works gets more requests. 311 requests per 1,000 residents go from 34.4 in March 2025 to 47.7 in July, and the crews are the same size. Pothole repair time should fall in summer. Instead it's 5.3 days in July 2025, against 3.4 the October before. Park maintenance work orders completed drop to 78.1% in August as parks staff are lent to patching crews, and Public Works overtime rises from 6.1% of hours in October 2024 to 11.6%.

Winter 2026 makes it plain. In February, requests reach 48.8 per 1,000, pothole repair time hits 8.4 days and overtime is 14.6% of hours. 311 median resolution time, which stayed between 5.0 and 5.6 days from January to October 2025, reaches 6.9 days, because the faster permit and code requests are swamped by slower street requests. Resident satisfaction falls to 61.6%, its lowest in two years. Far more residents drive on city streets than ever pull a permit, so the department that improved couldn't carry the score.

The board explains the difference on its own. Development Services changed how the work gets done. Public Works changed how the work arrives. By February 2026, requests are up about half on October 2024, overtime has more than doubled and parks completion is down 12 points. That's a capacity problem, not a crew that stopped trying.

It shows up in the budget, too. General fund utilization runs above plan from August 2025 and reaches 102.4% from March to May 2026, mostly Public Works overtime and extra asphalt. The city closes fiscal 2026 at 102.3%, about $2.7 million over a $119.5 million budget.

Development Services doesn't get a clean sweep either. Spring building season pushes permit turnaround back up to 16.3 days in April 2026, over its target of 14, because the express lane only covers simple jobs and additions still queue for full review. Days to voluntary compliance never reach the 30-day target. The last few days are the property owners who ignore the first letter, and tablets don't change that.

The fiscal 2027 budget funds a second pothole crew from August 2026. By September, pothole repair time is 4.4 days, overtime is 8.6% and park work orders are back to 86.0%. That's two months of data, and the street side still hasn't caught up with where it started: pothole repair time is a full day slower than in October 2024, and satisfaction, at 67.5%, is still just short of the 68.0% it started at. Library visits barely moved through any of it, at 2.72 and 2.73 per resident a year, slightly under the IMLS median.

List of Local Government KPIs

Library visits is the only KPI here with a published national median behind its target. Permit turnaround, code compliance days and resident satisfaction follow ICMA definitions, but ICMA doesn't publish a single national target for them, so they're marked as starting points with the rest.

Why Local Government Dashboards Matter

City departments are usually judged one at a time, at the council meeting where their item comes up. That's how a city ends up praising permitting and scolding Public Works in the same month, without noticing that one got a process fix and the other got a new front door with no extra crew behind it.

These ten numbers pull against each other in ways that only show on one screen. Making 311 easier to use raises request volume, which lengthens repair times even when crews work harder. Holding pothole repair time by lending parks staff lowers park work order completion. Holding both with overtime pushes general fund utilization over plan. Each of those trades can be the right call, but the council should see the cost when it's made, not in the year-end audit.

Satisfaction is the last to move and the hardest to win back. It follows the service most residents use, which for most cities is the street outside the house, not the permit counter. A board that shows demand, crew strain and cost beside the service times lets a manager explain a bad month with evidence, and bring a staffing request to budget season with a year of numbers behind it.

For agency-level measures like cost per service and capital project delivery, see the public sector dashboard example. If your city runs its own trash and recycling service, the waste center example covers that side of Public Works.