Tool

Generate a readiness checklist

Scoped to your funding stream, the return you are preparing for and your role. Built from 16 version-controlled templates, so the same choices always produce the same checklist and nothing is invented.

Readiness checklist · Bootcamps · 2026-27

22 checks across 6 areas

0 of 22 ticked. Ticks are kept on this page only and are cleared when you leave.

Monthly return readiness

The checks to run before every ordinary return. Short, repeatable, and the reason the consequential returns are manageable.

Every learner recorded as in learning is genuinely still attending

Why: A learner who has left but is still recorded as continuing generates funding that is not earned, and the aim eventually resolves as a non-achievement.
Owner: MIS or ILR officer
Evidence: Registers, or a curriculum lead's written confirmation of the current cohort
Where to look: Your own in-learning report, and a no-recent-attendance report

Red flags

Learners with no attendance recorded for several weeks
Learners past their planned end date with no explanation
A curriculum area that does not recognise names on its own list

Every aim that has ended carries an outcome, or the reason it does not is known

Why: An aim with no achievement recorded counts as a non-achievement in the qualification achievement rate, permanently once the year closes.
Owner: MIS or ILR officer
Evidence: Awarding organisation results, or a dated note of why the result is outstanding
Where to look: Your own ended-with-no-outcome report

Red flags

A whole cohort with no outcomes recorded
Outcomes outstanding from a results window that closed weeks ago
The same awarding organisation appearing repeatedly

Validation is clean, or every remaining failure is understood, accepted and documented

Why: Records that fail validation may be excluded from funding, and unresolved failures are treated as a control weakness.
Owner: MIS or ILR officer
Evidence: The validation error report, worked and annotated
Where to look: Local validation output and the submission validation report

Red flags

A large number of failures of a single rule
Warnings dismissed without being read
The same failures recurring every period

The funding position reconciles to expectation, and any movement is explained in writing

Why: An unexplained movement is a data problem that has not been located yet, and explaining it later is far harder than explaining it now.
Owner: Finance director or finance manager
Evidence: A written reconciliation comparing this period with the last
Where to look: Funding reports for this period and the previous one

Red flags

A material movement nobody can account for
A movement with an unchanged learner count
Reconciliation performed only at year end

Every leaver notified by curriculum has been recorded, with the real last date of attendance

Why: The date sets where funding stops and which achievement cohort the aim falls into. Using the notification date overstates funding and contradicts the register.
Owner: MIS or ILR officer
Evidence: Leaver notifications matched against recorded withdrawals
Where to look: Notification log and the withdrawal report

Red flags

A backlog of unprocessed notifications
Actual end dates clustering on processing dates rather than attendance dates
Withdrawals recorded weeks after the last attendance

Funding audit readiness

What to have in place before an audit, across every stream. Most of it is the routine you should be running anyway.

The evidence retrievability test has been run and the result is known

Why: Evidence that cannot be found within a reasonable time does not help at audit, however genuinely it was created.
Owner: Funding or compliance officer
Evidence: The test result: how many of a sample could be produced, and how quickly
Where to look: A random sample of learners across streams

Red flags

Evidence held by individuals
Evidence in more than one place with no index
A low retrieval rate

Data quality and funding monitoring reports have been worked, with outcomes recorded

Why: These reports test the same things an audit will, and they arrive while the data can still be corrected. Working them is the most effective preparation available.
Owner: Funding or compliance officer
Evidence: The exception log recording each record's outcome and where its evidence sits
Where to look: The monitoring and data quality reports for the period

Red flags

The same records recurring every period
Reports received and not worked
Correct records changed to empty a report

Changes to data already reported carry a recorded reason

Why: An unexplained change between returns is a standard audit query, and reconstructing the reason months later is far harder than recording it at the time.
Owner: Head or director of MIS
Evidence: The change log or system change history with reasons
Where to look: System audit trail and any bulk update records

Red flags

Bulk updates with no documented specification
Material changes between returns with no explanation
Changes made by people without the authority to make them

The per-period evidence set is complete: submitted file, validation output and funding reports

Why: This set answers most retrospective questions without re-derivation, and assembling it afterwards is far harder.
Owner: Head or director of MIS
Evidence: The archived set for each period of the year
Where to look: The archive of submissions and reports

Red flags

Missing periods
Reports not retained
No single location for the archive

No learner appears more than once

Why: A duplicate splits a learner's aims, hides prior attainment and distorts both funding and achievement measurement.
Owner: Enrolment, admissions or registry staff
Evidence: Identity evidence confirming whether two records are the same person
Where to look: A duplicate detection report on ULN, name and date of birth

Red flags

New ULNs created where an existing one should have been found
Two records with the same date of birth and address
Duplicates clustering around one enrolment period

Enrolment quality review

