Four partners, four spreadsheets, three days before the deadline
Part of your provision is delivered by subcontracted partners. Each month they send you their learner data so you can include it in your return. One partner sends a tidy spreadsheet on time. Another sends one with columns in a different order and dates in three formats. A third sends a PDF. The fourth sends nothing until you chase them twice.
Your data officer then spends days turning these into something your MIS can accept, checking for learners who have vanished since last month, questioning start dates that changed, and emailing partners with questions that are answered slowly. Evidence to support the data, such as signed agreements, arrives separately or not at all.
Why partner data is always hard work
- There is no agreed format, or there is one but partners drift from it.
- Errors are found by your team after submission rather than by the partner at upload.
- Nothing compares this month's data with last month's, so disappearing learners are spotted by eye.
- Questions to partners go by email and get lost.
- Supporting documents are sent separately from the data they support.
The cost of fixing it by hand
Every hour your data officer spends reformatting partner spreadsheets is an hour not spent checking your own data. Errors that slip through affect your return and your relationship with the partner. And oversight of subcontracted delivery depends on your data being right; if you only see partner data in a hurry each month, it is hard to see problems building.
How you oversee your partners and what they must provide is set by your contracts and the rules you work under. What we build makes the data flow reliable and visible.
A partner data portal
- Each partner gets a login to a simple portal, with their learners from last month already listed.
- They update each learner or upload a file in your template; the portal checks formats, required fields and valid values as they go, and explains any error in plain words.
- Changes from last month are highlighted for the partner to confirm: new starts, withdrawals, changed dates, learners missing from the upload.
- Supporting documents are uploaded against the learner they support.
- Your data officer sees each partner's submission with the changes listed, can raise a question on any learner, and the partner answers in the same place.
- Approved data is exported in the format your MIS imports, so nothing is retyped.
| Check at upload | Example | Who fixes it |
|---|---|---|
| Format | Date written in a different style | Portal fixes or asks the partner |
| Required field missing | No planned end date | Partner, before submitting |
| Invalid value | Standard code not recognised | Partner, before submitting |
| Change from last month | Learner no longer listed | Partner confirms withdrawal or corrects |
| Query from your team | Start date looks wrong | Partner answers in the portal |
Month end with partners, done calmly
Partners know their deadline and get a reminder a few days before. Most submit on time because the portal makes it easy and tells them straight away if something is wrong. Your data officer opens a status page: three partners submitted, one not yet. They review the changes, raise two questions, and approve.
Partners benefit as well. They find out about a missing field while they still have the learner's file open, not a week later in an email from your data officer, and they can see their own submission history and any open questions in one place.
Over time you build a record of each partner's data quality and timeliness, which helps in contract reviews. When a partner's learners start disappearing month after month, you see it as a pattern rather than as individual surprises.
Is partner data a monthly headache?
- Partners send data in different formats.
- Your data team reformats partner spreadsheets before every return.
- Learners disappear from partner data without explanation.
- Questions to partners get lost in email.
- Supporting documents arrive separately or late.