From Ledger to Headline: Making Council Performance Dashboards Readable in 2026

Local authority performance reporting is rarely short of data. A typical 2026 council dashboard might carry eighty indicators across waste, housing, adult social care, council tax collection and capital delivery. The difficulty is not supply. It is arrangement. When every measure receives equal visual weight, the reader is left to do the editorial work — and most readers, whether residents, scrutiny members or finance officers, will not.

The dashboard nobody reads

A representative 2026 performance pack might show council tax collection at 96.8 per cent by 31 October, a £4.2m overspend forecast in children’s services, 1,240 missed waste collections per 100,000 households, 84 per cent of housing repairs completed within 20 working days, and 112 adult social care reviews awaiting allocation. Each figure matters. Presented as twenty identical tiles, however, none of them leads. The reader sees noise before narrative.

The problem is partly institutional. Performance reports are assembled for committees, finance teams, service managers and residents at once. Each audience asks a different question, so the dashboard tries to answer all of them on one screen. The result is a filing cabinet with a colour palette. Good information design does not remove complexity; it sequences it.

At WHP Information Graphics, the working principle is simple: making complex information clear, one chart at a time. For council performance data, that means deciding what the page is for before deciding what it contains.

Fix one: lead with a single accountable metric

Every view should have one primary measure tied to a corporate priority, a statutory duty or a clear public promise. The measure should carry an owner, a target and a threshold. A finance view might lead with the forecast revenue overspend; a housing view might lead with the percentage of urgent repairs completed on time; a collection view might lead with the in-year council tax collection rate.

The headline is not the only number on the page. It is the number that tells the reader why the page exists. Put it in plain language, show the direction of travel and state the accountable officer or service area. A dashboard without a named owner is a noticeboard, not an accountability tool.

Fix two: layer the evidence instead of burying it

Progressive disclosure is the antidote to the eighty-tile dashboard. The first layer should answer the five-second question: is performance on track, ahead or behind? The second layer should answer the five-minute question: by how much, since when and against what benchmark? The third layer should provide the five-hour audit trail: definitions, source systems, extraction dates and downloadable tables.

This is not a plea for concealment. It is a plea for order. A summary line, a small multiple and a short annotation will often do more than a dense heat map. Where a table is necessary, sort it by exception rather than alphabetically. Where a chart is necessary, label the axis directly and remove the legend if it can be avoided.

Fix three: design for the phone before the committee room

Many residents will meet a council dashboard on a mobile phone, often while standing on a bus or waiting in a queue. Committee members may meet it in a printed pack. These are different reading conditions, and the mobile layout should not be an afterthought.

Start with a 360-pixel-wide screen. Stack the headline, the trend sentence and the chart vertically. Collapse secondary detail into expandable sections. Replace wide tables with ranked lists or small multiples. Test the colour contrast and tap targets, and ensure the page still makes sense when images fail to load. A dashboard that only works on a desktop monitor in a meeting room is a document, not a public service.

Fix four: annotate in plain English

Technical labels are where many council dashboards lose their readers. A measure called ‘percentage of Section 47 enquiries completed within timescale’ may be precise, but it is not self-explanatory. Add a short definition in plain English, a note on why the measure matters and a sentence explaining any unusual movement.

Annotations should also carry uncertainty. If a figure is provisional, say so. If a change is within normal monthly variation, say that too. Avoid implying precision that the data does not support. And never rely on colour alone to signal performance: use words, icons and position as well as red, amber and green.

Fix five: publish a rhythm and a change log

Real-time data is not always better data. Council performance measures are often monthly or quarterly, and a dashboard should reflect that cadence honestly. Show the date of the latest data, the date of the next update and the source system. Keep a short change log when definitions, targets or collection methods alter.

A visible update rhythm reduces anxiety and builds trust. It also protects the dashboard from the temptation to refresh a number simply because the technology allows it. Stability is a design feature: readers should be able to tell whether a change is a change in performance or a change in method.

What good looks like

A strong 2026 council performance view might open with one sentence: ‘Council tax collection was 96.8 per cent by 31 October 2026, 0.4 percentage points below target and broadly in line with the previous year.’ Beneath it, a simple line chart shows the in-year trajectory against target. A short annotation explains the main driver. A link opens the detailed table, the definition and the responsible service.

That is not a simplification of the evidence. It is an ordering of the evidence. The dashboard nobody reads usually fails not because the data is poor, but because the design asks the reader to work too hard to find the point. The fix is editorial discipline: one accountable metric, layered evidence, mobile-first layout, plain-English annotation and an honest update rhythm.