Guidance and public resources updated 10 October 2026.
A school IT audit establishes a reliable view of your technology, evidence, risks and future investment needs.
A complete audit should examine more than hardware. It should consider infrastructure, cyber security, filtering and monitoring, digital leadership, asset lifecycles, service delivery, resilience and the school's ability to support teaching and operations.
The health check is an indicative questionnaire. It does not replace a complete audit.
A school IT audit is a structured review of the technology, systems, evidence and governance supporting a school or Multi-Academy Trust.
The audit records the current position, identifies risks and gaps, tests whether important controls are supported by evidence, and provides leadership with prioritised recommendations.
The output should not be only a technical inventory or a list of problems. It should explain what matters, why it matters, what should happen next and how improvement can be planned and funded.
The term "IT audit" is frequently used to describe entirely different processes. Understanding these differences is essential before commissioning or conducting a review.
Reviews networks, wireless connectivity, switching, cabling, servers, storage, internet connectivity and technical resilience.
Reviews accounts, privileges, devices, vulnerabilities, backups, recovery, incident response and security governance.
Reviews the school's current position and evidence against the published DfE Digital and Technology Standards.
Brings safeguarding, leadership and technical evidence together to review whether filtering and monitoring arrangements remain appropriate.
Reviews support responsibilities, service evidence, strategic advice, documentation, escalation and value delivered by an internal team or external provider.
Combines the technical, governance, asset, financial and service perspectives into one current-state baseline and improvement roadmap.
Review:
Review:
Review:
Review:
Review:
Review:
Review:
Review:
Review:
Review:
Review:
Review:
A school IT audit should not be completed by the technology provider in isolation. Technical specialists can supply evidence and advice, but leadership, safeguarding and financial decisions require the appropriate organisational owners.
| Participant | Contribution |
|---|---|
| Senior leadership | Objectives, ownership, risk and priorities |
| School business or finance lead | Contracts, costs, procurement and budgeting |
| IT lead or provider | Technical evidence, configuration and dependencies |
| DSL or safeguarding lead | Filtering, monitoring and online-safety context |
| Data-protection responsibility | Data-processing and information-governance context |
| Curriculum or teaching representation | User need, teaching impact and adoption |
| Governors or trustees | Oversight, challenge and accepted-risk assurance |
Exact responsibilities will vary according to local governance, employment arrangements and support contracts.
A verbal assurance or an undated screenshot may help identify where to investigate, but stronger assurance normally comes from current, attributable and reproducible evidence.
A valuable audit should produce actionable outputs, not just a static document.
A concise explanation of the current position, material risks and decisions required.
Each finding should identify the affected area, supporting evidence, impact and confidence in the conclusion.
Recommendations should distinguish immediate risk treatment, planned improvement, routine maintenance and accepted exceptions.
Leadership should be able to see which replacement needs are likely to affect future budgets and which assumptions support the forecast.
Actions should be phased according to risk, dependency, affordability and organisational capacity.
Every approved action should have accountable ownership, a target review point and expected completion evidence.
Governors or trustees should receive a proportionate view of material risk, agreed investment and progress.
Bring current assessments, asset information and evidence into one consistent baseline.
Prioritise findings, identify dependencies and turn recommendations into a phased, costed roadmap.
Structure actions, record progress and maintain a clear view of remaining risk and completed work.
Red, amber and green ratings can help leadership see patterns, but the colour alone is not the audit.
Each rating should be supported by:
A green result should not remain green indefinitely without review, and a red result does not automatically mean immediate replacement.
There is no single review frequency that is appropriate for every part of a school's technology environment.
The full baseline should be reviewed at an agreed interval, while individual evidence should also be reconsidered when:
The audit should therefore be treated as a maintained management process rather than a document produced and then filed.
Material for Education. Download, share and discuss. No form or account needed.
Questions for school and MAT buyers, plus a reusable school evidence, action and investment worksheet.
For Schools, Multi-Academy Trusts
A fictional school review with evidence gaps, school and trust responsibilities, a three-year hardware plan and explicit cost exclusions.
For Schools, Multi-Academy Trusts
Leadership briefing
A teacher needs a new app. The office needs a replacement laptop. A parent asks about online safety. These requests may all involve IT, but they need different people to help.
Article
The Department for Education's digital standards cover many parts of school IT. You do not need to understand every technical detail before using them. Start with a school need and involve the colleagues who can check it.
Practical guide
A three-year IT budget should help colleagues understand what the school needs, when it needs it and what the likely costs include. It can do that without a complicated scoring model or a list of unexplained specifications.
asitplan brings structured assessments, evidence, asset information and improvement planning into one platform.
Use the platform to establish the current position, identify gaps, organise recommendations and build a costed roadmap for leadership.
Example product view · demonstration data
Structured questions help teams record their current position and identify what needs review. Use that evidence to support the next decision.
Question completion is not a compliance score. Missing evidence must remain visible and findings require review.
Use the published requirements when defining scope and checking evidence. Product examples support planning; they are not certification.
DfE digital and technology standards (opens in a new tab)Tell us about your organisation, priorities and any existing IT partner. We review your enquiry and pass relevant details to our distributor, who can coordinate a suitable partner or handle larger customers directly.
We will discuss scope and onboarding before access is arranged. This request does not book a demo or activate an account.