Reporting and governance
What good commissioner reporting should include
Reporting is where a commissioned package either demonstrates its value or becomes invisible. This sets out the four layers of reporting worth specifying, what each should contain, and how to ask for it at commissioning stage rather than chasing it later.
In short
- Specify reporting before mobilisation. Retrofitting it is much harder.
- There are four distinct layers: daily records, incident reports, progress reports and review reports. They serve different purposes.
- More frequent is not automatically better — a weekly report nobody reads is worse than a fortnightly one that is used.
- Reports should separate observation from interpretation.
- If you cannot tell from the reporting whether the package is working, the reporting is wrong.
The four layers
| Layer | Purpose | Frequency | Audience |
|---|---|---|---|
| Daily / service records | Contemporaneous account of what was delivered | Every session | Provider; available to commissioner on request |
| Incident reports | Record and escalate specific events | As they occur | Commissioner, promptly |
| Progress reports | Whether the package is achieving its outcomes | Agreed — weekly, fortnightly or monthly | Commissioner, case-holding professionals |
| Review reports | Should the package continue, change or end | At agreed review points | Commissioner, panel or review meeting |
Most reporting disputes come from conflating these — expecting a monthly progress report to contain incident-level detail, or receiving daily logs when what was needed was an assessment of whether things are improving.
Daily and service records
The base layer. Written at the time or immediately after, by the practitioner who was there.
Should contain: date, times, who was present, what was planned, what actually happened, how the person responded, anything of concern, and anything requiring follow-up.
Should not contain: speculation presented as fact, diagnostic language practitioners are not qualified to use, or judgements about people who were not present.
Commissioners do not usually need daily records routinely, but should be able to request them and receive them promptly.
Incident reports
The layer most often specified poorly. Agree at commissioning stage:
- What counts as an incident for this package — thresholds differ by situation and should be explicit
- How quickly you are told, and by what route
- Who is contacted out of hours, and who deputises
- What triggers immediate escalation rather than a report
- The safeguarding route — how a concern reaches statutory processes
A useful incident report contains: what happened, factually and in sequence; what preceded it; what the practitioner did; the outcome; who was informed and when; and what has changed as a result.
What it should not do is minimise. A provider whose incident reports are consistently reassuring is either exceptionally lucky or not reporting properly.
Progress reports
The layer that answers the question you actually care about: is this working?
A progress report should be structured around the outcomes agreed at design stage, not around activity. "We delivered 42 hours" is an invoice, not a progress report.
A workable structure
- Outcomes and progress against each — with observable evidence
- What has changed since the last report, in either direction
- Delivery summary — hours delivered against commissioned, and any gaps with reasons
- Risk — current picture, and how it has changed
- Incidents — summary, cross-referring to reports already sent
- What is working, and what is not — the second matters more
- Recommendations — including reduction or ending where appropriate
Review reports
Produced at agreed review points to support a decision: continue as is, change the model, step down, or end.
Should address: whether the original outcomes remain the right ones; progress against them; whether the support model is still appropriate; how risk has changed; the young person's or family's view; and a clear recommendation with reasoning.
Should be usable by someone who has not read the previous reports — review reports are frequently read by panels and managers coming to the case fresh.
Specifying reporting at commissioning stage
Ten minutes at design stage prevents most reporting problems.
Agree before mobilisation
- Which of the four layers you require
- Frequency of progress reporting
- Format — document, structured template, or agreed headings
- Who receives each report
- Turnaround time for incident reports
- What counts as an incident for this package
- Out-of-hours contact and escalation route
- Safeguarding escalation route
- Whether reports may be shared with other agencies, panels or proceedings
- Review points and who attends
- Whether you want to see an example report structure first
Ask for a sample structure before mobilisation. A provider who cannot show you what their reporting looks like probably does not have a standard.
Warning signs in provider reporting
- Uniformly positive. Real support work has setbacks.
- Activity instead of outcomes. Hours delivered without reference to whether anything changed.
- Late or chased. If you are asking for reports, the arrangement is not working.
- Interpretation presented as observation. Particularly diagnostic or clinical language.
- Identical phrasing week to week. Suggests template completion rather than recording.
- Incidents surfacing late — appearing first in a monthly report rather than at the time.
- No recommendations. A provider with no view about what should happen next is not engaging with the case.
How Gwennol reports
Reporting format and frequency are agreed at design stage, before delivery begins, so you know what you will receive and when. Records are kept from the first session. Incidents are recorded, escalated and followed up, with referral into statutory safeguarding processes where thresholds are met. Reviews look at risk, progress, outcomes and whether the package should continue, step down or change.
Within the scope of the contract and our current regulatory position, reporting sits with us rather than being handed back to the commissioner — see commissioned support vs agency staffing for why that distinction matters.
Questions we are asked
How often should we expect progress reports?
It depends on the situation. During instability, short frequent reporting is usually more useful than a long monthly document. For a settled longer-term package, monthly is often right. What matters is that it is agreed at design stage and that someone actually reads what arrives.
Can we see an example report before commissioning?
Yes, ask. We agree format and frequency at design stage and would rather show you a structure up front than discover after mobilisation that it is not what you needed.
Who owns the records?
Records of the support we deliver are created and held by us as part of running the package, and shared with the commissioner as agreed. Data protection responsibilities and retention should be covered in the contract — our current data-handling position is described in our privacy notice.
What if we disagree with something in a report?
Say so. Records should be factual, and factual errors should be corrected. Differences of professional interpretation are worth recording as differences rather than resolved by one party rewriting the other's account.
Do you report on outcomes or just activity?
Both, but they are separated. Delivery against commissioned hours is one section; progress against the outcomes agreed at design stage is another. Reporting that only shows activity does not tell you whether the package is working.