A back-to-school IT checklist should cover six things before pupils walk through the gates: network and wi-fi capacity, device health and imaging, user accounts and leaver removal, MIS and data readiness, filtering and monitoring compliance, and backup and recovery testing. Work through them in that order where possible, because most steps benefit from the previous one being in place. Account provisioning is most reliable once your MIS has rolled over to the new academic year. Load-testing devices under realistic conditions works best once the wi-fi is stable, though battery health checks, imaging and licence audits on a device trolley can run in parallel. Most September IT failures are not new faults at all. They are August jobs that nobody owned. This guide sets out what to check, in what order, and who should sign each item off.

Who This Is For

This is written for school business managers, business directors and MAT operations leads who carry the IT budget without holding an IT job title. You may run a single primary with 240 pupils and a part-time technician, or three secondaries with a shared central team. Either way, you sign off the invoices, answer the governors’ questions and get the phone call when the interactive panels will not connect on the first INSET day. You are not short of technical opinions around you. You are short of a single, ordered view of what has to be finished before term starts, and evidence that it was.

Why September Always Catches Schools Out

The problem is not incompetence, it is compression. Six weeks of maintenance work collides with cleaning, building projects, results days and a skeleton staff rota. Business managers tell us the same three things every year. Nobody documented what the last technician did. The renewal quote arrived in August, after the budget was set in March. And nobody knows what is broken until 400 pupils log on at once on day one. Meanwhile the safeguarding lead needs assurance that filtering and monitoring meet the requirements set out in Keeping Children Safe in Education, and that assurance has to be written down, not assumed.

Building a Back to School IT Checklist That Actually Gets Finished

A useful checklist assigns an owner and a date to every line, not just a task. That is the difference between a document that gets completed and one that gets rediscovered in October. We build school IT readiness plans around three columns: what must be true before INSET Day, what must be true before pupils return, and what can safely wait until half term. Anything that cannot be assigned an owner gets escalated to you immediately, in plain English, while there is still time to act.

This matters because education IT has constraints that generic business IT does not. Term dates are immovable. Safeguarding duties are statutory. Budgets are annual and inflexible. A back-to-school IT checklist that ignores those realities will simply generate a list of quotes you cannot fund. Our education IT support for schools and trusts is designed around the operational rhythm of the academic year, so the work that needs to happen in August is planned and resourced before the summer holidays start, not discovered when the invoices arrive.

Want this in a format you can hand to your technician and your governors? Download the printable back to school IT checklist and work through it section by section. Download the checklist →

New Term IT Prep for Devices, Accounts and Classroom Kit

Devices and accounts cause more first-week disruption than servers do. Start with an audit of every pupil and staff device, including the trolley of laptops nobody has opened since May, and check battery health, operating system updates and licence status. Reimage anything that has drifted from your standard build. Then reconcile your leavers list against every system, not just the MIS, because dormant accounts in email, cloud storage and third-party learning platforms are a common route into school data.

Classroom kit deserves a physical walkthrough. Test every projector, panel, visualiser and speaker in situ, with a real login, at the time of day the room is used. Faults found in August cost a call-out. Faults found in September cost a lesson.

Step by Step: Your September School IT Readiness Run-Through

Confirm the MIS academic year rollover. Verify it is complete and check that class lists, timetables and group memberships have flowed correctly into your email, cloud and learning platforms.

Process joiners, leavers and role changes. Do this across every system in one sweep. Disable rather than delete leaver accounts, keep an evidence log, and remove access to any third-party platform the MIS does not control.

Run a full device audit and reimage. Charge and update every trolley, check licence renewals for antivirus, MDM and productivity suites, and set aside spares for the first week.

Load-test the wi-fi. Focus on halls, sports blocks and mobile classrooms where coverage is weakest. Simulate a full class logging in simultaneously rather than testing with one laptop.

Test a real restore from backup. Recover a live file and a full system image, record how long each took, and share the result with your governors. A green backup report is not the same as a tested restore.

Review filtering and monitoring. Do this with your DSL, confirm the categories blocked are current, and document the check with a date and a name against it. The DfE Digital and Technology Standards set the benchmark for what compliant filtering and monitoring looks like.

What to Watch Out For

• Assuming the MIS rollover finished cleanly. Spot-check three classes manually before you trust the sync.
• Treating a green backup dashboard as proof of recovery. Only a tested restore proves anything to an auditor or an insurer.
• Leaving supply staff, governors and volunteers out of your account review. They are frequently the oldest live logins in the system.
• Booking network upgrades for the last week of August. Hardware lead times slip and installers get overbooked across the sector at once.
• Signing a renewal quote without checking the licence count against your actual pupil and staff numbers on census day.

Quick Checklist

• Named owner and completion date against every readiness task
• MIS rollover verified and cross-checked in three systems
• All leaver accounts disabled, logged and evidenced
• Every device charged, updated, imaged and licence-checked
• Wi-fi load-tested in weak-coverage areas with a full class
• One live restore completed and timed within the last 30 days
• Filtering and monitoring review signed off with your DSL
• Spare devices, chargers and cables staged for week one

Frequently Asked Questions

When should a school start its IT preparation for September? Begin in early July, before the summer holidays start. Audits, licence renewals and hardware orders need lead time, and installers across the education sector are booked out through August. Aim to have everything except final testing finished by the second week of August.

What are the DfE digital and technology standards and do we have to meet them? They are non-statutory guidance from the Department for Education covering broadband, wi-fi, network switching, cyber security, filtering and monitoring in schools and colleges. They are not legally binding on their own, but inspectors, insurers and safeguarding audits increasingly use them as the benchmark. Meeting them is the most straightforward way to evidence good practice.

Who is responsible for IT readiness if our school has no IT manager? The responsibility sits with the school business manager or headteacher by default, even where the technical work is outsourced. The practical answer is to make your provider accountable for delivery against a dated plan and keep sign-off with you. That way the work is owned technically and governed internally.

How do we prove our filtering and monitoring is compliant? Keep a dated record of who reviewed the settings, what was tested, what was blocked and what changed. Test with real search terms across a sample of devices and user groups, including guest and BYOD connections. Written evidence, reviewed at least annually and after any system change, is what an inspection will ask for.

You have roughly a fortnight of usable working time before staff return. Whatever is not owned by Friday will still be unowned in September, and it will surface in front of a full classroom. The schools that start term smoothly are rarely the ones with the biggest budgets. They are the ones where somebody wrote down what had to be true by a specific date and checked it. If your current arrangement leaves you finding faults on day one rather than fixing them in August, that is a supplier problem, not a school problem.

Book a 20-minute readiness review with our schools team and we will give you a prioritised list of what to fix before INSET Day.

Book your readiness review →