Building a school IT strategy that can be delivered

Begin with school priorities

Choose a small number of outcomes that technology can help achieve. Examples include reducing repeated office data entry, making classroom access more reliable or improving the way families receive essential information. Describe the current difficulty and who experiences it before naming a product.

A strategy is easier to evaluate when it says what will change. "Improve digital learning" is difficult to measure. "Make the agreed classroom resources available on the managed devices used in lessons" gives the team a concrete service to design and test.

Establish the current position

Bring together asset, contract and information registers, support issues, staff feedback and known risks. Identify unsupported equipment, renewals, unreliable services and tasks that depend on a single person. Include the systems that work well and should be retained.

Do not treat every complaint as a purchase request. Slow access might result from wireless coverage, account configuration, an overloaded service or a device fault. Ask for a technical explanation before allocating a device replacement budget to a different problem.

Connect the foundations to the ambitions

For schools in England, the Department for Education's digital and technology standards provide a reference for infrastructure and governance. Its current framework identifies core areas including connectivity, networks, digital leadership, filtering and monitoring, and cyber security. Use the applicable standards to inform the baseline rather than assuming that one new system makes the school digitally ready.

Map dependencies. A classroom platform may require reliable connectivity, managed accounts, suitable devices and staff training. Schedule those prerequisites before the feature that depends on them. The plan should make constraints visible so leadership can choose realistic priorities.

Compare a few credible options

For each problem, consider improving the existing service, changing the process, replacing the technology or accepting a limitation for a defined period. Record the benefits, costs, risks and effort of each option. Include the effect on workload and access for different users.

A small pilot can resolve uncertainty about usability or integration. Define what the pilot must demonstrate and when it will end. Avoid allowing a trial to become a permanent unsupported service simply because people have started using it.

Build a phased roadmap

Organise the work into manageable phases. An early phase may address ownership and urgent reliability issues, followed by infrastructure improvements and then service changes. Give every phase an accountable owner, resources, dependencies and acceptance evidence.

Include maintenance and renewals in the roadmap, not only new projects. Plan around school events, assessment periods, staff capacity and contract notice dates. A project that cannot be supported during term time is not ready merely because its installation date fits the calendar.

Make the financial plan explicit

Show one-off costs, annual commitments and expected replacement cycles separately. Include configuration, migration, training, support and exit costs. Explain which figures are quotes, estimates or assumptions, and consider what happens if the estimate changes.

The budgeting guide provides a worked example. The financial plan should also show who approves spending and what happens if funding is only available for part of a project. Avoid purchasing the visible equipment while leaving its essential management or support unfunded.

Choose useful measures

Use measures tied to the intended outcome. For reliability, this might be the frequency of interruptions to a particular service. For an office workflow, it might be the time required to complete a defined task and the number of corrections needed. For a website, it might be successful completion of common family tasks.

Record a baseline before the change and review after a realistic settling period. Avoid promising that usage counts alone prove better teaching or learning. Combine quantitative measures with staff and user feedback, and explain the limits of the evidence.

Review the strategy as circumstances change

Assign a leadership owner and a regular review cycle. Report progress, unresolved risks, costs and decisions needed in a format governors or trustees can understand. The digital governance guide describes this accountability in more detail.

Update the roadmap when school priorities, systems or budgets change. Keep a record of why decisions changed rather than quietly rewriting the original assumptions. A useful strategy remains short enough to guide decisions and detailed enough that someone can deliver its next phase.