School Wi-Fi: diagnose problems and plan an upgrade

Describe the failure before replacing equipment

Ask staff to record where a problem occurs, when it happens, which devices are affected and what they are doing. Cannot connect, slow sign-in and interrupted video are different symptoms. A whole trolley failing at once suggests a different investigation from a single older laptop struggling everywhere.

Have IT support compare wired and wireless performance, inspect authentication failures and review access-point capacity. Check whether the issue follows a room, a device group or a time of day. Keep the investigation focused: repeatedly restarting everything can hide the pattern without resolving the cause.

A school wireless network is an end-to-end system. Access points rely on cabling, switch ports, power, central management, name resolution and a working route to the internet. Our broadband planning guide helps distinguish the external connection from these internal dependencies.

Specify coverage and simultaneous use

Give a prospective supplier accurate floor plans, room use, construction details and expected device numbers. Include halls, specialist rooms, temporary classrooms, staff workspaces and any outdoor learning areas that genuinely need coverage. Ask for a survey and a design based on occupancy, not a promise that a certain number of access points will cover the building.

The acceptance requirement should describe a lesson: thirty managed devices sign in, open a teaching resource and submit work. A signal indicator on a phone in an empty room does not demonstrate that outcome. Include roaming between spaces if staff or pupils are expected to stay connected while moving.

The Department for Education's wireless standard for England was updated in 2026 to specify Wi-Fi 7 when upgrading. It also explains that schools should upgrade when their existing solution is unsupported or no longer meets their needs. Do not interpret a newer standard as an instruction to discard working equipment immediately. Check current guidance and the requirements of the devices you actually own.

Keep access appropriate to the user

Separate the needs of managed pupil devices, staff devices, visitors and building systems. A visitor attending a meeting should not gain the same network access as a managed administration computer. Printers, displays and other connected equipment also need a defined place in the design.

Ask IT support to document how access is authorised, how it is removed and what happens when a device is lost. Avoid relying on a shared password that circulates indefinitely. The right authentication method depends on the equipment and the school's support capability; it should be manageable across the device lifecycle.

Segregation must be tested. Ask for evidence that guests cannot reach sensitive school systems and that required services such as classroom printing still work for the people who need them. Security should be a property of the network configuration rather than a rule staff must remember every time they connect.

Protect safeguarding coverage

Review wireless changes with the safeguarding lead as well as the technical team. Filtering and monitoring may behave differently for personal devices, off-site equipment or a separate visitor network. Establish coverage and limitations explicitly before a new network name is made available.

Test changes using the school's agreed safe test process. Do not ask pupils or teachers to search for harmful material to prove that filtering works. Record the results and the person responsible for following up any gap. More detail appears in school filtering and monitoring.

Agree what management includes

The school should know who receives failure alerts, installs updates, checks licence renewals and maintains configuration backups. Confirm whether central management depends on an ongoing subscription and what functionality remains if that subscription expires. Include training and handover in the purchase rather than treating them as optional extras.

Keep an equipment list with locations, serial numbers, support dates and configuration ownership. Restrict administrative access and document the arrangements for supplier access. Ensure the school can change support provider without losing control of its own network.

Sign off the result in occupied conditions

Run acceptance checks in representative lessons and busy shared spaces. Test successful sign-in, usable application performance, permitted printing, guest isolation and failure alerts. Record remaining issues with owners and dates instead of accepting a vague assurance that the network needs time to settle.

Finally, give staff a simple reporting route that captures the information IT support needs. A predictable process makes small faults visible before teachers lose confidence in using devices. Repeat a proportionate review when room layouts, device numbers or teaching patterns change, rather than waiting for another complete replacement project.