KCSiE (Keeping Children Safe in Education)
Safeguarding obligations built into the software architecture — filtering, monitoring, and reporting designed to help DSLs meet their statutory duties.

LMS platforms, student portals, and virtual learning for UK schools, colleges, and training providers. KCSiE and UK GDPR child data provisions from the first commit — not retrofitted before an Ofsted visit.
Engagement
Compliance posture
What you get
You bring the teaching expertise. We bring the engineering — KCSiE-informed, accessibility-tested, and built for the inspection.
Course delivery, progress tracking, and resource libraries — with role-based access so staff, students, and parents see only what they should.
Live and recorded sessions with screen sharing, whiteboards, and breakout rooms — accessible on school devices and personal tablets alike.
Admissions, enrolment, attendance, and academic records in one place — with audit trails that satisfy both DfE returns and Ofsted scrutiny.
Secure portals where parents view progress, communicate with staff, and manage permissions — with age-appropriate design for younger learners.
How we work
Four phases, same rhythm every engagement. DPIA scoping and safeguarding review handled in discovery so there are no mid-build surprises.
Map the learning workflow, data flows, and safeguarding touchpoints. DPIA scoped where child data is involved, safeguarding review included.
Architecture diagrams, role permission matrices, and clickable prototypes — reviewed with teaching staff. Accessibility testing starts here.
Agile delivery with education-context testing. Encryption at rest, TLS in transit, audit logs end to end. WCAG 2.1 AA accessibility throughout — working towards 2.2.
Go-live with staff training, handover docs, and a 30-day window where fixes are free while you settle in.
Compliance map
Six frameworks we design against on every education engagement — with specifics, not hand-waving.
Safeguarding obligations built into the software architecture — filtering, monitoring, and reporting designed to help DSLs meet their statutory duties.
Lawful basis for processing children's data, age-appropriate privacy notices, parental consent flows, and data minimisation as architectural decisions — not afterthoughts.
Built to the Department for Education cyber security standards and JISC guidance for further education — access controls, incident response, and supplier assurance baked in.
All student-facing and parent-facing interfaces built to WCAG 2.1 AA today, with the WCAG 2.2 success criteria in flight (committed in our public Accessibility Statement). Keyboard navigable, screen-reader compatible, and tested with assistive technology.
Audit trails, attendance data, and progress reporting structured so your digital systems support rather than hinder inspection — surfaced in views designed for evidence retrieval.
ICO Children's Code compliance for platforms used by under-18s — default privacy settings, limited data collection, and no nudge techniques that exploit young users.
Proof of work
Our education portfolio is still being built — here's what's next in the pipeline.
Client project — NDA-covered
We're in early conversations with a UK multi-academy trust on a unified learning and safeguarding platform. Case study published once the project goes live.
Before you ask
We build safeguarding into the architecture — not as a bolt-on. Monitoring, filtering, and reporting features are designed to support your Designated Safeguarding Lead's statutory duties under KCSiE. We don't replace your DSL or your safeguarding policy — we build software that makes it easier to follow them. If your school doesn't have a DSL or clear safeguarding procedures, we'll flag that before we start building.
UK region (AWS eu-west-2 London by default). Children's data gets additional protections: stricter access controls, shorter retention periods, age-appropriate privacy notices, and parental consent flows where required. No third-country transfers without a contract, DPIA, and written sign-off. We design for UK GDPR child data provisions from discovery, not as a compliance checkbox at the end.
Integration depends on your SIS vendor's API surface. SIMS, Arbor, Bromcom, and most modern school management systems have workable APIs for structured data exchange. Legacy file-drop or CSV-based integrations are slower but doable. We'll assess feasibility in discovery before quoting — if integration is going to be painful, we'll tell you upfront.
Multi-academy trusts need a single platform with per-school data boundaries. We build multi-tenant architectures where each school manages its own data, staff, and students — while the trust gets a consolidated view for reporting and governance. Role-based access ensures a teacher at School A cannot see School B's records. DfE census returns and Ofsted data can be generated at school or trust level.
Every significant action in the system is logged with timestamps, user identity, and context. Attendance records, safeguarding referrals, behaviour incidents, and progress data all have complete audit trails. When Ofsted asks "show me the evidence", your digital systems should make that easy — not harder. We design reporting views specifically for inspection retrieval.
Tell us what you're working on — we'll reply within 24 hours on working days with an honest read on feasibility, compliance scope, and a realistic timeline.