Multi-Commissioner Series 1 — Article 3 of 4

VCSE Commissioning Analytics Series — Article 17 of 18 | Multi-Commissioner Series 1 — Article 3 of 4

How a Single Power BI Infrastructure Serves Multiple Commissioners Simultaneously | Multi-Commissioner Series 1 — Article 3 of 4

VCSE Power BI multi-commissioner reporting dashboard infrastructure is the technical architecture that enables a single Power BI data model to produce NHS ICB outcomes reports, local authority CLD-compatible returns, combined authority social value KPI submissions, and Procurement Act performance reports simultaneously — each formatted correctly for its commissioner, each drawing from the same consistent underlying data, and each refreshing automatically from the VCSE existing case management systems.

This is the practical realisation of the canonical data model discussed in the previous article in this series. The canonical dataset is the foundation. Power BI is the analytical and reporting layer built on top of it. And the result is a single reporting environment that eliminates the multi-commissioner data complexity that consumes significant administrative resource in VCSEs currently managing commissioner reporting manually.

The architecture works because Power BI separates data storage from data presentation. The data model holds one version of the truth — the canonical dataset with all service user records, outcome scores, contact dates, and social value outputs. Report pages apply commissioner-specific views to that data, calculating each commissioner’s metrics using their specific definitions, presenting them in their required format, and generating outputs ready for submission without any manual intervention between the data and the report.

The Power BI Data Model Structure for Multi-Commissioner Reporting

A Quematics-built multi-commissioner Power BI data model for a VCSE has five layers. The source connection layer links Power BI to every operational data source — case management system, HR system, finance system, and any commissioner-supplied data. Connections are scheduled to refresh automatically, typically daily, so the data model always reflects current operational data without manual extraction.

The canonical data layer standardises and validates all source data against the agreed canonical schema — applying data quality rules, resolving inconsistencies between source systems, deduplicating service users who appear across multiple contracts, and flagging any data quality issues for operational team attention. This layer is where the single source of truth is created and maintained.

The metric calculation layer contains all commissioner-specific DAX measures — the calculation logic that transforms canonical data into NHS ICB metrics, ASCOF metrics, combined authority social value outputs, and Procurement Act KPI figures. Each metric is calculated once, consistently, from the canonical data, and is available to any report page that needs it.

The report layer contains separate pages for each commissioner — an NHS ICB outcomes report page, a local authority CLD report page, a combined authority social value page, and an internal management overview page. Each page is formatted to the commissioner requirement and can be exported as a PDF or Excel file for submission with one click.

The alert and monitoring layer tracks performance against every contract target across all commissioners and generates automated notifications when any metric approaches a threshold that requires management attention — whether a social value KPI running below trajectory, an outcome completion rate falling below the contract minimum, or a data quality completeness rate dropping below the acceptable threshold.

Handling Service User Overlap Across Commissioner-Funded Services

One of the most technically complex aspects of multi-commissioner Power BI reporting for VCSEs is handling service users who receive services funded by more than one commissioner. A person who accesses an NHS ICB-funded mental health community service and a local authority-funded carers support service from the same VCSE organisation is one individual in reality — but they appear in two contract datasets, and their activity needs to be attributed correctly to each contract without double-counting at the organisational level.

The Quematics canonical data model handles this through a unique service user identifier that is consistent across all contract datasets within the organisation. When a service user appears in multiple datasets, the model identifies them as the same individual, attributes their activity correctly to each contract according to the service type recorded, and presents them as one person in any cross-contract summary view — while correctly counting them in each individual commissioner report for the contract they were served under.

This deduplication logic is essential for organisational integrity reporting and for any cross-commissioner overview that a VCSE board or senior leadership team needs to understand total reach and total impact across all commissioned activity.

Frequently Asked Questions

Can a single Power BI dashboard serve multiple commissioners for a VCSE?

Yes. A well-architected Power BI data model with a single canonical dataset and commissioner-specific report pages can produce NHS ICB outcomes reports, local authority CLD-compatible returns, combined authority social value KPI submissions, and Procurement Act performance reports simultaneously — each formatted correctly and drawing from the same consistent underlying data.

How does Power BI handle different metric definitions for different commissioners?

Power BI applies commissioner-specific transformation logic within the data model — different DAX measures calculate NHS ICB metrics, ASCOF metrics, and combined authority social value metrics from the same underlying dataset using their respective definitions. Each commissioner report page applies the relevant measures without affecting the others.

What does a VCSE multi-commissioner Power BI dashboard look like in practice?

It typically has a home page showing a cross-commissioner summary with a commissioner-by-commissioner status panel. Behind each panel is a dedicated report section with the specific metrics, visualisations, and formatted outputs required for that commissioner’s reporting framework.

How does the Power BI data model stay consistent when data is entered in multiple source systems?

The data model applies data quality rules and deduplication logic at the ingestion layer. A service user appearing in both an NHS ICB-contracted service and a local authority-contracted service is identified as the same individual through a unique identifier, preventing double-counting while correctly attributing activity to each contract.

How long does it take to build a multi-commissioner Power BI system for a VCSE?

Quematics typically delivers a foundational multi-commissioner system within eight to ten weeks — including data audit, canonical data model design, pipeline build, commissioner-specific report development, and user acceptance testing.

To discuss how Quematics can build a multi-commissioner Power BI system as part of our VCSE commissioning analytics service for your VCSE, visit our Power BI consultancy page or our data analytics for charities page, or contact us for a free 30-minute data review.