GovTech

Public dashboards & transparency

Publish the numbers before someone requests them — performance data presented with enough context to inform rather than inflame.

What is a public transparency dashboard?

A public transparency dashboard publishes a public body's operational data — complaint volumes and resolution times, project progress, expenditure, service performance — in a form citizens and journalists can read directly, rather than only through information requests.

Publishing changes the internal conversation

The strongest argument for transparency dashboards is not external. It is that publishing a number weekly changes how the organisation treats it. Resolution times that were reviewed quarterly get attention when they are visible, and the improvement usually starts before any citizen looks.

The risk is real too, and worth naming: published data will be used critically, sometimes without context. That is a reason to present figures carefully — with denominators, trends and explanation — not a reason to withhold them. Data obtained by RTI and published by someone else carries no context at all.

Process

How we deliver it

1Choose the measuresWhat genuinely reflectsperformance, agreedinternally first.2Establish definitionsOne documented meaning permeasure, publishedalongside.3Automate the feedDirect from operationalsystems, no manualcompilation.4Present with contextDenominators, trends andplain-language explanation.5Publish open dataDownloadable datasetsalongside the visualdashboard.
Process flow for Public dashboards & transparency
  1. 01

    Choose the measures

    What genuinely reflects performance, agreed internally first.

  2. 02

    Establish definitions

    One documented meaning per measure, published alongside.

  3. 03

    Automate the feed

    Direct from operational systems, no manual compilation.

  4. 04

    Present with context

    Denominators, trends and plain-language explanation.

  5. 05

    Publish open data

    Downloadable datasets alongside the visual dashboard.

Deliverables

What you receive

  • Public dashboard with automated data refresh
  • Documented metric definitions published alongside figures
  • Downloadable open datasets in machine-readable formats
  • Internal management view with greater detail
  • Accessibility conformance to GIGW 3.0 and WCAG 2.1 AA

Engagement shape

Twelve to twenty-four weeks, dependent on how ready the source systems are to supply data automatically.

Tooling

What we typically build with

  • React
  • PostgreSQL
  • Metabase and Grafana
  • Open data formats
  • GIS visualisation
  • WCAG 2.1 AA

Stack decisions follow the problem. This is where we usually start, not a fixed menu.

Frequently asked

Questions we get about this

What if the numbers look bad initially?

They often do, and publishing a poor baseline with a stated improvement plan is more credible than delaying until the figures flatter. Administrations that wait for good numbers before publishing usually never publish.

Should raw data be downloadable?

Yes, in machine-readable formats. Researchers and journalists will analyse it either way; providing it directly means they work from your complete dataset rather than a partial extract obtained elsewhere.

Talk it through before you commit

A discovery call is a working session on your constraint, not a sales pitch.

Quick inquiry

Tell us what you're trying to build

A short note is enough. You'll hear back from the team, not a bot — usually within one working day.

Captcha challenge