The Strategy and the Spine: Preparing for the December 31 Inclusion Deadline

The 60-second Briefing

• The DfE published its inclusion strategy requirements on March 25 2026, with a deadline of December 31 2026 for publication on each school's own website.
• The strategy is tied to the £400 million Inclusive Mainstream Fund, which gives the average secondary school around £48,000 and the average primary around £14,000 in 2026-27. The requirement applies to mainstream state-funded schools.
• Independent schools are not formally in scope but face parallel inclusion expectations under the ISI inspection framework, where inclusion has become a sharpened focus in its 2026 cycle.
• The strategy itself has to say three things: how leaders will provide high-quality support available to all pupils, which common needs and barriers to learning the school's cohort actually has, and which activities are used to meet them.
• The question no one has asked yet is whether the MIS, the safeguarding record system, the attendance system, and the intervention tracker can actually produce the evidence the strategy will claim exists.

Ten weeks between now and the December 31 deadline. Six if you count only the term weeks remaining and discount the Christmas holiday as practical working time. For state schools preparing an inclusion strategy under the DfE requirement, and independent schools preparing their own inclusion response under the ISI framework, the clock is close enough to the end that the drafting conversation has to be the next one on the senior leadership agenda.

Most of what has been published on the inclusion strategy so far has been written from the SEND leadership perspective. Schools Week explained the mechanics in March. Browne Jacobson wrote a legal note. Tribal Group and a dozen others have published template guidance. The sector has had seven months to think about what the strategy document should say.

What nobody has yet written about is the question that follows a published strategy around for the rest of its lifespan. Can the systems the school already runs actually produce the evidence to back up what the strategy claims? That is the IT and data question. It is also the question the inspector will arrive with if they decide to look at inclusion in any detail.

Let me walk through the state-sector requirement, then the parallel independent-sector expectation, then the data gap that applies to both.

What the DfE actually requires

The DfE guidance published on March 25 requires every mainstream state-funded school to produce and publish an inclusion strategy by December 31 2026. The strategy has to be on the school's own website, has to be updated each academic year (though a multi-year strategy is also accepted), and has to cover three specific areas.

The first is how leaders will provide high-quality support available to all pupils. That is the universal-provision question. Not what the school does for pupils with identified needs, but what the baseline provision looks like for every pupil who walks through the gate on day one.

The second is which common needs and barriers to learning the school's specific cohort has. This is the data question. The strategy cannot be a template downloaded from a provider site with the school's name pasted in. It has to describe what this school's pupils actually need, which means the school has to know what they need.

The third is which activities the school uses to meet those needs. This is the intervention question. The link between identified needs and actual provision has to be visible and tracked.

The strategy is tied to the Inclusive Mainstream Fund, which gives the average secondary school around £48,000 and the average primary around £14,000 in 2026-27 as a ring-fenced funding stream for the activities the strategy describes. That is not a small amount of money. It is also not a lot of money for a well-populated inclusion strategy. For a secondary school of 900, £48,000 is around £53 per pupil per year.

Ofsted will consider the published strategy when evaluating inclusion, which from September 2026 is a specific focus under the revised inspection framework. The strategy and the practice have to match. If the strategy claims an intervention is running and the inspection finds it is not, that is an inclusion-grade problem.

The parallel conversation for independent schools

Independent schools are not formally in scope of this particular DfE requirement, and the Inclusive Mainstream Fund does not reach them. The ISI inspection framework operates under its own set of expectations, which from the 2026 inspection cycle brings a sharpened focus to inclusion comparable in substance to the Ofsted position.

The practical implication for independent schools is that the inclusion question will come up in the next ISI inspection, whether or not the school has written a formal strategy document. ISI inspectors will want to see how the school identifies needs across its intake, how it tracks interventions, and how pupils with additional needs are supported through the curriculum. The document the school produces to answer those questions matters less than the evidence trail underneath.

That is the common ground between the state-sector requirement and the independent-sector expectation. The strategy document has a hard deadline in state schools and no deadline in independent schools, but the evidence trail is the same in both.

The data gap nobody has written about

Here is where the IT and data angle becomes the sharper edge of the whole conversation. The inclusion strategy, whether written for a DfE deadline or for an ISI inspection, is only as credible as the data it rests on. If an inspector asks to see the evidence behind a claim in the strategy, three systems come into play.

