Who looks after your school's technology after deployment?

A school technology project does not end when the devices arrive or the Wi-Fi goes live. Accounts change, software needs updates, equipment develops faults and staff need help when lessons are about to start.

If you are planning a refresh, agree who will look after the environment after handover. A clear support arrangement helps your school understand what is covered, who to contact and which costs continue beyond installation.

Start with ownership, not a list of tools

Your school may have an internal IT team, external providers or a combination of both. The useful question is whether each task has an owner and an escalation path.

• Who manages staff and student accounts?
• Who maintains devices, network equipment and classroom AV?
• Who checks backup results and coordinates recovery testing?
• Who follows up alerts and supplier faults?
• Who approves changes and communicates planned interruptions?

Document the boundaries between your school, its managed service provider and specialist vendors. Include any systems the provider does not manage.

Keep device management current

A well-planned rollout gives devices a consistent starting point. Ongoing management keeps that setup aligned with the way your school operates.

• Maintain an asset register and record device ownership.
• Agree how operating-system and application updates will be tested and deployed.
• Review enrolment, configuration and access policies as requirements change.
• Define how lost, faulty and retired devices will be handled.
• Clarify which BYOD tasks the school or provider can support.

Ask what monitoring covers and what action follows an alert. Monitoring and remediation should each have a defined scope.

Make account changes part of everyday operations

New staff, departing users and changing roles all affect access. Agree a repeatable process for requesting, approving and completing those changes.

Include administrator permissions, multi-factor authentication, shared accounts and external access in the review. Keep responsibility for policy decisions with the school, supported by technical advice and implementation where agreed.

Agree how backup and recovery will work

Start by identifying the information and systems your school relies on. Then confirm what is backed up, how failures are reported and how a recovery request will be handled.

• Which services, records and devices are included?
• Who reviews failed backup jobs?
• How are restoration tests scoped and recorded?
• What recovery priorities and targets have been agreed?
• Which licences, storage charges and recovery work are included or separate?

Ask for evidence of the agreed checks. Backup coverage and recovery targets should be confirmed for your environment rather than assumed from a package name.

Plan support around teaching hours and term peaks

Support needs can increase during enrolment, device refreshes and the start of term. Explain those busy periods before agreeing a service plan.

Confirm support hours, channels, onsite arrangements and escalation contacts. Distinguish a response target from a resolution target, and check how project work, after-hours requests and excess workload are charged.

Where the school has its own IT team, an external provider can take on agreed tasks or add capacity during peak periods. The division of work should be explicit.

Turn recurring problems into a practical improvement plan

Repeated Wi-Fi complaints, meeting-room issues or sign-in problems can point to a wider issue. Use support records to identify what keeps interrupting staff and which improvements deserve priority.

A regular service review can cover unresolved problems, asset condition, upcoming projects and the next term’s requirements. Measure specific operational changes, such as repeated incidents or deployment completion, without assuming they prove improved teaching or wellbeing.

Questions to ask before signing a support agreement

• Which sites, users, devices and platforms are covered?
• What work is included, and what requires a separate quote?
• Who owns each operational task and policy decision?
• What are the support hours and escalation arrangements?
• How are security incidents and recovery requests handled?
• Which licences, onboarding and recurring charges are additional?
• How will service performance and changes be reviewed?
• What documentation and access will the school receive at handover or exit?

Connect the refresh with the support plan

The Command Line helps schools plan equipment, deployment and technology projects. For the ongoing MSP side, The Urban Network advertises managed IT support, endpoint management, backup and education services covering campus Wi-Fi, BYOD and cloud learning environments. Availability, responsibilities and service levels should be confirmed in your proposal.

Discuss ongoing school IT support with The Urban Network, or start an education planning conversation with The Command Line.

Still planning the equipment and rollout? Read our 2027 school technology refresh guide for a checklist covering Wi-Fi, devices, classroom AV and security.