
After a school IT check, choose the next practical jobs
An IT check can produce a long list of findings. Turn it into a useful plan by separating urgent problems, unanswered questions and improvements that can wait, then giving each job a responsible contact.
For Schools, Multi-Academy Trusts · asitplan
Read the findings in school terms
Ask what each issue means for lessons, office work or protecting information. If the description is technical, ask IT to explain the effect.
Note when and where the check happened. A finding from one room may need further checking before it is treated as a whole-school problem.
Separate what was observed from a recommendation or an unanswered question.
Choose a sensible first set of jobs
Discuss priorities with affected staff and the relevant school contacts. A safeguarding or security concern should follow the school's established reporting and response process.
Other work may include repairs, missing equipment records or clearer instructions. Avoid presenting every item as equally urgent.
Check whether a small correction can solve the problem before proposing a larger purchase.
Get the facts needed for spending
Ask IT for suitable options and suppliers for complete costs. Include preparation, accessories and ongoing charges.
Explain which figures are quotes and which are estimates. Find renewal or notice dates if a service change is involved.
The person approving the budget should be able to see the problem, the choice and the practical effect of waiting.
Name the next action
For each agreed job, say who will arrange it, what happens next and when it should be checked. Use the school's existing work list rather than creating a competing one.
After a repair or change, ask a user to try the task it was meant to improve. Record the result and any remaining work.
The plan can be short. Its purpose is to make the findings usable for the people who need to act, with clear decisions and visible follow-up.
Sources and further reading
- DfE digital leadership and governance core standard
Leadership, registers, continuity and a needs-led strategy
Source checked 2026-10-10
- DfE IT support standards
Support channels, recorded requests, service expectations, maintenance and improvement planning
Source checked 2026-10-07