The first is the MIS. SIMS, iSAMS, Arbor, Bromcom, whatever the school runs. The MIS holds the pupil-level attainment data, the attendance data, the SEND register, and the demographic data that any serious inclusion strategy will have to reference. If the MIS data is incomplete, inconsistent across year groups, or not being used for internal reporting, the strategy will struggle under scrutiny. The most common gap in schools I speak to is that the MIS holds all the information in principle but nobody has ever built the reports that make it visible in practice.

The second is the safeguarding record system. CPOMS, MyConcern, or a similar platform. These systems hold the incident records, the pastoral intervention logs, and the pattern-of-concern information that genuinely underpins inclusion work. If the strategy claims that the school identifies emerging behavioural patterns early, the inspector will want to see how the system supports that claim. A safeguarding system used only for incident recording, with no reporting layer and no pattern analysis, cannot support that claim.

The third is the intervention tracker. This is often the weakest system in the stack. Many schools track interventions in a spreadsheet maintained by the SENCO, or across several uncoordinated spreadsheets held by different departments. Some schools have moved to an intervention module in their MIS. A smaller number use a dedicated intervention platform. Whatever the tool, the question is the same: can the school produce, on demand, a list of every intervention being delivered to every pupil, cross-referenced against the identified need, with entry and exit data and progress tracking?

If the answer to any of those three questions is no, the strategy document will say more than the systems can prove. That is the gap. And an inclusion strategy whose claims the systems cannot back up is worse than no strategy at all, because the inspector reading it will know that a claim was made that cannot be evidenced.

Four practical actions for the next ten weeks

For the IT and data lead working alongside the SENCO and the SLT on the inclusion strategy, four practical actions to prioritise between now and December 31.

The first is a data audit against the strategy claims. Before the strategy document is finalised, every claim it makes should be checked against the system that will have to produce the evidence. If the strategy says the school identifies emerging patterns in behaviour data, run the report that would show that. If the strategy says interventions are tracked with entry and exit data, pull the intervention list and look at it. Any claim the system cannot evidence either needs to be rewritten or needs the system fixed before December 31.

The second is a reporting layer review. The MIS, the safeguarding system, and the intervention tracker all have reporting capabilities that most schools do not fully use. The IT department and the SENCO together, with half a day in the diary before half-term, can usually surface three or four reports that would materially support the inclusion strategy. Build those reports now, document how to run them, and make sure the data they produce actually looks the way the strategy claims it will.

The third is an integration check. If pupil data lives in the MIS, safeguarding data lives in CPOMS, intervention data lives in a separate spreadsheet or module, and attendance data lives in a fourth place, the strategy's cross-referenced claims become hard to evidence. The inspection question is often how the school joins these together. If the answer is that joining them requires a human being spending two hours with four tabs open, that is the integration gap. Not every school can fix that in ten weeks. Every school can at least know where the gap is.

The fourth is a documentation pass on the data spine itself. I wrote earlier in the year about the data spine as the connective architecture that holds a school's pupil-centred systems together. The inclusion strategy is one of the first senior-leadership documents whose credibility rests directly on how well that spine is actually working. Spending the half-term holiday producing a short internal note on which systems hold which data, how they connect, and what the known gaps are, pays off well beyond the December 31 deadline.

A broader point

The inclusion strategy requirement is, on one reading, a paperwork exercise with a December 31 cliff edge and a funding stream attached. On another reading, it is the first of a new generation of statutory documents whose credibility depends on data the school has often never been asked to produce in a cross-referenced way before.

The sector has had years of guidance on what inclusion should look like in classroom practice. The DfE's 2026 requirement is the first serious attempt to make the strategy a public document the inspector can read and compare against reality. That is a real change. Published strategies are much harder to live with than internal commitments, because they can be checked.

For state schools under the DfE requirement, the deadline is immovable. For independent schools under ISI, there is no deadline but the inspection cycle will bring the same question. In both cases, the strategy document is the easy half. The data spine underneath it is the harder half, and the one nobody has yet given schools permission to spend ten weeks on.

Spend the ten weeks on it anyway.

See you in the digital staffroom.