Case study · Community services · data
Women's Community Shelters
Taking a shelter network’s reporting from about two weeks of exports and spreadsheets to a 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
Women's Community Shelters records its client work in CIMS. Turning that into management, funder and board reports meant exporting, checking and reshaping the data by hand each reporting cycle, about two weeks of staff time.
Before: each reporting cycle, by hand
Exports and refuge spreadsheets reshaped into reports by hand.
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
We built a repeatable path from CIMS to a checked set of reporting data, keeping the original files, and reports shaped around the network's own questions. That makes it easier to trace a figure back to its source and definition. The demo below shows the idea on invented data.
Refuge report (demo report on invented data)
Bed nights by month
Where this figure comes from
158 women and children accommodated
- Client system export, original file kept
- Each woman or child counts once per quarter, even if they stay in more than one refuge.
- Matches the source total
- Refreshed automatically on 1 October 2026
158 women and children accommodated
What changed
The reporting cycle that used to take about two weeks of staff time now runs on its own.
This sits alongside CIMS; it doesn’t replace it.
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.