ILR R13 Deadline Checks for Training Providers
R13 is an important checkpoint for training providers reviewing the accuracy and completeness of their Individualised Learner Record (ILR) data. For the 2025 to 2026 funding year, the R13 latest return date is 14 September 2026, with the final ILR return due on 23 October 2026.
Completing thorough ILR R13 deadline checks can help providers identify outstanding validation errors, incorrect learner records, funding data issues and gaps in supporting evidence before the return is submitted. It also provides an opportunity to review reports such as PDSAT and compare ILR data against internal records, helping to identify issues that may need attention ahead of the final return.
This guide provides a practical ILR R13 deadline checklist for training providers, covering the key data quality checks, reports and evidence that should be reviewed before the deadline.
⠀
Table of Content:
⠀
What Is ILR R13?
R13 is one of the Individualised Learner Record returns submitted during the funding year.
The ILR timetable sets out when providers need to submit their data and the purpose of each return. The Submit Learner Data Provider Support Manual states that the return date is the hard close date for including data in the national database for that return.
Providers must therefore ensure their data is complete and fit for purpose by the relevant return date. Data submitted after the relevant deadline will not be processed for that particular return.
For the 2025 to 2026 funding year, the published timetable gives the following key dates:
Return | Latest return date |
R04 | 4 December 2025 |
R06 | 5 February 2026 |
R10 | 4 June 2026 |
R13 | 14 September 2026 |
R14 | 22 October 2026 |
⠀

