First week of the month, and the data return is due
Your physio business holds a contract to see NHS-funded musculoskeletal patients alongside your private work. Every month the commissioner wants a return: referrals received, referral sources, waiting times to first appointment, attendances, did-not-attends, discharges and sometimes outcome measures, broken down in their format.
Your operations lead exports appointment data from the clinic system, pulls referral dates from a spreadsheet the admin team keeps, looks up discharge dates in treatment notes, and pastes everything into the commissioner's template. It takes the best part of three days. The numbers never quite match last month's closing figures, and there is always a query afterwards.
Why the return is so manual
Clinic systems are built to run a clinic, not to produce contract reports. The data exists, but not always in the shape the commissioner wants. Referral received date, first contact date and first appointment date may be recorded in different places, or not recorded at all for some patients.
NHS and private patients share the same diaries and physios, so NHS activity has to be separated out reliably. If a patient is tagged inconsistently, they appear in one month's figures and not the next.
Definitions matter. What counts as a wait, when a discharge is recorded, whether a cancelled appointment is a DNA: each needs to be applied the same way every month, and in a manual process they drift depending on who builds the return.
What a manual return costs
| Issue | Consequence |
|---|---|
| Days of spreadsheet work | Senior time lost every month |
| Inconsistent definitions | Figures that change between months |
| Missing dates | Gaps the commissioner queries |
| NHS and private mixed | Activity over or under counted |
| No early warning | Waiting time problems spotted after month end |
Contract returns are also how the commissioner judges your service. Figures that are late, inconsistent or queried do not help when the contract comes up for renewal.
How we produce the return from your data
- We agree each figure's definition with you, matching the commissioner's guidance, and write it down in plain language.
- NHS patients are identified consistently, using a referral source or funding tag that reception set at referral, with a check that catches untagged records.
- Data is pulled from your clinic system through its API or scheduled exports into a small reporting database.
- Records missing a required date or status are listed for admin to complete before the return is produced.
- The return is generated in the commissioner's template, with a comparison against the previous month so unusual changes stand out.
- A weekly dashboard shows waits and referral volumes as they happen, so problems are visible before month end.
The operations lead reviews and submits every return. The system does the assembly and highlights anything that needs a human decision.
The first week of the month, afterwards
The return becomes a checking job rather than a building job. Definitions stay the same from month to month, so figures are consistent and queries fall away. Missing data is caught while it can still be fixed. The weekly dashboard means you see a lengthening wait early and can add capacity, rather than explaining it to the commissioner afterwards.
When the contract is renegotiated, you have a clean history of activity to bring to the table.
The work also stops depending on one person. At the moment, the return is often built by the only member of staff who understands the spreadsheet. With definitions written down and the assembly automated, someone else can check and submit it when that person is on holiday, and the figures will be built the same way.
Is your NHS return built like this?
- The monthly return takes days of spreadsheet work
- Figures are pieced together from several sources
- The commissioner queries numbers most months
- NHS and private activity are hard to separate
- You only see waiting time trends after month end