School digital governance: decisions, ownership and evidence

Give digital technology a leadership owner

Identify a senior person who is accountable for the direction and effectiveness of technology. That person does not need to carry out every technical task, but should understand the decisions required and ensure the right people are involved.

In England, DfE's digital leadership and governance standard describes a senior leadership digital lead and suggests considering a digital link role among governors or trustees. Apply responsibilities to the school's actual structure rather than assuming a particular job title exists. Small schools can share support, but accountability should remain clear.

Distinguish the main responsibilities

Use a simple responsibility table to prevent work falling between teams. The example below is an organisational starting point, not a statement that every role must be held by a separate person.

Responsibility	Practical focus
Leadership	Outcomes, priorities, risk decisions and resources
IT delivery	Configuration, maintenance, technical evidence and recovery
Finance and business management	Budgets, contracts, renewals and procurement coordination
Safeguarding	How technology supports safe practice and escalation
Data protection	Advice and oversight concerning personal information
Governance	Appropriate scrutiny, challenge and assurance

Record who is consulted and who approves a decision. A technician can describe a risk and propose a fix; leadership may need to decide how to fund it or whether a temporary limitation is acceptable.

Keep the records that support decisions

Maintain useful information about equipment, contracts and the information held in systems. Each record needs an owner and an update process. A spreadsheet can be adequate when it is accurate, controlled and actually used; a costly platform does not fix unclear responsibility.

Include renewal and notice dates, administrative ownership and planned review points. Reconcile records when equipment is installed, moved or disposed of and when services are introduced or retired. The purpose is to make operational and financial decisions possible, not to collect detail nobody can maintain.

Connect risks to actions

Describe a risk in terms of the school activity affected, its cause and the likely consequence. "The only person who can recover the domain account is leaving" is more actionable than "website risk". Record existing controls, the proposed action, an owner and a review date.

Distinguish a problem already happening from a future risk. An unavailable service needs incident handling; the chance of another failure may also need a longer-term improvement. Keep sensitive details in the appropriate restricted record rather than in a broadly circulated board paper.

Ask for evidence that is understandable

Governors and leaders need assurance that controls work, not a list of technical acronyms. A backup report can state when a representative restoration was last tested, what was recovered and what remains unresolved. A support report can explain repeated disruptions to a particular activity and the plan to address them.

Use trend information carefully. A rise in reported incidents may reflect better reporting rather than a worse service. A low number of support tickets can conceal staff avoiding an unreliable system. Ask what the measure means and combine it with practical evidence from users.

Make approval proportional to the change

Define who can approve routine maintenance, new services, access changes and material spending. Ensure urgent work has an escalation route when the usual approver is unavailable. Record decisions that accept a significant risk or commit future funding.

Do not require a board meeting for every minor configuration correction. Equally, a new service handling pupil information should not arrive solely because an individual staff member accepted an online trial. Give colleagues a clear route to request useful technology and receive a timely decision.

Review contracts and outcomes together

Before a renewal, ask whether the service still meets the school's needs, whether it is used effectively and whether known issues have been resolved. Review the complete cost and any practical difficulty in leaving. The procurement guide explains how to evaluate a future arrangement.

A service can be technically available and still fail its original purpose. Use the IT strategy to connect renewal decisions to intended outcomes, rather than renewing automatically because changing would require discussion.

Use a repeatable governance cycle

At agreed intervals, review major risks, service performance, current projects, upcoming renewals and decisions needed. Assign actions and check completion at the next review. Adjust the level of detail to the school's scale and risk.

Keep a clear record of decisions and reasons. The resulting governance process should help the school act sooner, make ownership visible and learn from experience. It should produce decisions and follow-through, rather than a larger collection of reports nobody uses.