The last three days of every month
Your MIS or data officer knows the pattern. As the return deadline approaches, they run the validation in your MIS and fix what it flags. That catches the formatting errors. It does not catch the learner who withdrew three weeks ago but whose coach has not told anyone, or the planned end date that changed in the e-portfolio and not in the MIS, or the learner whose employer changed and whose record still shows the old one.
So the data officer emails coaches asking them to confirm their caseloads. Half reply. They spot a few problems by eye, fix what they can and submit. Next month, a correction goes in for last month's error, and the cycle repeats.
Why the MIS is often out of step
The MIS is the record used for the return, but most of the real changes happen elsewhere first.
- Coaches learn about withdrawals, breaks and changes of employer in conversation, and record them in the e-portfolio or in an email.
- Signed documents such as training plan changes are stored separately from the data fields they affect.
- Several systems hold a planned end date, and they drift apart.
- Updates to the MIS depend on someone forwarding the change to the data team.
- The checks built into the MIS test whether the data is valid, not whether it is true.
What errors cost in time and trust
Corrections take time every month, and they make your figures harder to rely on. Your finance team forecasts on data that later changes. Your managers make decisions on caseload numbers that include learners who have already left. And if data is ever examined in detail, mismatches between the return and the learner file are exactly what gets questioned.
Your data officer carries most of this, usually alone, in the busiest days of the month. We do not give funding advice; the rules on what is claimed and when stay with your team and your adviser. What we fix is the gap between what your systems say and what has happened.
The pre-return checks we build
- We connect read-only to your MIS, e-portfolio and document store, through APIs or scheduled exports.
- A set of comparison checks runs daily, not just at month end. Each one compares a field across systems, such as status, planned end date, employer, standard or recent activity.
- Mismatches go into a queue with both values shown, the learner, the coach and the date each value last changed.
- Activity checks flag learners with no logged work, review or contact for a period you set, since they may have left without anyone recording it.
- Each item is assigned to the coach or data officer to resolve, with a note of what they did.
- Before the return, the data officer sees what is still open and can hold or proceed, with a record of the decision.
| Check | Compares | Typical cause |
|---|---|---|
| Status | MIS against e-portfolio | Withdrawal known to the coach but not recorded |
| Planned end date | MIS against training plan and e-portfolio | Extension agreed but only one system updated |
| Employer | MIS against latest signed agreement | Change of employer not passed to the data team |
| Recent activity | E-portfolio and hours log against a threshold | Learner disengaged without anyone noticing |
| Documents present | Learner record against document store | Signed change not filed |
The checks are the ones your data team asks for. We start with the mismatches you already find most often and add more as they prove useful.
Month end without the scramble
Because checks run every day, most mismatches are resolved within the week they appear. The coach who forgot to record a withdrawal gets a task the next morning, not a panicked email at month end.
By the last few days of the month the queue is short. Your data officer runs the MIS validation, looks at a handful of open items, and submits knowing the return reflects what the coaches know. Corrections the following month become rare, not routine.
Signs your data needs this
- Every return is followed by corrections for things that were already known.
- Coaches are asked to confirm caseloads by email every month.
- Planned end dates differ between your MIS and e-portfolio.
- You find withdrawn learners still showing as active.
- One person holds the whole return process in their head.