Central Visibility Without Central Bottlenecks: A MAT IT Model

The Context

As MATs grow, central teams often mandate that all IT decisions, purchases, and support requests must flow through the central office. While this provides total visibility, it inevitably creates a severe bottleneck. Local schools become frustrated as minor requests take weeks to approve, leading to a breakdown in trust between the academies and the central team.

Who This Guide is For

MAT executives, central IT directors, and headteachers within Trusts.

Why This Matters

A bottlenecked central IT team slows down teaching and learning. If a teacher has to wait three weeks for a new piece of software to be approved by a central committee, they will simply stop innovating. Conversely, if local schools have total autonomy without central oversight, the MAT risks compliance failures, duplicated costs, and cyber vulnerabilities.

What Good Looks Like

A "Hub and Spoke" model based on "Earned Autonomy." The central team sets the guardrails (security baselines, approved vendors, compliance standards) and monitors them automatically. Within those guardrails, local schools have the autonomy and budget to make rapid decisions that support their specific educational needs.

Approach and Methodology

1. Define the Guardrails: Establish strict, non-negotiable central policies (e.g., all devices must be enrolled in MDM, all software must pass a central DPIA).
2. Provide a Catalog: Create a pre-approved catalog of hardware and software. If a school orders from the catalog, approval is instantaneous. If they want something outside the catalog, it triggers a central review.
3. Delegated Administration: Do not force every password reset through the central helpdesk. Delegate specific, restricted administrative rights to local IT staff or office managers to handle immediate, low-risk operational tasks.
4. Automated Oversight: Use central management tools to monitor compliance silently. The central team doesn't need to manually check every device; the system should alert them only when a device falls out of compliance with the guardrails.
5. The Role of the Central Team: The central team transitions from being a "glorified helpdesk" to a strategic assurance and architecture function, focusing on major projects and cyber resilience rather than daily break-fix.

Evidence to Retain

• A documented Scheme of Delegation outlining exactly which IT decisions can be made locally versus centrally.
• The pre-approved IT procurement catalog.
• Automated compliance reports confirming local adherence to central guardrails.

Questions Leadership Should Ask

• "Are we centralizing this process to actually reduce risk, or simply because we don't trust our local staff?"
• "How long does it currently take for a school to procure and deploy a standard replacement laptop?"

Common Pitfalls

• The Illusion of Control: Mandating a central approval process but lacking the central staff to actually process the requests, bringing IT operations to a halt.
• Shadow IT Resurgence: Schools bypassing the slow central process entirely and buying equipment on personal credit cards to claim on expenses.
• Ignoring Local Context: Imposing a single device standard (e.g., iPads for everyone) that works well for a primary school but completely fails the needs of a secondary school computer science department.

How asitplan Can Help

asitplan provides the central visibility required for this model to work. Central teams can monitor asset health and compliance across all schools in real-time, intervening only when a school deviates from the established baseline, thus allowing local autonomy to flourish safely.