Learning support: the evidence chain from need to claim

To claim learning support you need to show four things, in order.

• The need was assessed, and the assessment is dated before the support started.
• The support was actually provided.
• It cost what you are claiming, where the stream expects cost to be evidenced.
• The record reflects it correctly.

Audit tests the chain end to end and a gap anywhere breaks it. The most common gap is the second link: support delivered informally by teaching staff, genuinely and consistently, with no record that it happened.

The second most common is the first: a need that is obvious to everyone who works with the learner and has never been written down.

Create a support plan at the point of assessment and record delivery against it as it happens. Maintain cost records alongside, where the stream expects the claim to reflect cost.

Reconcile learners with support monitoring recorded on the ILR against learners with a support plan on file, termly. Differences in either direction are findings.

Learning support exists across 16 to 19, adult and apprenticeship provision, but the way it is claimed is not the same in each.

Check the rules for the stream you are working in rather than assuming what you know from another.

The underlying principle is constant: need, provision, cost, claim, evidence. What differs is how the claim is made, what it is worth and what the rules require you to hold.

High needs funding is a separate arrangement again, built from place funding and a local authority top-up, and should not be confused with learning support within a programme.

Take the claim mechanism, the monitoring codes and the evidence requirements from the funding rules for the stream and funding year.

Where a learner attracts both high needs funding and learning support, be clear which costs sit against which, because the evidence expectations differ.

The chain breaks in predictable places, and each has a straightforward fix.

• Assessment never written down: make the support plan the trigger for the claim.
• Support delivered informally: give course teams a simple way to record it.
• No cost records: attribute cost as support is delivered, not at year end.
• Codes applied to a group: set the code from the individual plan.

The most effective single change is to make the support plan the thing that triggers the claim, rather than the monitoring code. If no plan exists, no code is applied, and the chain cannot break at the first link.

The second is to give teaching staff a route to record support that takes seconds rather than minutes. Informal support is real and valuable, and it goes unrecorded because recording it is inconvenient rather than because anybody is careless.

The third is a termly reconciliation in both directions: learners with codes but no plan, and learners with plans but no codes. The second list is often larger than the first, and it represents support the college is delivering and not claiming.

Where a claim genuinely cannot be substantiated, remove it and record the decision. A removed claim with a documented reason is a far better position than a claim that fails at audit.

Model the support plan as the master record, with delivery sessions recorded against it and cost attributed per session or per period. The ILR monitoring records are then generated from the plan rather than entered independently.

Report the two reconciliation directions separately each term, with counts rather than lists, so the trend is visible and the conversation is about process rather than individual learners.