ILR Data Collection for Small Learning Providers: A Practical Setup Checklist

For a small learning provider, ILR work can feel less like a single administrative task and more like a chain of decisions: who collects learner information, where evidence is recorded, who checks changes, and what happens when something does not match the expected record. The Department for Education (DfE) guidance on setting up ILR collection with the Learner Entry Tool provides the official starting point. This article turns that starting point into an operational workflow that a small team can use consistently.

This checklist is designed for UK independent learning providers, small online schools and course administrators who are responsible for learner-record data. It is not a replacement for current DfE guidance, funding rules or provider-specific instructions. Treat the current official guidance as the source of truth, and use the process below to make your local responsibilities clearer.

1. Start with the official guidance and name one accountable data owner

Before creating forms, spreadsheets or staff instructions, open the current DfE guidance on setting up ILR data collection with the Learner Entry Tool. Read it alongside the guidance and publication for the earnings adjustment statement (EAS), where relevant to your organisation.

Small providers do not need a large data department, but they do need a clear decision-maker. Assign an ILR data owner: the person accountable for maintaining the local process, monitoring updates to guidance, resolving routine questions and escalating matters that need specialist or senior review.

That person should not have to do every task. In a small team, one administrator may collect enrolment details, a tutor may confirm learning activity, and a director may approve a submission-related decision. The important point is that everyone knows who owns the final internal check.

Minimum ownership decisions to document

• Who monitors official DfE guidance and communicates relevant changes internally.
• Who configures or administers access to the Learner Entry Tool.
• Who collects information from learners and who checks it for completeness.
• Who can amend a learner record after enrolment.
• Who performs the pre-submission or pre-reporting quality review.
• Who decides whether an issue may require EAS consideration or external advice.

Put these decisions in a one-page operating note. A short, maintained document is generally more useful than a long procedure that staff cannot find or follow.

2. Map the learner-data journey before collecting the first record

Data quality problems often begin at handoff points. A learner may give information to a sales adviser, start learning with a tutor, change circumstances through support staff, and appear in a record maintained by an administrator. Map the route from first enquiry to ongoing updates.

Use a simple workflow with five stages: enquiry, enrolment, learning delivery, change reporting and record review. For each stage, identify the staff role, the information that may be created or updated, the place where it is recorded, and the person who checks it.

The table is a process aid, not a statement of mandatory DfE fields or evidence rules. Your internal form and workflow should be checked against the current official guidance before use.

3. Set up a reliable Learner Entry Tool workflow

The Learner Entry Tool should sit within a controlled process, rather than becoming the only place where staff remember what happened. Create a short setup plan that answers practical questions before staff begin entering learner data.

1. Confirm access and continuity. Identify the people who need access, who can provide cover during absence, and how access requests or removals are handled.
2. Use a standard intake route. Decide how learner information reaches the person entering or reviewing records. Avoid relying on scattered email threads or verbal messages.
3. Define a source-of-truth record. State where supporting enrolment and learning information is stored internally, and how it links to the learner record.
4. Create a change log. Record the date a change was reported, the person reporting it, the action taken, the reviewer and any outstanding question.
5. Separate entry from review where feasible. Even in a two-person team, a second pair of eyes for higher-risk changes can reduce preventable errors.
6. Test the process with sample scenarios. Walk through a routine enrolment, a correction and a learner change before processing a large group.

Keep staff guidance practical. Instead of saying “maintain accurate data”, tell colleagues what to do: use the intake checklist, upload or record the approved evidence in the agreed location, notify the data owner of a change, and do not overwrite a record if the underlying question is unresolved.

4. Build a learner-record checklist for enrolment and ongoing updates

A checklist is most effective when it separates collection from verification. Staff should be able to show that information was received, then show that an appropriate person checked it against the provider’s process and the current official guidance.

Learner-record checklist

• Record the learner’s identity and contact information through the provider’s approved enrolment process.
• Confirm that programme, start and learning arrangements are recorded consistently across the learner file and operational systems.
• Capture information needed for ILR collection using the current DfE guidance and local instructions.
• Record the source and date of important learner information or updates.
• Flag incomplete, conflicting or late information rather than guessing or silently filling gaps.
• Document relevant changes during learning and route them to the data owner for review.
• Keep a clear audit trail of who made a material update and why.

For online providers, include a defined route for tutors to report changes. A tutor should not need to interpret data requirements alone; they should only need to recognise a reportable event, record the facts, and send it through the agreed channel.

5. Add a review gate before data is submitted or reported

Do not make quality assurance a last-minute search for errors. Set a recurring review rhythm that fits your learner volumes: for example, a weekly check of new records and changes, followed by a more formal review before any relevant submission or reporting point.

A useful review asks four questions:

1. Complete: Are required items present according to the current guidance and provider process?
2. Consistent: Do dates, programme details and learner updates agree across the relevant records?
3. Supported: Is there an identifiable source or record supporting important entries and changes?
4. Escalated: Have exceptions been logged, assigned and resolved or deliberately held for advice?

Maintain an exceptions register. It can be a controlled spreadsheet or workflow board containing the learner reference, issue type, date raised, owner, next action and decision. This prevents unclear cases from disappearing into individual inboxes.

6. Know when to escalate a possible earnings-adjustment issue

The DfE provides separate EAS guidance and a publication on how to submit an earnings adjustment statement for 2026 to 2027. Small providers should not assume that an EAS is a routine correction route for every data issue. Instead, create an escalation step for cases where staff believe an earnings-related adjustment may be relevant.

Your internal escalation should capture the facts, the period involved, the records already checked, the reason the matter cannot be resolved through the normal learner-record process, and the person responsible for checking the current EAS guidance. The data owner should then decide whether to seek senior, funding, finance or specialist advice before any action is taken.

Practical rule: do not ask front-line staff to decide whether an EAS is required. Ask them to report the issue promptly and preserve the supporting information.

7. Printable ILR readiness checklist and responsibility matrix

Use the following as a one-page readiness check. Print it, assign names against each line, and revisit it when official guidance or staffing changes.

SubSchool can help small teams turn repeatable administrative steps into structured checklists, prompts and review workflows while keeping teachers and provider leaders in control of the educational and operational decisions. Explore SubSchool if you want to reduce repetitive coordination around enrolment, learner updates and internal quality checks.

Reminder: ILR, funding and EAS processes can change. Check the live DfE guidance before applying this checklist to a submission, payment-related decision or provider policy.