IT and data directors, COOs and central teams
Disconnected Systems and Spreadsheet Dependency
The trust has plenty of systems. The work falls into the gaps between them, and spreadsheets fill those gaps.
Who this affects
- IT and data directors
- Central operations teams
- School business professionals
- Anyone maintaining a critical spreadsheet
What usually makes it difficult
- The same information requested repeatedly
- Critical spreadsheets owned by one person
- No agreed source of truth for operational data
- Manual re-keying between systems
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 data map of what exists, where, and who owns it
- Connections through approved APIs, secure imports or maintained records
- Replacement of critical spreadsheets with owned, audited records
- Cross-system workflows that span more than one platform
- Provenance and refresh history on every connected field
Example workflow
- 1A critical spreadsheet is identified during the operations review.
- 2Its fields, owners and consumers are mapped.
- 3An equivalent record and workflow are configured.
- 4Data is connected or imported by an approved method.
- 5The spreadsheet is retired with the history retained.
Example management view
- Systems by school with owner and purpose
- Connection method and status
- Last verification date
- Proposed future connections
How the platform approaches it
- 1Map the landscape before proposing any change.
- 2Connect rather than replace wherever the existing system works.
- 3Minimise the data copied into EduGap.
- 4Retain source, confidence and refresh history.
Capabilities used
- Systems landscape
- Data mapping
- Approved connections and imports
- Cross-system workflows
- Provenance tracking
- Exception handling
Intended outcomes
Design goals for the platform, not measured results from real schools.
- Less duplicated data entry
- Fewer single-person spreadsheet dependencies
- Greater use of information the trust already holds
Integration availability depends on supplier APIs, permissions, security review and commercial arrangements. No connector is described as live until it has been built and agreed for your trust.
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 moreCybersecurity Coordination
Cyber risk is managed differently in every school, and the trust often learns about a gap only after an incident.
Read moreFiltering 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.