Why Are R13 Checks Important?
R13 sits towards the end of the funding year, which means there is less time to resolve significant data issues before the final return.
A provider may have accumulated changes throughout the year involving:
Learner starts
Withdrawals
Transfers
Changes to learning delivery
Achievement information
Funding information
Employment information
Apprenticeship records
Learning aim details
Changes to learner circumstances
Leaving these checks until the final return can create unnecessary pressure.
The Provider Support Manual states that the final ILR return must include the learner and learning delivery data returned during the year, including amended records.
R13 is therefore an important point to review the quality of the data before moving towards the final return.
⠀
Need an Independent ILR Review?
If your team is approaching R13 with a backlog of data checks, recurring validation issues or uncertainty around funding related records, an independent review can help identify areas requiring further investigation.
Skills Office Network can support training providers with ILR, funding and data related reviews, helping organisations identify potential issues and strengthen their processes.
⠀
ILR R13 Deadline Checks for Training Providers
The following checks can help structure your R13 preparation.
⠀
1. Check the R13 Deadline
Start by confirming the applicable deadline for your funding year and provider type.
For 2025 to 2026, the latest R13 return date is 14 September 2026. For 2026 to 2027, the published R13 date is 14 September 2027.
Do not assume that a previous year’s date will remain unchanged.
The official ILR timetable should be treated as the source of truth for the relevant funding year.
Also remember that the Submit Learner Data guidance states that data needs to be complete and error free for the purposes of the relevant return by the applicable deadline.
⠀
2. Review Outstanding Validation Errors
Validation errors should be reviewed before the R13 submission.
Consider:
Which errors remain outstanding?
Who owns each issue?
Can the underlying learner record be corrected?
Does the correction require supporting evidence?
Could the issue affect funding?
Are similar errors appearing across multiple records?
Has the root cause been identified?
A list of validation errors is useful, but resolving the underlying cause is more valuable.
For example, if the same issue is appearing repeatedly across a cohort, the provider may need to review the process that is generating the data rather than correcting individual records one at a time.
The current ILR technical resources include validation rules for the relevant funding year, alongside the ILR specification and other technical documents.
⠀
3. Review Learner Starts
Check that learner starts have been recorded accurately.
Review:
Start dates
Learning aims
Programme information
Funding information
Learner details
Eligibility information
Required monitoring information
The Provider Support Manual states that new starts must be reported within two reporting months of their start date.
A R13 review is a useful opportunity to identify learners who may have started earlier in the year but whose records remain incomplete.
⠀
4. Check Withdrawals and Leavers
Withdrawal and leaving information should be reviewed carefully.
Check whether:
Learners who have left have been recorded correctly
Actual end dates are accurate
Withdrawal reasons have been recorded where required
Learning delivery records reflect the learner’s actual position
Apprenticeship withdrawals have been reported within the required timescale
The Provider Support Manual states that apprenticeship withdrawals must be reported within three reporting months of the leave date.
⠀
5. Review Achievements and Outcomes
Achievement data can have a direct relationship with funding and performance information.
Review:
Learning aims that have been completed
Achievement dates
Completion information
Outcome information
Evidence supporting the recorded outcome
Any outstanding results
Records where the expected outcome does not match the learner’s current position
The Provider Support Manual explains that achievement funding for relevant Adult Skills Fund learning aims completed in the current year will only be paid where the achievement is reported in the current year.
This makes accurate and timely outcome recording an important part of year end data preparation.
⠀
6. Check Apprenticeship Records
Providers delivering apprenticeships should undertake additional checks on their apprenticeship data.
Depending on the provision and circumstances, this may include reviewing:
Programme information
Learning aim information
Start dates
Planned end dates
Actual end dates
Breaks in learning
Withdrawals
Completion information
Achievement information
Employment details
Funding information
Relevant monitoring information
Apprenticeship data can involve multiple linked records and funding rules, so providers should make sure that the information held in their systems accurately reflects the learner’s actual position.
⠀
Are Apprenticeship Data Issues Repeating Across Your Provision?
Repeated ILR issues can sometimes indicate a process problem rather than isolated data errors.
Where the same issues continue to appear, an independent review can help providers look beyond individual records and consider whether their data collection, quality assurance or internal processes need strengthening.
Skills Office Network can help providers review their current position and identify areas that may require further attention.
⠀
7. Review Funding Related Data
R13 is also an important point to review records that contribute to funding calculations.
Depending on your provision, consider checking:
Funding models
Funding eligibility
Learning aim funding information
Funding eligibility dates
Prior learning
Attendance and participation information
Planned and actual hours
Additional funding information
Funding monitoring fields
Changes that could affect the funding generated
The exact checks required will depend on the funding stream and the learner’s circumstances.
Providers should always use the relevant funding rules, ILR specification and current technical guidance rather than relying on historic practice.
⠀
8. Check Your EAS Position
Where applicable, review your Earnings Adjustment Statement alongside your ILR data.
The EAS operates alongside the ILR and allows providers to submit adjustments that cannot be represented through the ILR.
For 2025 to 2026, the published guidance states that the R13 EAS deadline is 14 September 2026.
Providers should therefore ensure that relevant EAS information is reviewed as part of their wider R13 preparation rather than treating it as a separate exercise.
⠀
9. Review PDSAT Reports
PDSAT reports can provide another layer of assurance when reviewing learner and funding data.
DfE’s ILR funding return guidance specifically refers to reviewing PDSAT reports to reduce the risk of inaccurate ILR returns.
When reviewing reports, consider:
Which issues have been identified?
Are they genuine errors?
Is supporting evidence available?
Do multiple learners show the same issue?
Does the issue indicate a wider process weakness?
Has corrective action been completed?
Has the underlying cause been addressed?
The purpose should not simply be to clear a report.
It should be to understand why the issue occurred and whether the same problem could happen again.
⠀
10. Review Data Against Your Own Systems
The ILR should reflect what has actually happened to learners.
Where appropriate, compare the submitted data against internal systems such as:
Learner management systems
Attendance records
Assessment records
Apprenticeship documentation
Enrolment records
Achievement records
Employer information
Learner files
This can help identify discrepancies between operational records and the data being prepared for submission.
The ILR specification and Provider Support Manual should then be used to determine how the relevant information should be recorded.
⠀
11. Check That Evidence Exists
Correct data should be supported by an appropriate audit trail.
Before R13, ask:
Can we evidence the information we are submitting?
Depending on the record, this could involve checking:
Enrolment evidence
Eligibility evidence
Learner declarations
Assessment records
Attendance
Employer information
Achievement evidence
Withdrawal documentation
Changes to learner circumstances
Funding evidence
The exact evidence required depends on the funding stream and data being reported.
The important point is that data should not be treated as separate from the underlying learner record.
⠀
12. Investigate Unusual Data
A good R13 review should not focus exclusively on known errors.
Look for unusual patterns.
For example:
Unexpected increases in withdrawals
Unusual achievement patterns
Large changes in learner numbers
Significant changes in funding
Repeated validation issues
Missing information across a cohort
Unexpected changes in delivery
Records that differ significantly from previous months
An unusual result is not automatically an error.
It is a reason to investigate.
⠀
R13 Data Review Checklist
Area | What to check |
Deadline | Confirm the current R13 date |
Validation | Review outstanding errors |
Starts | Check recent and historic starts |
Withdrawals | Review leaving dates and reasons |
Achievements | Check completion and achievement information |
Apprenticeships | Review programme and funding records |
Funding | Check relevant funding information |
EAS | Review adjustments where applicable |
PDSAT | Investigate relevant reports |
Evidence | Confirm an appropriate audit trail |
Internal systems | Compare ILR data with operational records |
Unusual patterns | Investigate unexpected changes |
Final review | Confirm outstanding actions are assigned |
⠀

