Skip to content

Case study · Community services · data

Women's Community Shelters

Taking the repeated CIMS export and reporting work out of a shelter network’s reporting cycle.

What we did
Reporting automation + Power BI
Year
2026
Type
Community services · data

The reporting problem

Women's Community Shelters uses CIMS for client and service work. To make that data useful for management, funder and board reporting, staff had to get it out, check it and turn it into a consistent set of measures.

The reporting task was not just a dashboard design problem. Source extracts, joins and calculation definitions had to be made dependable first.

What we built

We implemented a controlled CIMS extraction path that keeps the original source files, validates the data and publishes a curated reporting release into the client's SharePoint environment. Power BI then refreshes from that governed release.

The views are specific to the organisation and its reporting questions, rather than a generic sector dashboard. The process makes it easier to trace a reported figure back to its source and definition.

01CIMS extractionRepeatable source capture with retained originals
02ValidationChecks before a reporting release is promoted
03SharePointPublication into the client’s Microsoft environment
04Power BIOrganisation-specific management and reporting views

What changed

The extraction and reporting flow now runs without routine staff action. The work also exposed calculation and data-join issues, so we could correct those definitions or surface them for review before they were relied on in reporting.

This case study describes the implemented reporting path. It does not imply that CIMS was replaced or that every corrected figure has been formally accepted by the board.

Evidence note: The implementation is documented in project artefacts. The change in routine staff work is based on my observation of the delivered process; no time saving has been independently audited.