This benchmark helps schools and trusts understand the level of demand and complexity placed on their IT operation.
It looks at factors such as organisational scale, technical footprint, safeguarding and compliance expectations, and the extent of change or transition underway. Together, these give a clear picture of how much IT capacity is typically required — independent of whether support is delivered in-house, by an external provider, or through a hybrid model.
The benchmark does not assess the quality of your current IT provision, and it does not prescribe a specific team size. Instead, it provides a neutral, leadership-friendly sense-check that can be used to support planning, governance discussions, and procurement decisions.
The questions should take around 5–10 minutes to complete. You’ll receive an immediate summary explaining where your organisation sits and what that usually implies for IT capacity and sourcing.
What we’re looking at
These questions help establish the overall scale and structure of your organisation. This sets a baseline for IT demand and provides important context for interpreting the benchmark results.
A1. What best describes your organisation?
A2. Approximately how many pupils are you responsible for in total?
Please enter a whole number. This captures overall scale only and will be interpreted alongside the number of sites and organisational structure.
A3. How many physical sites are supported by IT?
Please include all schools, offices, and operational sites that rely on shared IT systems or support. This helps the benchmark understand distribution and coordination overhead.
A4. What phase(s) do you operate?
What we’re looking at
This section looks at how complex your IT environment is to support and how dependent day-to-day teaching and operations are on reliable technology. These factors influence the level of specialist knowledge, resilience, and responsiveness required.
B1. Which best describes your IT environment?
B2. How dependent are teaching and core operations on IT systems?
B3. Approximately how many user devices are supported in total?
This includes staff and pupil devices. The benchmark will consider this alongside the number of sites and the level of standardisation.
B4. How standardised is your IT environment?
B5. Are there specialist or mission-critical systems that require dedicated expertise?
What we’re looking at
This section considers the non-negotiable requirements placed on IT, including safeguarding, data protection, regulatory compliance, and the level of governance and assurance expected. These factors increase demand on IT capacity even where systems appear technically simple.
C1. To what extent are safeguarding processes dependent on IT systems?
C2. How would you describe the sensitivity and volume of data handled?
C3. What level of external scrutiny or audit applies to your IT arrangements?
C4. How formal are the governance and assurance expectations around IT?
C5. How complex is your supplier and contract landscape?
What we’re looking at
These questions identify whether you are operating in a period of change or transition. During such periods, IT demand, risk, and uncertainty are often temporarily higher than steady state.
D1. Are you currently undergoing, or about to undergo, a major IT-related transition?
For example, a managed service or PFI contract ending, a significant change in operating model, or a major migration of systems or infrastructure.
D2. Are systems or infrastructure changing ownership or responsibility?
This includes scenarios where responsibility is moving from an external provider to the organisation, or between internal teams.
D3. How confident are you that systems and infrastructure are well documented?
This includes configuration, dependencies, credentials, and operational knowledge.
D4. How much change is IT currently expected to support?
What we’re looking at
This section looks at how resilient IT needs to be and the role it is expected to play beyond day-to-day support. These expectations significantly influence the level and shape of IT capacity required.
E1. How tolerant is the organisation of IT disruption?
E2. How dependent are senior leaders on reliable IT systems and reporting?
E3. Is IT expected to actively enable strategic change?
For example, supporting organisational change, standardisation, efficiency, or new ways of working.
E4. How important is confidence and assurance in IT arrangements?
Based on the structure, distribution, and expectations placed on IT in your organisation.
Click on a band to read the description.
Typical context
Band 1 reflects environments where IT demand is limited, stable, and predictable. Technology supports core activity but does not place sustained or complex demands on the organisation.
This is most commonly seen in small, single-site organisations with a straightforward technical footprint and limited reliance on custom or highly integrated systems.
In this band, IT is an enabler rather than a driver of organisational complexity.
IT capacity characteristics
IT support in Band 1 environments is typically light-touch and intermittent. Demand is usually reactive, with relatively few concurrent issues or changes to manage.
Capacity may be provided by a single individual, a shared role, or an external provider offering basic support and maintenance.
Formal processes and documentation are often minimal, because the scale of the environment does not require them.
Common risks if capacity is misaligned
The primary risk in this band is not under-capacity, but over-engineering. Introducing unnecessary systems, processes, or complexity can quickly increase demand without delivering proportionate benefit.
There is also a risk that reliance on a single individual or supplier goes unrecognised, though the overall impact of disruption is usually limited.
Common delivery models
Band 1 organisations are most commonly supported through simple managed services, shared arrangements, or part-time in-house provision.
At this level, the most effective models are those that remain proportionate, flexible, and aligned to actual need rather than anticipated growth.
Typical context
Band 2 organisations are operating in an environment where IT plays an important and visible role, but the overall level of complexity remains moderate and largely manageable.
This is commonly seen in smaller trusts, growing schools, or organisations that are beginning to standardise systems and rely more heavily on digital processes, but without the scale or distribution that drives sustained complexity.
IT is important in this band, but it is not yet under continuous strain. Demand fluctuates rather than remaining constant.
IT capacity characteristics
In this band, IT support is typically required on a regular but not constant basis. There may be predictable busy periods, such as refresh cycles or the start of the academic year, but these are interspersed with quieter periods.
Capacity is often provided by a small team or individual, sometimes alongside other responsibilities, with an increasing need for basic documentation, standard processes, and forward planning.
At this level, IT is often still able to absorb change without formal structures, but the limits of that approach are beginning to be visible.
Common risks if capacity is misaligned
Where IT capacity is stretched, organisations in this band may experience slower response times, reliance on informal knowledge, or an increasing sense that IT work is crowding out other priorities.
There is a risk that early warning signs of growing complexity are missed, leading to reactive decisions later. These risks usually arise gradually and are easy to underestimate.
Common delivery models
Band 2 organisations are commonly supported by a small in-house resource, a part-time role, or a managed service providing routine support with occasional additional input.
At this stage, clarity around responsibilities and expectations is often more important than increasing raw capacity, particularly as the organisation grows or changes.
Typical context
Organisations in Band 3 have reached a point where IT is business-critical and consistently relied upon. Teaching, safeguarding, administration, and leadership activity all depend on technology working reliably every day.
This is commonly seen in larger single schools, growing trusts, or organisations with multiple sites, established systems, and increasing expectations around assurance and reporting. IT demand is no longer occasional or reactive — it is sustained and predictable, even if not always formally planned.
IT capacity characteristics
In this band, IT support typically needs to be continuously available, not just responsive when something goes wrong.
Common characteristics include a steady volume of support requests throughout the year, regular change activity such as device refresh and onboarding, and a growing need for documentation, standardisation, and forward planning.
At this level, IT capacity usually needs to extend beyond “keeping the lights on” and begin supporting coordination, consistency, and resilience.
Common risks if capacity is misaligned
Where IT capacity does not match the level of demand, organisations in this band often experience growing backlogs of unresolved issues, fragile knowledge held by one or two individuals, and inconsistent experiences across sites or teams.
There is often little time for preventative work or improvement, leading to frustration at leadership level despite “having IT support”. These issues are rarely caused by lack of effort; more often they reflect an underestimation of how much work the environment now generates.
Common delivery models
Band 3 organisations are commonly supported through a small in-house team with broad generalist skills, a hybrid model combining in-house capacity with specialist or overflow support, or a managed service where expectations and service design align well with operational reality.
At this level, the success of the model depends less on whether support is internal or external, and more on whether roles are clearly defined, capacity is sufficient for both day-to-day demand and planned change, and responsibility for resilience and assurance is explicit.
Typical context
Band 4 reflects a period of transition, change, or uncertainty, rather than a long-term steady state. Organisations in this band are often undergoing significant change that temporarily increases risk and demand on IT.
This commonly includes scenarios such as a managed service or PFI contract ending, a move between operating models, major system or infrastructure migration, trust growth or reorganisation, or a change in key IT personnel or responsibilities.
Importantly, this band does not imply that IT is poorly run. In many cases, it reflects a deliberate and necessary transition that requires additional capacity and attention while the organisation stabilises.
IT capacity characteristics
During transitional periods, IT capacity is often stretched by a combination of business-as-usual demand and additional change activity. Work that might normally be absorbed into routine operations now competes with planning, migration, handover, and risk management.
Common characteristics include increased reliance on temporary solutions, duplicated effort, parallel systems, or a higher level of oversight and coordination to maintain continuity and safeguarding.
At this stage, IT capacity needs to support stability first, then transition, rather than optimisation or long-term improvement.
Common risks if capacity is misaligned
Where capacity is insufficient during transition, organisations may experience heightened operational risk, unclear ownership of systems, loss of critical knowledge, or an over-reliance on informal workarounds.
There is also a risk that short-term pressures crowd out proper planning, leading to decisions that are expedient rather than sustainable. These risks are not a reflection of poor intent, but of the inherent complexity of managing change without adequate bandwidth.
Common delivery models
Band 4 environments are often supported through temporary or hybrid arrangements, such as interim in-house capacity, enhanced managed service support, or targeted consultancy alongside existing teams.
The focus at this stage is usually on clear ownership, continuity, and risk reduction, with the intention of moving towards a more stable steady-state model once the transition is complete.
Successful organisations in this band are those that recognise the transitional nature of the situation and plan explicitly for what comes next, rather than treating the current state as permanent.
Typical context
Band 5 reflects environments where IT is highly complex, widely distributed, and strategically critical to the organisation’s ability to operate. Technology underpins not only day-to-day activity, but also assurance, compliance, resilience, and long-term planning.
This band is commonly seen in larger or more mature trusts, highly distributed organisations, or settings with significant regulatory, safeguarding, or data protection obligations. The scale and interdependence of systems means that failures or weaknesses can have wide-reaching consequences.
At this level, IT is no longer a background service. It is a core organisational capability that requires active leadership and sustained investment.
IT capacity characteristics
Organisations in Band 5 typically require dedicated, multi-skilled IT capacity with clear separation between operational support, infrastructure, security, and strategic planning responsibilities.
Common characteristics include continuous demand across multiple sites, a high volume of concurrent initiatives, formal change management, and a strong emphasis on standardisation and assurance.
At this level, IT capacity must support not just delivery, but also governance, resilience testing, supplier management, and forward strategy.
Common risks if capacity is misaligned
Where capacity does not match the level of complexity, organisations in this band may experience systemic risk rather than isolated issues. This can include inconsistent standards across sites, fragile dependencies on individuals or suppliers, and limited visibility of risk at leadership level.
There is also a risk that strategic decisions are delayed or taken without sufficient technical insight, leading to increased cost, inefficiency, or exposure over time. These risks arise not from poor intent, but from the challenge of sustaining oversight at scale without sufficient bandwidth.
Common delivery models
Band 5 organisations are commonly supported through structured in-house teams, often complemented by specialist external support for defined areas such as security, infrastructure, or large-scale change.
Managed services may still play a role, but typically as part of a hybrid or federated model, with strong internal capability retained to set direction, manage risk, and assure delivery.
Success in this band depends on clear accountability, mature governance, and a shared understanding at leadership level that IT capacity is a strategic enabler rather than a discretionary cost.
Your result is:
