Skip to content
Explore the interactive fictional MAT demonstration.Open the demo

COOs, central services and school business professionals

Operational Management

Central service requests, recurring checks, policies and operational actions are handled differently in each school and tracked in inboxes.

Who this affects

  • Chief operating officers
  • Central service teams
  • School business professionals
  • IT and estates leads

What usually makes it difficult

  • Requests arriving by email with no shared queue
  • Recurring checks that quietly stop recurring
  • Knowledge held by individuals rather than the organisation
  • No comparable view of operational performance across schools

What EduGap could build

An indicative scope for this area

Actual scope is agreed during the operations review and recorded in your system blueprint.

  • A central service request queue with routing and escalation
  • Recurring operational checks with evidence
  • Trust-wide action management with owners and dates
  • Digital and operational standards tracking
  • Service performance reporting to schools

Example workflow

  1. 1A school raises a central service request.
  2. 2It is routed to the responsible team with a target date.
  3. 3Related records and prior requests are shown to the handler.
  4. 4Work is completed and evidence attached.
  5. 5Service performance is reported to the school.

Example management view

  • Open requests by team and age
  • Recurring checks due this month
  • Overdue actions by school
  • Escalations awaiting decision

How the platform approaches it

  1. 1Capture operational work in one place with clear ownership.
  2. 2Standardise the steps that should be consistent.
  3. 3Preserve justified local differences.
  4. 4Report delivery honestly, including what is late.

Capabilities used

  • Service request management
  • Recurring schedules
  • Action management
  • Standards tracking
  • Escalation rules
  • Service reporting

Intended outcomes

Design goals for the platform, not measured results from real schools.

  • Fewer lost requests
  • Operational knowledge retained by the organisation
  • Consistency where it matters

This coordinates operational work. It is not a full ITSM suite and does not certify statutory compliance.

Related areas

  • Digital Leadership and Governance

    Digital responsibility is often shared between a trust IT lead, a school business manager and an external provider — with nobody holding the whole picture.

    Read more
  • Cybersecurity Coordination

    Cyber risk is managed differently in every school, and the trust often learns about a gap only after an incident.

    Read more
  • Filtering and Monitoring Reviews

    Reviews are expected regularly, but the record of who checked what, when, and what they found is often thin.

    Read more

Could your trust operate with greater clarity?

Book a discovery call to talk through how your trust currently coordinates operational work — or explore the fictional demonstration first.