Ofsted Applications: Three Mismatches to Catch Before Submission
Filed under: Practice Notes
An application can contain a correct answer in one box and contradict it in the next. For a childcare provider in England, a useful final review follows those connections: the proposed provision must fit the register, supporting records must match the applicant, and linked forms must identify the right registration.
Ofsted’s June 2026 account of returned applications identifies these problems. It also makes an important distinction: an application accepted for further processing is not a completed registration. Keep that distinction in the team’s progress notes.
1. The register and the declaration tell different stories
Ofsted describes applications in which the selected registers do not match the ages of children to be cared for. A declaration that conflicts with the application can also prevent acceptance. Review those answers together, rather than asking different colleagues to approve isolated sections.
Here is a fictional review of an application draft, not a recommendation of which register a provider should select:
| Part of the record | What the reviewer finds | What happens next |
|---|---|---|
| Provision description | The draft describes the intended ages and care arrangement. | Compare these details with the applicable official registration guidance. |
| Register selection | The selection was copied from an earlier, different proposal. | Stop treating that answer as confirmed; resolve it against the present provision. |
| Final declaration | It still reflects the earlier selection. | Review it again after the register question is resolved. |
The error is not an empty field. Every field could be filled, yet the form would describe two different proposals. The learning task is to find the connection before submission.
2. Identity details drift between records
The June post flags incorrect personal details and mismatches with DBS information, including previous names and address history. A reviewer should identify the precise field that differs, rather than writing “DBS checked” against the entire application.
Use invented details when practising with colleagues. For a real application, the authorised reviewer works in the approved system with the relevant records. The review note can say “previous-name entry differs from supporting record; applicant to resolve” without copying the sensitive information into a training sheet.
3. A familiar URN belongs to the wrong thing
A unique reference number is not useful merely because it is valid somewhere. Ofsted’s post distinguishes the registered person’s URN from a setting URN in different joining arrangements and explains linked EYS/EY2 submissions. Locate the instructions for the actual form before reusing a number.
For the rehearsal, replace all real numbers with labels: “registered person”, “setting” and “not yet identified”. Ask the colleague reviewing the draft to show which label the form requires and where the number will come from. Recognising that the source is unresolved is a better result than confidently copying the number from the nearest letter.
Finish with a connected review
Read the provision description, register selection and declaration as one story. Then check the identity fields and the specific reference requested by each linked form. A second reader should be able to explain why each answer belongs to this application.
Start with Ofsted’s overview of application routes if the route itself is unclear. This article selects three review problems; it is not the complete registration checklist or an eligibility decision.
To turn the exercise into team learning, use our small professional-learning cycle: choose one recurring mismatch, try a connected review, then examine whether the next draft resolves it. Keep the finding specific rather than declaring the whole process error-proof.