Is your school support system just fixing problems?

The two documents behind this article

The Department for Education (DfE) published its IT support standard on GOV.UK on 17 November 2025, as one part of Meeting digital and technology standards in schools and colleges. It covers support that is run in house, bought from an outside company, provided through a trust or local authority, or a mix of these. Its five parts ask schools to plan, commission and review that support, and to make sure staff get clear guidance and training.

The second source is the Education Endowment Foundation's (EEF) A School's Guide to Implementation, third edition, published in April 2024. It rests on a review of 293 studies from 1996 to 2023, with more of them about teaching and learning than about health.

Neither document is about school software as such, and neither tests whether following it brings tickets down. The standard is guidance, not research. The EEF guide was written about changes to teaching and school practice, so applying it to a school's systems is our reading, not its finding.

What a school support system should record

The IT support standard asks schools to make sure every request is recorded and tracked until it is resolved. For each one it lists five things to note: a description of the issue, the date and time, who asked (and who approved it, if needed), the priority, and the steps taken to resolve it. It suggests considering a helpdesk or case management system for the job.

It also says what the log is for. A school's digital lead can use the records to see how well support is meeting demand, to spot recurring problems and outdated technology, and to plan improvements or training. The standard warns against requests sent by instant message, because they go unrecorded and make trends harder to see.

That is the first difference between a support desk that answers requests and one that learns from them.

A fix closes one ticket. A record of the fixes shows which question keeps coming back.

Repeat problems often point to training

The standard says that when recurring issues come from user error or a lack of knowledge, the digital lead should provide extra training. It also says that if one type of technology keeps generating requests, replacing it may be more efficient. Elsewhere it asks IT support to help identify training needs from the trends in its requests.

So one repeat request can mean two different things. Staff may not have been shown how to do something, or the tool may not fit the job. A log that only says "closed" cannot tell the two apart.

Training that carries on after go-live

The standard asks for induction training when staff join or change roles, followed by regular refreshers on the essential systems, and for materials to be updated when new tools arrive. It also asks for plain-English guides on logging in, resetting passwords and raising a request, and says good guidance reduces reliance on IT support for simple queries.

The EEF guide, drawing on research into change in schools, says initial training is unlikely to be enough on its own to change practice. Follow-on support, given while people are using the new approach, is often what turns understanding into habit, and professional development should continue throughout implementation. Its checklist for the delivery phase asks whether initial training is being reinforced by feedback, prompts and reminders.

It also says complex, whole-school changes can take at least two years, and advises spending time exploring and preparing rather than only launching.

The guide warns against relying on one or two people. The loss of key staff can change how an approach is seen in a school, so a broad range of colleagues should be involved. In a support system, that means the person everyone asks should not be the only one who knows the answer.

How a school support system should talk to staff and leaders

The EEF guide says leaders should communicate the direction of travel and explain decisions. It also warns that colleagues can appear to be on the same page when they are not, and that monitoring works best when staff see it as a way to improve, not as a punishment.

The IT support standard turns part of this into routine. The digital lead and IT support are asked to agree and record how quickly requests should be answered and resolved, how they are prioritised and how serious incidents are escalated, and then to meet regularly to check those expectations are realistic. Staff should be able to see the status of their requests.

The standard also asks for a written summary of the annual review to go to the senior leadership team, the business manager and governors or the trust board, and says governors or trustees should approve major decisions such as contract changes.

What to measure besides speed

Response and resolution times are on the DfE's list, so speed still counts. Beside it, the standard asks for a formal review of IT support, led by the digital lead, at least once a year, using the request records and user feedback. The review looks for times of high demand, technologies that cause many requests, and training needs for IT support staff and for everyone else. It also asks whether support has the skills and capacity it needs, and notes that value for money does not necessarily mean the lowest cost.

The EEF guide adds a condition. Monitoring data improves things only if it is shared, understood and used, so staff and leaders need time to reflect on it. Neither document gives a target for ticket numbers or a list of scores to chase. Both point to evidence from the log and from the people who use the systems.

What a school can take from this

• Log every request in one place. Use the DfE's five fields and ask staff to stop sending requests through chat messages that nobody records.
• Sort last term's requests by repeats. For each topic that keeps returning, decide whether it needs training, a short guide or a different tool.
• Plan training in two parts. Book the induction and the follow-up sessions together, so support after go-live is not an afterthought.
• Write down the response and escalation rules. Share them with staff, and let people check where their request stands.
• Review in writing at least once a year. Look at the repeats each term as well, and send governors the written summary.
• Ask the people using the systems. A short anonymous survey shows where staff feel stuck. For a way to ask where teachers' time goes, see what the OECD's teacher survey says about workload.