ILR data quality: the pre-submission checklist for adult-learning providers
Good Individualised Learner Record (ILR) data comes from checking records every month, not only in the week of a return. Validate the full file after each monthly return window opens, give every error an owner, and read the funding reports that come back. Check the data again at enrolment, because most submission errors start there. In submission week, freeze routine changes, clear every error, and explain every large change from the last return.
What is the difference between validation and submission?
Validation checks an ILR file against the rules of the ILR specification. Submission sends the file to the Department for Education (DfE). The DfE's Funding Information System (FIS) is a tool that providers run before submission: it validates the file and shows the funding it will generate. The Submit learner data service then accepts the file, validates it again and returns reports. Errors stop records being funded; warnings do not, but they often become errors later.
When are ILR returns due?
The ILR is returned monthly. Returns R01 to R12 follow the months of the funding year from August to July. R13 and R14 are the final returns after the year ends, in September and October. The DfE publishes the exact dates for each year in the ILR guidance.
Which fields fail most often?
Typical problem areas are the unique learner number (ULN), prior attainment, postcode, employment status, learning delivery dates and outcomes, and funding and monitoring codes.
What should we check at enrolment?
- Check the ULN against the Learning Records Service. Resolve differences in name or date of birth at once.
- Record prior attainment. It controls eligibility and funding.
- Record postcode, employment status and household situation carefully.
- Collect learning support and health information with the correct consent wording.
- Attach eligibility evidence at enrolment, not during audit preparation.
What is the monthly routine?
- Validate the full file soon after the monthly return window opens.
- Work the exceptions each week. Give each exception a named owner.
- Read the funding reports that come back after each return. A flag that repeats is a process problem.
- Track missing outcomes, overdue planned end dates and unchecked ULNs by curriculum area.
- Keep an audit trail of who changed what, and why.
What do we do in submission week?
- Set a cut-off for routine changes, so the file is stable while it is checked.
- Clear every error and read every warning.
- Compare totals with the last return, and explain every large change.
- Have a named person approve the return. Keep the file and reports with the evidence.
How Envelope Adult Education does this
Envelope Adult Education validates each learner record when staff enter it, puts each exception in an owned work queue, keeps the audit history of every change and produces the ILR file for each return. Envelope Adult Education →
Sources
See it with your own data
We will show this process in Envelope Adult Education, with examples from your organisation.