A front-door review, which is where most funding-critical data is captured and where errors are cheapest to prevent.

ULNs are obtained or verified through the Learning Records Service at enrolment

Why: A new ULN created for somebody who already has one splits their record across providers and years, permanently.
Owner: Enrolment, admissions or registry staff
Evidence: The record of the search carried out before a new ULN was requested
Where to look: Enrolment records and ULN creation log

Red flags

New ULNs created without a documented failed search
Learners with more than one ULN

Aims are confirmed as fundable for the stream and dates before enrolment completes

Why: An aim that is not fundable produces a valid record that generates nothing, and the cost is incurred anyway.
Owner: Curriculum manager or head of department
Evidence: The learning aims database record for the aim
Where to look: Aim funding attributes checked at curriculum planning

Red flags

Aims past their funding end date
Aims not fundable for the stream
Aims added to the offer without checking

Start dates are recorded per learner, not defaulted from the class

Why: The start date fixes the applicable rules, the qualifying period and the funded period. A defaulted date claims for a period the learner was not there.
Owner: Enrolment, admissions or registry staff
Evidence: Registers showing genuine first attendance
Where to look: Enrolment records compared against registers for late joiners

Red flags

Late joiners sharing the class start date
Start dates clustering on a single day

Monthly data quality review

The standing data quality review, separate from the return checks, focused on trends rather than individual records.

The five monthly counts have been produced and the trend reviewed

Why: A count that rises is a control failure rather than a workload problem, and the trend says where to look.
Owner: Head or director of MIS
Evidence: The trend sheet for the year
Where to look: In-learning past planned end, ended with no outcome, validation failures, unexplained movement, unrecorded leavers

Red flags

Counts rising month on month
Counts produced but never reviewed
No breakdown by curriculum area

Recurring exceptions have been root-caused rather than reworked

Why: Records that recur are regenerated by a process that has not changed. Reworking them each period treats the symptom.
Owner: Head or director of MIS
Evidence: The root cause analysis and the process change made
Where to look: The exception log, filtered to recurring records

Red flags

The same records every period
No owner outside the team clearing the report

Governance assurance pack

What a governing body should see about funding, so assurance rests on measures rather than on reassurance.

The reconciliation position for each stream is reported with movements explained

Why: Governors cannot assure a position they cannot see. A reconciliation with explanations is the minimum useful report.
Owner: Finance director or finance manager
Evidence: The reconciliation and the written explanations
Where to look: Funding reports against allocations

Red flags

Forecast reported without reconciliation
Movements unexplained
Only annual reporting

The data quality measures are reported with their trend and named owners

Why: A control described is not a control demonstrated. The measure is what shows it is working.
Owner: Head or director of MIS
Evidence: The trend sheet with owners
Where to look: The monthly data quality counts

Red flags

Narrative without numbers
No owners named
No trend

What is currently known to be wrong is reported, with the action and the exposure

Why: Assurance that reports only what is going well is not assurance.
Owner: Senior leader, principal or COO
Evidence: The known issues register with exposure and actions
Where to look: The issues log

Red flags

Nothing ever reported as wrong
Issues without a quantified exposure

Previous audit findings and what changed as a result are reported

Why: A finding that produced no change is likely to recur.
Owner: Funding or compliance officer
Evidence: The findings, the actions taken and the evidence they worked
Where to look: Previous audit reports and the action log

Red flags

Findings closed with no evidence of change
Recurring findings across years

New MIS starter induction

What a new member of an MIS team should be able to do, and by when. Not a funding control, but the thing that most often goes missing.

The new starter can trace one learner from enrolment to funding report

Why: The single most useful thing a new MIS starter can do. Everything else builds on it.
Owner: Head or director of MIS
Evidence: The walkthrough completed with a named colleague
Where to look: One live learner record, followed end to end

Red flags

Induction limited to system training
No walkthrough of the funding consequence

The new starter has the college's own system map

Why: Where each concept lives in your system, who owns it, and which report shows it. Specific to your configuration in a way no external guide can be.
Owner: Head or director of MIS
Evidence: The system map document
Where to look: The internal system map

Red flags

No map exists
Map not updated since the last upgrade

The new starter knows which returns matter most and why

Why: R04, R10 and R14 have consequences the others do not. Knowing that shapes how the year is worked.
Owner: Head or director of MIS
Evidence: The year plan, walked through with the new starter
Where to look: The return calendar for the funding year

Red flags

Every return treated identically
No year plan

Sign-off

Optional, and kept on this page only. It is here so a printed or exported checklist carries who completed it and when.

Completed by

Sources behind these checks

Funding allocations and data returns information

GOV.UK

Data collection timetable 2026 to 2027

Department for Education2026-27

This checklist contains no learner information and must not be used to record any. It is a readiness aid, not a substitute for the funding rules or your own assurance framework.