The national data spine: What it means for school ICT

national data spine for schools

Schools rely on accurate pupil information every day, from monitoring attendance and progress to coordinating safeguarding and SEND support. The challenge is that this information can often sit across several systems. The Management Information System (MIS) holds one part, while specialist platforms and records hold the rest. Bringing the full picture together can take time, particularly when a pupil moves school or receives support from several services.

Set out in the government’s Every Child Achieving and Thriving White Paper, published in February 2026, the proposed national data spine is intended to support secure information sharing across education systems in England. This could make it easier for records to follow pupils and for staff to see what support is already in place. It could also reduce some of the repeated administration for schools and families. The proposal is still at an early stage, with further detail expected on MIS integration, connectivity and data protection.

Because the national data spine will rely on MIS platforms sharing information securely and consistently, it will influence what schools need from future MIS contracts. This makes the DfE’s planned MIS framework particularly relevant. The framework is currently expected to launch in September 2027, so schools with an MIS renewal due before then still need to decide how to proceed.

Everything ICT can help schools review their current MIS contract, key dates and procurement options in line with DfE guidance. For academy trusts, this means limiting pre-launch contract extensions to 12 months and including DfE’s MIS Core Principles in any necessary new procurement. Whether an extension, a compliant mini-competition or a new agreement is appropriate, Everything ICT can help schools build in suitable break and review points, meeting their current needs while retaining flexibility as the new framework becomes available.

What the national data spine is

The national data spine would allow existing education systems to share agreed pupil information securely, including attendance, progress and assessment records.

It is also expected to support the Education Record app and future digital support plans for pupils with SEND. Further detail is expected on what information will be shared and who will be able to access it. The wider reform programme points to implementation from 2028–29, although the timetable for the spine has yet to be confirmed.

What it means for school ICT

The key issue is whether the school’s MIS can share data in the format the spine will require. Providers will be better placed to confirm compatibility once the technical specifications are published. In the meantime, they can explain how their platforms support current DfE data standards, secure integrations and data exports. This gives schools an early indication of how much work may be needed and whether a future migration could be necessary.

An upcoming MIS renewal is a useful opportunity to take those questions further. Schools may want to ask how the provider is preparing for the data spine, how easily information can be retrieved and moved, and what support would be available when changing supplier. Everything ICT can help turn the DfE’s emerging requirements into clear supplier questions and build the answers into a compliant, well-documented procurement process. This gives school leaders a stronger basis for comparing providers.

Access to the data spine will also depend on a stable and secure connection. The current DfE broadband standard recommends full fibre, enough capacity for the school’s needs and a backup connection. Schools with unreliable broadband may want to include improvements in their wider ICT planning.

Good data management will matter just as much as the technology. Schools need clear controls over who can view or change information, with access removed promptly when staff leave or change roles. Accurate records are also important, as connected systems can pass outdated or incorrect information further if it is not picked up early.

Clear ownership will help bring this work together. A named member of SLT can coordinate the relevant data protection, safeguarding, SEND, administration and ICT leads, while keeping governors informed about progress, costs and emerging risks.

The data protection implications

The national data spine could bring together some of the most sensitive information a school holds, including details about health, SEND and safeguarding. Schools will need a clear understanding of what is being shared, why it is needed, who can access it and who is responsible at each stage.

Schools should involve their Data Protection Officer (DPO) as guidance emerges. The DPO can help confirm the appropriate lawful basis, identify any additional condition required for processing special category data such as health information, and make sure the right checks are built in from the start.

A Data Protection Impact Assessment (DPIA) may also be required before a school connects to the spine, particularly where sharing creates a high risk to pupils’ rights and freedoms. The ICO’s guidance on children’s information explains what to consider.

A standard DPIA template could cover the key questions common to all schools. Each school would then complete it with details of its own MIS, the information being shared, who can access it and the safeguards in place. This would include data minimisation, which means sharing only the information needed for a clear purpose and limiting access to the appropriate people.

What schools can do now

Schools can strengthen their position now through a small number of practical checks.

  1. Talk to your MIS provider. Ask how the platform supports current DfE data standards, secure integration and data portability, as well as how the provider plans to prepare for the national data spine.
  2. Check your broadband and backup arrangements. Compare the current service with the DfE broadband standard and review any relevant contract dates. This can help identify improvements before connectivity becomes a more pressing issue.
  3. Review how pupil data is managed. Check who has access, how permissions are removed when staff leave or change roles, what audit records are kept and who is responsible for correcting inaccurate information.
  4. Agree who will lead. Give a named member of SLT responsibility for coordinating the work and keeping governors informed as the requirements develop.
  5. Keep the position under review. Add the data spine to the school’s digital strategy or risk register, monitor updates from the DfE and agree when the school will revisit its plans.

Time to prepare

The national data spine could make it easier for schools to maintain complete pupil records, coordinate support and reduce repeated administration. Delivering that across different systems and settings will take time. Schools can make useful progress by reviewing their current systems, contracts and responsibilities.

If you are reviewing an MIS, broadband or wider ICT contract, Everything ICT can help you understand your options and plan a compliant procurement that meets your current needs while leaving room to respond as the DfE’s plans develop. Speak to the Everything ICT team to talk through your next steps.