Case study · Community services · data
Lou's Place
Turning each reporting cycle’s exports and spreadsheets into one report that runs on its own.
- Service
- Reporting automation
- What we did
- Reporting automation
- Year
- 2026
- Type
- Community services · data
- Client
- Client website ↗
The reporting problem
Each reporting cycle, staff pulled exports from SRS and the feedback survey, matched them up in spreadsheets and rebuilt the reports by hand. That took about two weeks of staff time.
Before: each reporting cycle, by hand
Exports, survey results and spreadsheets copied into reports.
About two weeks of staff time
Checked and joined
Every source is pulled, checked and joined the same way.
Original files kept
Runs on its own
One set of reports, refreshed on schedule.
Runs on its own
What we built
Each source is now pulled, checked and joined the same way every time, with the original files kept. The reports are built around Lou's Place's own programmes and questions, which makes it easier to trace a figure back to where it came from. The demo below shows the idea on invented data.
Service report (demo report on invented data)
Visits by month
Where this figure comes from
303 women supported
- Client system export, original file kept
- Each woman counts once per quarter, however many times she visits or which programmes she uses.
- Matches the source total
- Refreshed automatically on 1 October 2026
303 women supported
What changed
The reporting cycle that used to take about two weeks of staff time now runs on its own.
This sits alongside SRS; it doesn’t replace the client system.
Want to see this on your own numbers? Grab 20 minutes
Evidence note: The two-week figure is the time the previous process took, as observed during the project. It hasn’t been independently audited.