What curriculum decisions do to funding

Four ordinary curriculum decisions change funding more than anything MIS can do afterwards.

• Which aims a learner is put on.
• How many hours are planned and timetabled for them.
• How quickly a leaver is reported, and with what date.
• How quickly a result is passed on.

Aim choice decides whether an aim is fundable at all for the stream and the learner. Planned hours decide the funding band for 16 to 19 students, which sets the rate for the whole year. Leaver reporting decides how much funding is claimed for someone who has gone, and whether the aim sits in the achievement rate. Results reporting decides whether an aim counts as an achievement or as a non-achievement.

None of those is a data entry task. They are all curriculum decisions that happen to be recorded by somebody else.

Aim eligibility is an attribute of the learning aim reference on the learning aims database, scoped by stream and by date. An aim that is not fundable for the stream produces a valid ILR record that generates nothing.

Planned hours comprise planned learning hours and planned employability, enrichment and pastoral hours, and determine the funding band and therefore the national funding rate applied for the year. Hours must be planned, timetabled, education-related and evidenced.

Actual end date, completion status and outcome drive both the funding period and the qualification achievement rate, and are the fields most often populated late.

MIS can only record what it is told. The two things worth being fast about are leavers and results.

• A leaver: within days, with the real last date of attendance.
• A result: as soon as it is known, not at the end of term.
• A timetable change that alters hours: before the next return.
• A learner who has moved onto a different aim: immediately.

The date matters as much as the fact. A withdrawal recorded with the date it was noticed rather than the date the learner stopped attending overstates funding and can put the aim in the wrong achievement cohort.

Results held back to be entered as a batch are the single largest cause of unrecorded outcomes, because the batch is often never completed before the year closes.

Set a notification service level in working days and measure against it. Report the number of withdrawals whose actual end date precedes the notification date by more than the agreed window, by curriculum area.

That single measure converts an abstract data-quality conversation into an operational one with a named owner.

Thinking about funding when you design a programme is legitimate. Recording something that did not happen is not. The line between them is simple: is it real?

Designing a fuller programme, with more genuinely planned and timetabled activity, is good curriculum practice and it happens to attract more funding. Nobody should feel uncomfortable about that.

What is not legitimate is recording hours that are not delivered, counting activity that does not meet the conditions in the rules, or choosing a funding model because of what it pays rather than because it describes the provision.

The practical test is whether the plan would survive a reconciliation against the delivered timetable. If it would, it is a curriculum decision with a funding consequence. If it would not, it is a funding decision dressed as a curriculum one, and it will be found.

The same test applies to aims. Checking that an aim is fundable for the stream and the dates before it goes into the offer is planning. Discovering it in November is an avoidable cost.

Build two checks into the curriculum planning cycle: aim funding attributes confirmed on the learning aims database before the offer is published, and planned hours derived from the timetabling system rather than from a programme template.

Both are cheap at planning time and expensive at any other point in the year.