Planning IT across a multi-academy trust

Define what should be shared

A multi-academy trust in England may coordinate strategy, purchasing, identity management and support across schools. That does not mean every school should receive an identical technology project at the same time. Start by identifying which shared arrangements solve a real problem.

Useful candidates include account lifecycle rules, security expectations, asset records, contract visibility and support reporting. Local teaching needs, specialist equipment and building constraints may still justify differences. Write down the reason for an exception and who reviews it, rather than letting undocumented variation accumulate.

Build a reliable school-by-school baseline

For each site, record connectivity, network equipment, devices, key systems, contracts, support arrangements and known risks. Include ownership of domains and cloud accounts. Describe the condition and support status of the service, not just the number of devices.

Use a consistent format so the trust can compare needs. A school with newer equipment may still have a serious access or recovery problem; a school with older devices may have a stable service for its intended tasks. Avoid ranking priorities solely by age or the loudest request.

Separate joining-day needs from later improvements

When a school joins a trust, identify what must work immediately: communication, authorised access, support contacts and critical operational services. Preserve essential continuity while ownership and responsibilities are confirmed.

Then plan later integration in manageable stages. A simultaneous change of email, identity, management information and classroom services creates several dependent risks. Where possible, prove one migration and its support arrangements before beginning another. Record temporary arrangements and their expiry or review date so they do not become permanent by accident.

Design access around responsibilities

Define who needs access to which school, data and service. A trust-wide account does not automatically justify access to every pupil record. Use role-based access and involve the appropriate data protection and safeguarding staff in decisions affecting their responsibilities.

Consider staff working across sites, temporary cover, central teams and leavers. Document the authoritative source for identity information and how changes reach connected services. Test unusual cases such as a person moving between schools or holding two roles, rather than designing only for a single permanent employee.

Make the support model understandable

Tell staff how to raise a problem, what information to provide and how urgent issues are escalated. Distinguish local hands-on work from central administration and contracted support. Agree who owns a fault when it crosses those boundaries.

Use a consistent severity model based on service impact. A whole-school connectivity failure is different from one damaged keyboard, but a single user's access problem may still be urgent if it prevents a critical task. Reporting should help prioritise the school impact rather than merely count closed tickets.

Coordinate purchasing with implementation capacity

Shared purchasing can make requirements and contract management more consistent, but the trust still needs a suitable procurement route and evidence of value. Include deployment, training, support and exit work when comparing proposals. The procurement guide provides a structured method.

Plan installation around each school's calendar and local readiness. A trust-wide device delivery is not a completed project if charging, storage, accounts or wireless service are missing. Assign school-level acceptance checks as well as central technical checks.

Report outcomes and exceptions

Give leaders and trustees a view of reliability, security risks, spending, overdue actions and project benefits. Show material differences between schools without exposing unnecessary personal or incident details. A trust average can hide one site with a persistent problem.

Keep an exception register for departures from agreed standards. Record the reason, risk, mitigating steps, owner and review date. This allows proportionate decisions while preserving visibility. It is more useful than claiming complete standardisation when staff are working around an unsuitable central process.

Keep governance connected to local experience

England's DfE digital leadership and governance guidance provides a reference for responsibilities and planning, but the trust must apply those responsibilities to its actual structure. Explain which decisions belong centrally and which school leaders can make locally.

Review the IT strategy with feedback from school staff and service users. When a shared approach works, capture the practical conditions that made it work. When it creates unnecessary difficulty, revise it openly. The aim is a dependable service across the trust with clear accountability, not uniformity for its own sake.