Start with the question behind the report
In our work with a care provider, the team was already looking at agency spending. The difficulty was understanding the detail across the available information. Preparing the figures involved spreadsheets, formulas and manual checks, while temporary names made investigations difficult across the data.
We worked with the team to deliver dashboards that made staffing coverage easier to examine: how many hours were required, how many were filled by employed staff and how many were covered by agency workers. Where the underlying information was correct, agreed rates could also help them understand income alongside agency costs.
That was a more useful starting point than deciding which charts would look good. The report needed to help people investigate the work being covered and where staffing questions required attention.
Agree what the figures mean
Before a measure becomes a chart, someone needs to understand the records behind it. Which hours are being counted? How is agency work identified? Which period does the report cover? If rates change, which rate applies to a particular entry?
These are business questions as much as technical ones. The person building the dashboard can help uncover inconsistencies, but the organisation needs someone who can resolve uncertain definitions and confirm how the data should be interpreted.
When information is missing or unreliable, show the limitation. A clear gap is more useful than a precise-looking number that encourages the wrong conclusion.
Delivery and regular use are different outcomes
The dashboards were delivered, but the team did not use them regularly after handover. The business was going through continual change, and the delivered scope soon fell out of step with the next set of requirements.
That limits what we can claim about the result. We made the information easier to examine; we cannot attribute lasting savings or improved staffing decisions to dashboards that were not consistently used.
It also leaves a practical lesson. A reporting project should include a conversation about the routine around the report: who will look at it, what they will decide and how changes to the business will reach whoever maintains it. That conversation deserves attention before the charts are finished.
Give the first report a job it can keep doing
For a new reporting project, we would start with one decision, a named owner and an agreed review point. Use enough information to answer that question, then check whether the result helps the team act. More charts can follow when there is a clear reason for them.
Keep a route for correcting definitions and updating the scope as the business changes. A report that was accurate at delivery can become less useful if the way work is recorded changes and nobody owns the adjustment.
If your team spends time assembling figures but still struggles to use them, the first discussion need not be about a particular reporting tool. Tell us what you are trying to decide, what information you have and where the manual work happens. That is a useful basis for scoping the next step.