Skip to content
Explore the interactive fictional MAT demonstration.Open the demo
Vendor-neutral by design

Keep the systems that work. Connect the operations around them.

EduGap gives trusts a consistent operational environment even when individual schools use different MIS, finance, HR, IT and compliance platforms.

Designed to complement existing systems. No named third-party integration is connected in this demonstration.

Different systems, one operational view

Preserve local systems. Create common operational control.

Growing trusts often inherit different MIS, finance, HR, payroll, productivity, IT support, websites, compliance processes, policy approaches and supplier contracts.

A shared layer across the trust

EduGap provides a shared operational layer across a multi-academy trust. It connects responsibilities, reviews, risks, actions, evidence, policies, contracts and service providers in one controlled environment.

Local system choices can remain in place while trust-wide workflows use consistent owners, dates, evidence, approvals and reporting.

What we coordinate

The work between your systems

  • Responsibilities

    A consistent trust-wide operational record with ownership and traceability.

  • Reviews

    A consistent trust-wide operational record with ownership and traceability.

  • Actions

    A consistent trust-wide operational record with ownership and traceability.

  • Risks

    A consistent trust-wide operational record with ownership and traceability.

  • Evidence

    A consistent trust-wide operational record with ownership and traceability.

  • Policies

    A consistent trust-wide operational record with ownership and traceability.

  • Contracts

    A consistent trust-wide operational record with ownership and traceability.

  • Suppliers

    A consistent trust-wide operational record with ownership and traceability.

  • Approvals

    A consistent trust-wide operational record with ownership and traceability.

  • Reports

    A consistent trust-wide operational record with ownership and traceability.

Your existing technology landscape

Examples and potential integration points

These names illustrate systems a trust may already use. Their inclusion does not imply endorsement, partnership or a live integration.

MIS examples

Examples
  • Arbor
  • Bromcom
  • PowerSchool
  • SIMS
  • Other approved MIS platforms

Productivity examples

Examples
  • Microsoft 365
  • Microsoft Teams
  • SharePoint
  • Google Workspace
  • Google Drive

Business system examples

Examples
  • Finance
  • HR
  • Payroll
  • Procurement
  • Helpdesk and ticketing
  • Policy management
  • School websites
  • Document management

Potential integration subject to supplier access and technical approval. Integration availability depends on supplier APIs, permissions and commercial arrangements.

Three ways to introduce information

Use the lightest appropriate method

    Approved API connection

    An authorised exchange where a suitable supplier API, permission and approved purpose exist.

    Controlled file import

    A reviewed import with source, date, owner, confidence and change history retained.

    Secure reference or manual record

    Link to authorised source material or maintain the minimum operational facts directly.

Minimal data approach

Coordinate operations without copying unnecessary pupil data

Many operational workflows need responsibility, status, deadlines, assurance and evidence—not pupil-level records. The platform is designed to record the minimum information required for the approved purpose.

EduGap is not a pupil database, attendance system, assessment system, safeguarding case-management system or parent communication platform.

Human and technical assurance

  • Confirmed purpose
  • Data minimisation
  • Appropriate permissions
  • Supplier approval where required
  • Security review
  • Data protection review
  • Testing
  • Named system owner
  • Monitoring
  • A documented method for disconnecting it

MIS platforms generally manage

  • Pupil records
  • Attendance
  • Behaviour
  • Assessment
  • Timetables
  • Parent communication
  • Statutory returns
  • School-level pupil reporting

EduGap coordinates

  • Trust-wide responsibilities
  • Operational actions
  • Risks and mitigations
  • Policies and acknowledgements
  • Evidence and assurance
  • Digital standards
  • AI product governance
  • Suppliers and contracts
  • Cross-school instructions
  • New school onboarding
  • Education partner service delivery
  • Cross-system workflows
  • Leadership and board reporting

EduGap does not compete with your MIS. It coordinates the operational work that sits around—and often between—the systems used throughout your trust.

Discovery

Map Your Trust’s Systems Landscape

Tell us which systems your schools use and where cross-system coordination is hardest. We will respond with an honest view of where a shared operational layer may help.

Submitting this form does not create an integration or technical commitment.

Book a discovery call

Fields marked with an asterisk are required.