03 Apr 2026
This week, we’ve been focused on developing our understanding of how to access school data.
Our tools need school data to function, so establishing where that data is stored and how we can access it is mission-critical.
As we are creating tools that will automate parts of the SENCO workload, they need to be able to access the same scope of data that the SENCO can. This data is typically stored in multiple formats and systems, many of which are currently inaccessible via an API. This presents a challenge when you are building tools that depend on APIs to perform as efficiently as possible.
To enable us to continue making progress while API accessibility is improved, we will utilise a hybrid approach that combines data obtained via APIs with manually uploaded data.
In the longer term, we are encouraged by the UK government's plans to create a national “data spine”. This is the most ambitious initiative since the 2012 Open Data Strategy, and it differs most significantly in scope. Where the Open Data Strategy focused on making school data publicly available (resulting in the now-accessible National Pupil Database alongside many other datasets), the data spine initiative aims to interconnect schools and their systems in near real-time.
We had the pleasure of hearing this announced in person by the Education Secretary at BETT 2026, and it is a significant part of the government's white paper, released in late February. While its realisation may be many years away, it is helpful for EdTech startups such as ours, as it enables us to align our ambitious product development strategy with the government's goal for a data-driven school system with open data standards to connect and share information.
We wish you a fantastic Easter weekend.
