How often do you have to submit the ILR?

Providers submit the ILR monthly throughout the funding year, which runs from August to July. Each return corresponds to a period (for example R01 through to R14 for the closing returns), and each has a published ESFA deadline. Every submission is a cumulative snapshot of all your current learners, not just that month's changes.

What happens if you miss an ILR submission deadline?

Missing a hard close deadline typically means your data for that period is not processed in that month's payment run, which can delay funding and affect cash flow. It can also create compliance and reconciliation issues. Providers usually set internal deadlines ahead of the ESFA date to allow time for validation and corrections.

Who is responsible for the ILR in a training provider?

Ownership usually sits with the funding or MIS team, who compile, validate and submit the return. However, accurate ILR data depends on the whole organisation – tutors and delivery staff record activity such as off-the-job training and progress, while quality and compliance colleagues ensure records match the evidence held.

Does the ILR affect Ofsted inspection?

Ofsted focuses on the quality of education and training rather than funding data directly, but accurate ILR records help you present a truthful and consistent picture of your learners, their programmes and their progress. Reliable data supports the self-assessment and management information you rely on during inspection.

What Is an ILR Submission? A Practical Guide for Apprenticeship Providers

What is the ILR?

The Individualised Learner Record (ILR) is the primary data collection used to record information about learners and their learning in the further education and skills sector in England. Every training provider that draws down public funding – whether that is apprenticeship funding through the levy and co-investment, or adult education funding – uses the ILR to tell the Education and Skills Funding Agency (ESFA) and the Department for Education (DfE) exactly who they are training, what they are studying, and how that learning is progressing.

In practical terms, the ILR is a structured dataset. For each learner it captures personal details, the programme they are enrolled on, start and planned end dates, the standard or framework being delivered, employer information for apprenticeships, and a range of records covering delivery, achievement and funding. It is the single source of truth that underpins how much funding a provider is paid and how that delivery is evidenced.

Learner details (demographics, prior attainment, additional needs)
Programme and aim information (e.g. apprenticeship standard, level, dates)
Employer and workplace details for apprenticeships
Funding and delivery records that drive payment calculations
Achievement, completion and end-point assessment (EPA) outcomes

So what is an 'ILR submission'?

An ILR submission is the act of uploading your ILR data file to the ESFA's Submit Learner Data service (often referred to as the FIS/Submit service) by a set deadline. Rather than being a one-off event, submission is a recurring, cyclical activity: providers submit their ILR on a monthly basis throughout the funding year.

The funding year runs from August to July, and each month has its own return, commonly labelled by period – for example R01 covers the first return of the year, running through to R14 as the final closing returns. Each submission is a cumulative snapshot of your entire cohort at that point in time, not just the changes made that month. When you submit, the service validates your file, runs it through the funding calculation, and produces reports that confirm what will be paid.

Because payment is driven directly by the data, the ILR submission is where funding, curriculum delivery and compliance meet. If a learner is not accurately recorded in a given period's return, the associated funding may not be generated for that month.

Why the ILR submission matters

The ILR submission is not merely an administrative formality. It is the mechanism by which providers are paid for apprenticeship delivery, and the dataset that regulators and auditors rely on when scrutinising provision.

Getting submissions right protects cash flow, supports accurate management information, and reduces the risk of clawback at audit. Inaccurate or late data can lead to underpayment, unexpected adjustments, or funding being recovered. For that reason, ILR quality is treated as a core discipline within provider quality and compliance teams.

Funding: payments for on-programme learning, EPA and achievement are triggered by ILR data.
Compliance: the ILR provides the evidence trail for ESFA funding rules and audit.
Performance: achievement rates and other published measures are derived from ILR returns.
Ofsted context: while Ofsted inspects quality of education rather than funding data, accurate records help you present a truthful picture of your learners and their progress.

How the monthly ILR cycle works

Each period follows a broadly similar rhythm. Data is captured throughout the month in your management information system, reconciled against your delivery and evidence, then exported as an ILR file and submitted before the deadline. The ESFA publishes a schedule of return dates for the year, and hitting each 'hard close' deadline is essential – late submission can mean missing a payment run for that period.

A typical monthly workflow looks like this:

Update learner records: enrolments, changes, breaks in learning, withdrawals, completions and EPA outcomes.
Reconcile: check that off-the-job training hours, actual delivery and evidence match what the data says.
Validate: run the file through validation to identify and resolve errors and warnings.
Submit: upload the return to the Submit Learner Data service before the deadline.
Review reports: check funding summary reports and error reports, then plan corrections for the next return.

Common ILR errors and how to avoid them

Most funding issues at audit trace back to data that does not match delivery on the ground. The good news is that the most frequent problems are avoidable with disciplined monthly processes and clear ownership between delivery, funding and compliance teams.

Rather than treating the ILR as a month-end scramble, effective providers keep records accurate in near real time. Purpose-built apprenticeship management software such as Journey can help by keeping learner records, off-the-job hours and evidence aligned throughout the month, so the export is a reflection of clean, reconciled data rather than a last-minute reconstruction.

Late recording of withdrawals or breaks in learning, causing funding to generate incorrectly.
Mismatches between recorded off-the-job training and the actual evidence held.
Incorrect start or planned end dates that distort funding profiles.
Missing or inaccurate employer and workplace details for apprenticeships.
Failing to review validation errors and funding reports before the next return.

Good practice for reliable submissions

Build a repeatable monthly routine with clear responsibilities and internal deadlines that sit comfortably ahead of the ESFA's hard close. Give your funding team time to reconcile, validate and correct rather than submitting at the last moment.

Treat the ILR as a shared responsibility. Tutors and delivery staff generate much of the underlying activity, so accurate, timely recording at their end makes the submission far smoother. Regular data-quality checks, sample audits against evidence, and reviewing funding reports each period will keep surprises to a minimum and keep your provision audit-ready.