How a State Court Put Its Service Data in Front of the Public

A state-level judicial institution serving thousands of residents wanted two things that pulled in the same direction: openness with the public about how its services were being used, and better internal decisions about where to put its staff. Neither was possible while the data sat in spreadsheets across teams and formats. OnPoint Insights standardised that data into SharePoint and built three Power BI dashboards on top of it, one of them public.

Court data made public

Programme usage, demographics, languages and help centre activity are published in a dashboard citizens can open themselves, instead of being available only on request.

3 dashboards, 2 audiences

One public-facing view and two internal court management views, all built on the same standardised data.

Spreadsheets to automated refresh

Excel files cleaned, standardised and moved into SharePoint, with Power BI refreshing from them automatically instead of someone rebuilding a workbook.

The problem

Transparency is a data problem before it is a policy one

A court can commit to being open and still have nothing it can publish. Service data kept in spreadsheets, in different formats, maintained by different teams, cannot be put in front of citizens, because nobody can stand behind the numbers in it.

Our client had both halves of that problem. Residents could not see what court programmes were actually doing, and internally nobody could analyse visitor demographics, case types or how well the phone and chat services were coping.

What was getting in the way

  • Limited public access to service usage data reduced transparency and made it harder for citizens to understand court programme activity.
  • Internal teams had no efficient way to analyse visitor demographics, case types and resource allocation patterns.
  • There was little visibility into call, chat and other communication channel performance, so user engagement and service quality were hard to evaluate.
  • Data sat across multiple spreadsheets and formats, which slowed reporting and made consistent analysis difficult.

Our approach

Standardise the data, then publish it

What we found

The public dashboard and the internal ones needed the same thing first: one set of numbers that could be trusted and refreshed without anyone rebuilding a spreadsheet. Standardising the Excel data and moving it into SharePoint came before a single visual was designed.

What we did

A public dashboard, four pages. Programme usage, demographics, languages, interviews and help centre activity, published for citizens to browse rather than request.

A dashboard for staffing decisions. County-level visitor trends, case types and demographics, so staff and resources are planned against where demand actually is.

A dashboard for service channels. Call and chat volumes, wait times and channel usage, so the court can see where people are struggling to get through to someone.

One source behind all three. Excel data cleaned and standardised, stored in SharePoint and connected to Power BI for automated refresh, so the public and internal views cannot drift apart.

The choice we made

We published the public dashboard from the same standardised data as the internal ones, rather than preparing a separate extract for public consumption. It means the figures citizens see are the figures the court manages with, and it removes the quiet risk in any transparency project: two versions of the same number, one of them wrong, both of them public.

BUILT ON
  • Power BI Power BI
  • SharePoint SharePoint
  • Excel Excel

The results

What changed for the court and for the public

The court can now show its work, and decide with the same numbers it shows.

Citizens can check for themselves

Court programme data is openly accessible rather than held internally, which the client links to stronger public trust and awareness of what the services actually offer.

Staffing follows demand

Management allocates staff and resources against visitor trends and demand patterns by county, instead of against last year’s assumptions.

Shorter waits on the channels people use

Visibility into call and chat performance improved wait times and communication efficiency, which is what the public experiences of a court service before anything else.

Let's Connect

Facing a similar challenge?

Talk to our data and AI team about where you are today and what good looks like. 30 minutes, no obligation.

Book a consultation
Professional customer service agent on a support call
More Case Studies
Next Case Study
Contact Us

Collaborate with us

We're here to answer your questions and help you find the right solution.

Client-oriented
Results-driven
Problem-solving
Transparent

"*" indicates required fields

This field is for validation purposes and should be left unchanged.