Explained / Other / 13 August 2026
Selling EdTech into UK schools in 2026: DfE, Schools Buying Hub, Computing Standards
UK school procurement is multi-layered: academy trusts, local authorities, federations, individual schools. The Department for Education's Schools Buying Hub is the dominant procurement framework; DfE's published standards for school IT (broadband, network, cyber security, digital accessibility) are increasingly mandatory. A practitioner walkthrough.
School procurement runs on the academic year (September starts; budget windows in March-April for September deployment). DfE's compliant-by-default frameworks compress procurement. Vendors targeting UK schools must align with DfE Computing standards and the broader Keeping Children Safe in Education (KCSIE) statutory guidance.
How UK school procurement actually works
UK school procurement is multi-layered. The buyer can be a multi-academy trust (MAT) covering 20 to 100 schools, a single academy trust, a local-authority maintained school, a federation of maintained schools, or an individual independent school. Each layer has different procurement authority, different financial scrutiny, and different cycle constraints.
For state-funded schools, the Department for Education's Schools Buying Hub is the dominant procurement framework infrastructure. The Hub exists to help schools and trusts buy efficiently against pre-procured frameworks; vendors registered on Hub-supported frameworks have a meaningful advantage in being shortlisted.
The DfE has published digital and technology standards covering broadband, network infrastructure, cyber security, digital accessibility, cloud solutions, and meeting-room technology. The standards are increasingly treated as mandatory by schools running competent procurement; vendors who do not align face a procurement-screening problem.
The academic year and budget cycle
UK schools run on the academic year (September to July) and the financial year (1 April to 31 March for academy trusts; varies for maintained schools). The two cycles do not align, which creates a planning rhythm vendors need to understand.
The practical pattern: budget for September deployment is set in the March-April budget round of the same calendar year. School leaders evaluate vendors in the autumn and spring terms; commercial decisions are typically signed in the spring (March to May) for September-onward implementation. Mid-year deployments are uncommon and require either explicit project budget or capital reallocation.
Vendors targeting UK schools should plan their commercial cycle against this rhythm: pipeline-build September to December, evaluation January to March, commercial close March to May, implementation June to August, go-live September. Vendors who chase deals on a calendar-quarter cadence misalign systematically.
Multi-academy trust dynamics
Multi-academy trusts (MATs) are the dominant scale buyer in UK state schools. Large MATs (50+ schools) operate procurement at near-corporate sophistication: dedicated procurement function, formal RFPs, vendor panels, central contracts that flow to individual schools. Mid-size MATs (10 to 50 schools) operate lighter versions of the same. Small MATs (under 10 schools) run procurement at school level with central trust signoff.
A vendor selling into a large MAT is making one decision that flows to many schools. The deal cycle is longer (6 to 12 months) and the procurement bar is higher, but the resulting deployment scale justifies the investment. Vendors who treat each MAT school as an independent sale typically underperform against vendors who go directly to the trust.
DfE digital and technology standards
The DfE's published standards cover specific categories: broadband connectivity (minimum bandwidth tiers per pupil), network infrastructure, cyber security (multi-factor authentication, backup, incident response, supplier assurance), digital accessibility (WCAG 2.2 AA conformance), cloud solutions (data residency, security, sustainability), meeting-room technology, and others.
Vendors providing products in these categories should map their offering against the relevant standard and present evidence of alignment in the procurement pack. Schools running procurement against the standards expect this evidence; vendors who present without it face screening or remediation requests that slow the cycle.
Keeping Children Safe in Education (KCSIE)
KCSIE is statutory safeguarding guidance that all schools and colleges must follow. Vendors whose products process pupil data, monitor pupil activity, host pupil-generated content, or provide channels through which pupils can communicate with adults trigger KCSIE considerations.
The safeguarding lead at each school is the relevant decision authority on KCSIE-touching procurement. Vendors should be prepared to evidence: how the product supports safeguarding (filtering, monitoring, reporting), how pupil data is protected, how incidents are escalated, how the vendor cooperates with police investigations and school safeguarding processes. Vendors who treat KCSIE as a tick-box exercise typically lose the deal at safeguarding-lead review.
Source: Department for Education Schools Buying Hub. DfE digital and technology standards (broadband, cyber, accessibility). KCSIE statutory guidance. Editorial synthesis.