Multi-Commissioner Series 1 — Article 2 of 4

VCSE Commissioning Analytics Series — Article 16 of 18 | Multi-Commissioner Series 1 — Article 2 of 4

The Canonical Data Model: One Collection Process That Serves All Commissioners | Multi-Commissioner Series 1 — Article 2 of 4

VCSE multiple commissioner reporting frameworks data management is the structured approach to collecting service delivery data once, at the point of activity, in a way that can generate every commissioner-specific report required — NHS ICB, local authority, combined authority, and central government — without additional data collection, manual transformation, or inconsistency between outputs.

The solution to multi-commissioner reporting complexity is not collecting more data. It is collecting the right data once, structured correctly from the point of referral, and applying different transformation rules to produce each commissioner report from a single consistent source. This approach — building a canonical data model at the collection layer — is the architectural principle that makes multi-commissioner reporting manageable rather than overwhelming.

A canonical data model for VCSE multi-commissioner reporting captures, at minimum, the following fields for every service user from the point of referral: unique service user identifier; referral date, source, and pathway; demographic data — age, sex, ethnicity using ONS 18+1 categories, postcode, disability status, primary language; primary need or support reason using a category structure that maps to both ASCOF and combined authority outcome definitions; service type and intervention model; episode start and end dates with all intermediate contact dates; validated outcome measure scores at baseline, mid-point, and closure; closure reason and onward referral destination; employment and housing status at referral and at closure where relevant to the service model; and social value output flags — volunteering generated, skills activities completed, community connections made.

This single dataset contains everything needed to produce an NHS ICB outcomes report, a local authority CLD-compatible return, and a combined authority social value KPI submission — because it was designed from the outset to serve all three, rather than designed for one and retrofitted for the others.

How to Map Each Commissioner Framework to the Canonical Dataset

Once the canonical dataset is established, the task is mapping each commissioner framework to the fields it requires and the transformation rules that produce its specific metrics.

For NHS ICB reporting under the Strategic Commissioning Framework, the mapping draws on validated outcome measure scores for PROM completion rates and mean change scores; demographic fields for equity analysis by ethnicity and deprivation; episode dates for waiting time calculations; contact dates for productivity metrics; and cost data from the finance system for value for money evidence. The ICB report is produced by applying these field selections and calculations to the canonical dataset for the reporting period.

For local authority adult social care reporting under ASCOF and the Care Act, the mapping draws on the same referral, demographic, and episode fields — but applies the ASCOF metric definitions and CLD schema rather than ICB metric definitions. The primary support reason field must use a category structure that maps to both the ICB service classification and the CLD primary support reason list — which requires careful design at the canonical model stage to avoid having to maintain two separate categorisation systems.

For combined authority social value reporting, the mapping draws on employment and housing status fields, social value output flags, demographic data for diversity evidence, and — where social value monetisation is required — applies the combined authority unit cost database to the output counts to produce financial value figures. This transformation layer is the most complex to build but the most valuable once operational, because it eliminates the manual calculation of social value financial figures that most VCSEs currently perform separately for each contract.

Managing the Reporting Calendar Across Multiple Commissioners

Different commissioners have different reporting cycles. An NHS ICB may require monthly activity returns and quarterly outcome reports. A local authority may require quarterly returns aligned to the financial year. A combined authority may require quarterly social value KPI submissions with an annual impact report. A VCSE holding three contracts may face significant reporting activity in ten of twelve months of the year.

The only sustainable approach is a single automated reporting system that can generate any commissioner report on demand from the live canonical dataset — rather than a separate manual production cycle for each report. This means that when the NHS ICB quarterly deadline falls in the same week as the local authority quarterly return and the combined authority monthly social value update, the contract manager opens the Power BI dashboard, selects the commissioner and period, and generates each formatted report in minutes rather than days.

Quematics builds this reporting calendar functionality into every multi-commissioner analytics system — a report generation layer that knows each commissioner format, each reporting period definition, and each submission requirement, and produces correctly formatted outputs automatically from the shared canonical data model.

Frequently Asked Questions

How should VCSEs structure data collection to serve multiple commissioners?

VCSEs should build a single canonical data model capturing all fields required by any commissioner from the point of referral, then apply commissioner-specific transformation rules to produce each reporting output. This eliminates inconsistency and reduces total data collection burden compared to maintaining separate processes for each commissioner.

What is a canonical data model for VCSE multi-commissioner reporting?

A canonical data model is a single agreed data structure that captures all information needed to produce any commissioner report from one consistent dataset — demographics, referral data, service activity, outcome measures, and social value outputs. Each report is generated by applying transformation rules to the canonical dataset rather than collecting data separately for each report.

Which data fields must a VCSE collect to serve NHS ICB, local authority and combined authority reporting simultaneously?

The minimum shared fields are: unique service user identifier, referral date and source, demographics including ONS ethnicity categories and postcode, primary support reason, service type, episode dates, validated outcome measure scores, closure reason, and employment or housing status. Additional fields include DRD dates for BCF reporting and social value output counts for combined authority contracts.

How do you prevent data inconsistency across multiple commissioner reports?

The only reliable way is ensuring all commissioner reports draw from the same underlying dataset with the same date boundaries, inclusion rules, and calculation logic. A Power BI data model with a single canonical dataset and commissioner-specific report views achieves this automatically.

What is the reporting calendar challenge for VCSEs with multiple commissioners?

Different commissioners have different reporting cycles — NHS ICBs monthly or quarterly, local authorities quarterly or annual, combined authorities quarterly. A VCSE holding three contracts may face reporting deadlines in nine of twelve months. A single automated reporting system generating any report on demand is the only sustainable solution at scale.

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