What Should Training Providers Do Before the R13 Deadline?
A useful R13 preparation process should begin before the final submission date.
A practical sequence could be:
Step 1: Confirm the Deadline
Check the current ILR data collection timetable for the relevant funding year.
Step 2: Produce Your Outstanding Issues List
Bring together validation errors, unresolved data queries and outstanding internal actions.
Step 3: Prioritise Funding and Compliance Risks
Deal first with issues that could affect funding, eligibility, learner status or the accuracy of the return.
Step 4: Review Supporting Evidence
Make sure important records can be supported by appropriate documentation.
Step 5: Compare Internal Records
Check the ILR against the systems and records used by your operational teams.
Step 6: Run Relevant Reports
Use validation tools, PDSAT and other appropriate reports to identify potential issues.
Step 7: Complete Corrections
Give data owners clear responsibility for resolving outstanding issues.
Step 8: Complete an Independent Quality Review
Where appropriate, ask someone who was not responsible for making the original changes to review the final data.
Step 9: Submit Before the Deadline
Do not rely on the final hours before the deadline.
Step 10: Record Lessons Learned
Use recurring R13 issues to strengthen your data processes for future returns.
⠀
Common R13 Mistakes to Avoid
Leaving Checks Until the Last Minute
R13 should be part of an ongoing data quality process rather than a single deadline driven exercise.
Treating Validation Errors as the Whole Review
Validation checks are important, but a technically valid return can still contain inaccurate information.
Correcting Records Without Investigating the Cause
If the same error continues to appear, consider whether a wider process issue needs to be addressed.
Forgetting Supporting Evidence
Data should be capable of being supported by an appropriate audit trail.
Failing to Check Funding Implications
Some data errors can have implications beyond the learner record itself.
Assuming Previous Year Rules Still Apply
ILR specifications, validation rules, funding guidance and timetables can change.
The current guidance should always be checked.
⠀
How Can Training Providers Strengthen R13 Preparation?
The strongest approach is to make R13 preparation part of normal data governance.
Instead of waiting for the deadline, providers can establish regular processes for:
Reviewing validation errors
Checking learner starts
Monitoring withdrawals
Reviewing achievements
Checking funding information
Reviewing PDSAT reports
Comparing operational records
Investigating unusual patterns
Recording corrective actions
Monitoring recurring issues
This creates a clearer picture of data quality throughout the year and can reduce the amount of work required immediately before a return deadline.
⠀
When an Independent ILR Review Can Help
Internal teams may already have effective processes in place, but there can be value in bringing in an independent perspective when:
The same errors keep recurring
There is a significant backlog of data checks
Staff capacity is limited
Funding implications are unclear
A provider has experienced recent organisational change
New provision or funding streams have been introduced
Internal teams want an additional quality assurance check
There is uncertainty about whether existing processes are sufficiently robust
Skills Office Network can support training providers with independent review and practical advice around funding, data and compliance.
⠀
R13 and the Final ILR Return
It is important to understand the relationship between R13 and R14.
R13 is not the final ILR return of the funding year.
For 2025 to 2026, the final ILR return is due on 23 October 2026. The DfE guidance also states that the final return includes learner and learning delivery data returned during the year, including records that have been amended.
R13 therefore provides an important opportunity to identify and address outstanding issues before the final stage of the funding year.
For providers preparing for R14, the quality of the R13 review can help create a clearer starting point for final checks.
⠀
What Happens If Data Is Not Ready?
The Submit Learner Data guidance describes the return date as a hard close for the relevant collection.
This means providers should not plan their process around the assumption that there will be additional time after the deadline.
The Provider Support Manual states that data must be complete and fit for purpose by the return date and that data sent after 6pm on the return date will not be processed for that particular return.
This is why providers should build internal deadlines ahead of the official R13 deadline.
⠀
Final ILR R13 Deadline Checklist
Before submitting your R13 return, ask:
☐ Have we confirmed the correct R13 deadline?
☐ Are all outstanding validation errors being addressed?
☐ Have recent learner starts been checked?
☐ Have withdrawals and leavers been reviewed?
☐ Have achievement and completion records been checked?
☐ Have apprenticeship records been reviewed where applicable?
☐ Have funding related fields been checked?
☐ Have we reviewed relevant EAS information?
☐ Have relevant PDSAT reports been investigated?
☐ Have ILR records been compared with internal systems?
☐ Have unusual patterns been investigated?
☐ Is supporting evidence available?
☐ Are outstanding actions assigned to named people?
☐ Has the data received an appropriate final quality review?
☐ Are we working to an internal deadline ahead of the official close?
⠀
Conclusion
The ILR R13 deadline should be treated as an important data quality checkpoint rather than simply a submission date.
For training providers, effective preparation means checking learner records, validation errors, funding information, achievements, withdrawals, apprenticeships, EAS information, PDSAT reports and supporting evidence.
The current ILR timetable and Provider Support Manual should always be used when confirming deadlines and technical requirements, as these can change between funding years.
For 2025 to 2026, R13 is due by 14 September 2026, giving providers a clear point at which their data needs to be ready for the relevant return.
The earlier your organisation identifies and investigates data issues, the more opportunity there is to resolve them before the final stages of the funding year.
⠀
Need Support With Your ILR and Data Quality Processes?
If your organisation is approaching R13 with outstanding data issues, recurring validation errors or concerns about the quality of your current processes, an independent review can provide an additional perspective.
Skills Office Network can help training providers review their current position, identify areas requiring further investigation and strengthen practical data and compliance processes.



