EdTech Software Development UK — Specialist Builds for UK EdTech Businesses

UK EdTech is a £3.5bn market — driven by remote learning adoption, increasing digital literacy expectations, and government investment in education technology. Building software for UK education settings requires specific compliance knowledge: KCSIE safeguarding obligations, the ICO Age Appropriate Design Code for products aimed at under-18s, and MIS (Management Information System) integration with the dominant school data platforms.

KCSIE Safeguarding Requirements

Keeping Children Safe in Education (KCSIE) is statutory guidance for schools and colleges in England. Technology used in schools must not create safeguarding risks. Specific software requirements: content filtering capabilities or compatibility with school content filtering, no unsupervised communication channels between adults and children, appropriate access controls to prevent unauthorised adult access to children's data, and audit logging sufficient for safeguarding investigations.

ICO Age Appropriate Design Code (Children's Code)

The ICO's Age Appropriate Design Code (AADC) — sometimes called the Children's Code — is statutory guidance for online services likely to be accessed by children under 18. Key requirements: privacy settings must be high by default, children's data must not be used for profiling for commercial purposes, geolocation must be off by default for children, and nudge techniques to weaken privacy protections are prohibited.

MIS Integration — SIMS, Arbor, Bromcom

UK schools use Management Information Systems (MIS) as their central database for pupil records, attendance, and assessment data. The dominant systems are: SIMS (by Capita — most widely deployed), Arbor (growing rapidly), and Bromcom (strong in secondary). EdTech platforms must integrate with these MIS systems to avoid manual data entry. SIMS offers an API via the SIMS Developer Programme; Arbor and Bromcom have open APIs.

DfE Digital Standards and Data Sharing Frameworks

The DfE (Department for Education) sets digital standards for education technology — including the EdTech Demonstrator Programme and the Standards for Education Technology. The DfE also maintains the GDPR guidance for schools, specifying lawful bases for processing pupil data and the data sharing requirements for statutory education returns (CBDS, Census).

SEND and Accessibility Requirements

Under the Equality Act 2010 and SEND Code of Practice, schools must support students with Special Educational Needs and Disabilities. EdTech software must be accessible: WCAG 2.1 AA compliance, screen reader compatibility (NVDA, VoiceOver), keyboard navigation, captions for video content, and adjustable text size/contrast. The PSBAR 2018 makes WCAG 2.1 AA legally mandatory for maintained school websites.

UK EdTech Compliance checklist: KCSIE, UK GDPR (ICO Children's Code / AADC), DfE standards, Ofsted, WCAG 2.1