Set Up ILR Data Collection with the Learner Entry Tool: A Practical Checklist for Small Providers

The ILR Learner Entry Tool (LET) is designed for further education providers that need to create Individualised Learner Record (ILR) data but do not use a data management system. It lets providers manually create ILR data in XML files for an academic year. The Department for Education describes it as optional and particularly useful for smaller providers; its guidance indicates that performance may be affected above 500 learner records.

The official guidance page was last updated on 11 August 2026, rather than 21 August 2026. For small providers, the practical challenge is rarely just entering fields into a tool. It is building a dependable process around the tool: knowing which evidence is needed, who checks it, where it is stored, and what happens when a learner’s circumstances or programme details change.

This article translates that operational challenge into a repeatable workflow. It is not a replacement for the current ILR specification, funding guidance, validation rules, submission timetable, or your contractual obligations. Use the relevant current Department for Education materials when deciding which data is required and how it must be recorded.

What the ILR Learner Entry Tool does

The LET helps a provider assemble ILR data into an XML file. It is intended for providers without a data management system and should be downloaded in the version that matches the academic year for which data is being prepared. The tool is not the same as a complete quality-assurance process: the official user guidance states that LET does not validate data. That means your team still needs an evidence-led check before data is exported and submitted.

Think of the tool as the place where approved information is entered, not the place where information is first discovered or interpreted. A small provider will normally work more reliably when learner-facing staff collect evidence and record changes during delivery, while a named ILR owner enters, checks, exports, and tracks the data file.

Before you begin: create one source of truth

Before opening the ILR Learner Entry Tool, make a simple learner-record map. Its purpose is to prevent staff from searching across email inboxes, paper folders, enrolment forms, and teaching notes each time a record needs updating.

For every learner, identify the approved location for the information and evidence your organisation needs to support its ILR return. Your map can be a controlled spreadsheet, a secure enrolment system, or a structured learner folder. What matters is that it is current, access-controlled, and understandable to the person covering the work if the usual administrator is unavailable.

Do not treat the examples in this table as a list of mandatory ILR fields. The current ILR specification and provider guidance determine the data requirements. The table is a practical way to organise evidence and accountability before data entry begins.

A step-by-step workflow for smaller providers

1. Confirm the reporting year and working tools. Download the appropriate academic-year version of LET. Keep a record of the version used, the date it was installed, and the staff member responsible for maintaining it.
2. Set up a secure working area. Decide where the live LET file, exported XML files, supporting evidence, and quality-assurance log will be held. Avoid using personal email accounts or uncontrolled desktop folders as the only location for learner records.
3. Build a programme reference sheet. For each programme offered, record the internal programme name, delivery lead, applicable learning aim or standard reference, expected timetable, and the source used to verify those details. Check current official reference material before entering codes.
4. Complete enrolment checks before entry. Gather the provider-approved evidence needed for enrolment and eligibility decisions. Record missing items in a follow-up list instead of relying on memory or informal messages.
5. Enter learner and learning-delivery information. Enter information from checked records, using consistent internal conventions for filenames, learner identifiers, and document locations. Where a field is unclear, pause and consult the current specification or relevant guidance rather than guessing.
6. Record changes as part of delivery. Programme changes, withdrawals, completions, support changes, and corrections should trigger a documented review. A short change log makes it easier to see who updated a record, when, and which evidence supported the change.
7. Export only after a second-person or second-pass review. In a one-person provider, the second pass may be a scheduled review completed on a different day using a printed or filtered checklist. The goal is to review the record with fresh attention, not simply to re-read it immediately after entry.
8. Use the relevant submission and checking services. The DfE’s ILR collection pages distinguish between creating data, checking data quality, and submitting learner data. Follow the current process and timetable for your type of provision, leaving time to investigate reported errors or warnings.

Assign responsibilities when one person wears several hats

Small providers often cannot separate admissions, teaching, quality assurance, and data administration into different jobs. That is workable if roles are explicit. The same person may complete more than one task, but each task should still have a named owner, a review point, and an evidence location.

A responsibility matrix is particularly valuable where tutors enter information directly. It clarifies that tutors provide timely, factual delivery updates, while the person responsible for ILR administration checks that the record is complete and aligned with current guidance.

Pre-submission quality-assurance checklist

Before exporting or submitting, use a checklist that asks for evidence rather than assumptions.

• Have all active, completed, withdrawn, or changed learner records been reviewed for the reporting period?
• Does each entry match the provider’s current enrolment, programme, attendance, and progress records?
• Have learning aims, programme references, and dates been checked against the current official sources and guidance relevant to the provision?
• Are unresolved data questions recorded in an issue log with an owner and target review date?
• Has a reviewer checked a sample or all records, according to your provider’s documented approach?
• Has the exported file been stored in the approved secure location with a clear version name?
• Have relevant reports, validation outputs, errors, warnings, and corrections been reviewed through the current DfE process?

The DfE’s ILR resources include guidance on maintaining accurate data, validation, submission, and reports for possible errors. Smaller providers should turn these external steps into a short internal calendar: preparation date, data-entry cut-off, review date, correction window, submission deadline, and evidence-retention review.

Handle learner information carefully

ILR work involves personal information and may involve sensitive information. The official ILR privacy notice says providers should ensure learners have seen the notice as part of enrolment. It also explains that the ILR collects information about learners and learning and describes how the Department for Education uses personal information.

Operationally, apply data minimisation and access control: collect only information needed for your approved process, limit access to colleagues who need it for their role, and avoid copying learner data into unnecessary trackers. Keep a clear distinction between the working data file, source evidence, and informal notes. If you use a shared drive, make sure permissions reflect the sensitivity of the material rather than convenience.

Your organisation should obtain appropriate privacy, data-protection, and contractual advice for its own circumstances. This checklist is an administrative workflow, not legal advice.

Common bottlenecks and a repeatable response

• Information arrives late: keep a missing-evidence list with an owner, request date, next action, and escalation point.
• Tutors describe changes informally: use a standard change form or controlled log so that the ILR owner receives the same minimum information every time.
• Programme details are copied from last year: require a dated check against current official documentation before a programme is opened for enrolment.
• One person is overloaded: schedule fixed weekly data-maintenance time and a separate monthly review, rather than trying to resolve every record only at submission time.
• Files become hard to trace: use a naming convention that includes academic year, reporting period, version, and export date, while avoiding unnecessary personal data in filenames.

Copyable ILR setup readiness checklist and responsibility matrix

Use the following template as the starting point for an editable internal checklist. Add the fields required by your provision and current guidance; do not assume that every row applies in every funding or delivery scenario.

SubSchool can help you turn this checklist into an editable process template alongside your teaching workflow, reducing repetitive coordination while keeping the provider and teacher responsible for the final educational and administrative decisions. Start with the checklist, adapt it to your provision, and make the review routine visible to everyone involved.

For the official starting point, consult the Department for Education guidance on setting up an ILR and collecting data with the Learner Entry Tool, then follow the linked current technical and submission guidance for your reporting year.