The official R01–R14 timetable, with a practical view of the next return, key claim points and a calendar download for your team.
Fourteen collection deadlines, with the relevant funding-claim and QAR markers in one place. Find the return you need, see what is coming and take the dates into your team’s calendar.
Dates checked against the official data collection timetable on 9 September 2026. Each collection closes at 6pm UK time.
| Return | Closes at 6pm | Time remaining | Timetable notes |
|---|---|---|---|
| R01 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R02 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R03 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R04 | 18:00 · Europe/London | 6pm UK time | Reference date: 1 November 2026 |
| R05 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R06 | 18:00 · Europe/London | 6pm UK time | Mid-year funding claims; reference date: 1 January 2027 |
| R07 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R08 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R09 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R10 | 18:00 · Europe/London | 6pm UK time | Year-end funding claim; QAR data collection; reference date: 1 May 2027 |
| R11 | 18:00 · Europe/London | 6pm UK time | Standard monthly collection |
| R12 | 18:00 · Europe/London | 6pm UK time | QAR data collection |
| R13 | 18:00 · Europe/London | 6pm UK time | Reference date: 31 July 2027 |
| R14 | 18:00 · Europe/London | 6pm UK time | Final funding claims; QAR data collection; reference date: 31 July 2027 |
Showing 14 of 14 returns.
The download contains the displayed returns as fixed calendar events. It is not a live subscription. Check the official timetable before each return.
Choose a date that leaves your team time to investigate errors, obtain missing evidence and revalidate. The right buffer depends on your provision and the work outstanding. A local cut-off is your operational plan, not another government deadline.
Check which learner changes are included, who owns unresolved issues and whether the file reflects the intended funding year. Pay particular attention to changes of circumstance and records handed between teams.
Check the response from the official service and keep the evidence of what was submitted. Record any correction or follow-up with an owner. An uploaded file and a resolved return are different points in the workflow.
Autumn requires deliberate naming. Keep the year next to the R number in task lists, folders, meeting notes and calendar invitations so that a discussion about “the next return” refers to the same dataset for everyone.
This calendar starts with R01 on 4 September 2026 and finishes with R14 on 21 October 2027. Filtering the table changes which dates are included in your download. It does not remove a collection from the full timetable.
Use the 2025/26 timetable for that year’s R13 and R14, which close in September and October 2026. Give each year its own clear return checklist and reconcile both against the appropriate records.
Journey’s funding and ILR capability is designed around the learner record, so delivery changes and return preparation share their underlying context. This public calendar is available without an account; it does not create a workspace task, validate a file or submit data.
The published timetable states 6pm. This calendar uses 18:00 UK time and its download accounts for GMT and British Summer Time. A deadline is the point by which the return must be submitted, not a recommended time to begin uploading it.
A new funding year begins while the previous year still has post-year returns open. For example, the 2025/26 R13 and R14 periods fall in September and October 2026 while 2026/27 R01 and R02 also occur. Check the funding year in the return, not just the R number. This table contains 2026/27 only.
R12 is the final in-year collection. R13 and R14 are later collections for that same funding year, with R14 the final collection. Review the published submission requirements, data corrections and funding-claim guidance with your funding lead before the year closes.
They reproduce the reference dates and funding-claim or qualification achievement rate markers shown in the official timetable. They help you identify collections that need particular attention. A marker is not a complete list of your organisation’s submission obligations or a replacement for the associated guidance.
No. The .ics file is a snapshot of the dates displayed here. If the official timetable changes, check the revised dates and replace the imported events. Stable event identifiers help compatible calendars recognise an updated import, but calendar applications handle re-imports differently. Verify the result in your own calendar.
No. Calendar events are planning aids. Journey’s ILR workflow is a separate capability for preparing returns from the learner record and reviewing data-quality issues. Your authorised team remains responsible for checking, submitting and reviewing the official submission result.
Contact the organisation’s funding or MIS lead, check the official submission and payment guidance and establish which collection can accept the data. Record the impact and the agreed recovery action. Do not assume that a later upload removes an earlier payment delay or other obligation.
The dates and collection markers above were checked against the official ILR data collection timetable for 2026 to 2027, published in the Submit Learner Data guidance. The timetable gives a January 2026 update date; Journey checked it on .
There may be changes in-year. Use the government service as the source of truth, particularly before a collection closes. Journey’s filtering, countdown and calendar export are convenience features built around that published information.
Bring your learners’ journey, your team’s questions and your next ambition.
