How to start a useful school IT check
An IT audit is a structured check of what the school has and how it supports its work. Staff can contribute useful observations without testing technical settings themselves. Start with a clear question and involve IT where needed.
For Schools, Multi-Academy Trusts · asitplan
Decide what you want to learn
Choose the part of the school or the problem being checked. That might be a laptop trolley, an office process or the start-of-term setup.
Write down the question in everyday terms: “Can this room show the lesson material?” or “Do we know where these laptops are?”
Agree who will help and what is outside the check. A visit to one room will not answer every question about the school.
Use the records already available
Ask for the current equipment list, support details and relevant agreements. Check their dates and who updates them.
Compare a small set of equipment with the list. Note the school labels, locations and missing accessories. Mark uncertain details as needing a check.
Ask staff how they use the equipment. A device on a shelf may be a spare, awaiting repair or no longer needed.
Try suitable everyday tasks
With the authorised colleagues, check an ordinary lesson or office job using safe material. Record what happens and when.
Leave technical, electrical and security checks to the people responsible. Staff should not visit harmful sites, change settings or interrupt working services to see what happens.
Ask IT to explain the limits of any technical report in plain language.
Talk to the people affected
A teacher can describe an unreliable screen. An office colleague can explain a difficult sign-in or missing tool. IT can investigate the cause and advise on options.
Keep personal information and sensitive system details in the school's approved records. Use fictional or suitably protected examples in wider reports.
Describe staff difficulties respectfully. The purpose is to understand the work, rather than blame someone for a process they did not design.
Turn findings into a short work list
Separate confirmed problems from questions still needing an answer. For each action, name a responsible contact and a sensible next date.
If spending is proposed, get options and complete costs first. Make clear what was checked and what remains outside the work.
After a fix, repeat the relevant task. A useful check ends with understood findings and follow-up, rather than a large document that leaves staff unsure what to do.
Sources and further reading
- DfE digital leadership and governance core standard
Leadership, registers, continuity and a needs-led strategy
Source checked 2026-10-10
- NCSC 10 Steps: asset management
What should you do? — systems, accounts, online identity and suppliers
Source checked 2026-10-07
- DfE IT support standards
Support channels, recorded requests, service expectations, maintenance and improvement planning
Source checked 2026-10-07