Monday's caseload meeting
Your delivery manager has eight skills coaches, each with a caseload across several standards and dozens of employers. The weekly meeting begins with each coach talking through their learners who are behind, on a break, about to reach gateway or not responding. Each coach has their own spreadsheet or notes. Some are thorough. Some are optimistic.
When a new learner needs allocating, the manager does not know who has room. When a coach is off sick for two weeks, nobody else can quickly see what their learners need. When the managing director asks how many learners are at risk of not completing on time, the answer takes a day to build.
Why the picture is always second hand
- Progress against the plan is in the e-portfolio.
- Off-the-job hours are in the hours log.
- Review dates are in the coach's calendar or another report.
- Learner status and planned end dates are in the MIS.
- Informal knowledge, such as an employer restructure, is in the coach's head.
Each system has its own reports, but none shows a single learner's situation across all of them, and none shows a caseload the way a manager needs to see it.
What a missing caseload view costs
Coaches spend time preparing updates instead of coaching. Managers spot problems late. Workload is uneven, because nobody can see that one coach has twice the at-risk learners of another. Cover during absence is poor, and learners notice.
The deeper cost is that risk is found at the end, not the middle. A learner who has not progressed for three months is much harder to get back on track than one noticed at three weeks.
The caseload view we build
What we build reads from the systems you already have and shows the result in one place.
- We connect to your MIS, e-portfolio and hours log, read-only, through APIs or scheduled exports.
- For each learner we calculate simple measures you agree: progress against plan, hours against plan, days since last review, days since last activity, weeks to planned end date.
- Each measure has a threshold you set, and a learner who crosses one gets a flag with the reason in plain words.
- Coaches see their own caseload sorted by flags; managers see every coach, with counts by status and a click through to any learner.
- Coaches can add a short note to a flagged learner, such as employer restructure, call booked Thursday, which the manager sees too.
- A weekly summary goes to the manager by email, with changes since last week.
| Measure | Source | Example flag |
|---|---|---|
| Progress against plan | E-portfolio | Behind plan for several weeks |
| Off-the-job hours | Hours log | Well under planned profile |
| Last progress review | E-portfolio or calendar | Overdue |
| Last learner activity | E-portfolio and hours log | No activity recently |
| Planned end date | MIS | Close, with gateway items missing |
A shorter meeting and earlier action
The Monday meeting now starts from the screen. The manager looks at the flagged learners, reads each coach's note, and spends the time on the few that need a decision. Allocation of new learners looks at real caseload sizes and risk, not guesswork.
Allocation also gets fairer. A coach whose caseload is full of learners close to gateway has a very different month from one whose learners all started recently, and the view makes that visible when new starts are shared out.
When a coach is off, the manager opens their caseload, sees which reviews are due and which learners are flagged, and hands them to a colleague with the notes attached.
Could your team use this?
- Coaches prepare caseload updates by hand each week.
- Managers ask coaches for information that exists in your systems.
- Absence cover is slow because caseloads are not visible.
- Learners at risk are found late in the programme.
- Workload between coaches is hard to compare.