Service scope and responsibility
Proposals distinguish included services, exclusions, service hours, escalation routes and the responsibilities that remain with the school or another supplier.
A practical overview of company information, service governance, data protection, transition planning and the evidence schools can request during procurement.
OpsWise provides clear legal and contact information so procurement teams can complete basic checks before discussing service detail.
View the Companies House recordThe exact documents depend on the agreed service and procurement route. These are the areas we expect a school to examine and discuss with any managed IT provider.
Proposals distinguish included services, exclusions, service hours, escalation routes and the responsibilities that remain with the school or another supplier.
Priority definitions, response targets, review meetings and useful measures are set out in the service schedule rather than left as informal expectations.
Access, privileged administration, data-processing terms, incident escalation and relevant supplier information are considered during service design and contracting.
Technical decisions involving filtering, monitoring, identity and devices are considered alongside the responsibilities of DSLs, leaders and governors.
Discovery, access handover, estate records, priority risks and named owners form part of the proposed implementation approach.
Contract discussions can cover continuity arrangements, ownership of information, return of access and practical cooperation with an incoming provider.
We would rather answer due-diligence questions directly than rely on badges or broad assurances. Evidence is supplied where it exists and its relevance to the proposed service is explained.
Availability and final wording depend on scope and the agreed contract. No certification or partnership should be inferred unless it is explicitly evidenced.A proposal explains the assumptions behind the scope so leaders can compare what is included, what is optional and what may remain with another supplier.
The number and type of users, devices, buildings and locations that need support.
Remote coverage, planned onsite time, service hours and the role of any internal IT team.
Identity, cloud platforms, networks, filtering, backups, servers, devices and third-party services.
Known service issues, cyber risks, safeguarding dependencies, lifecycle pressures and required projects.
Access handover, discovery, documentation, tooling, remediation and coordination with the outgoing provider.
Agreed term, responsibilities, optional work, licensing and supplier costs are shown separately where relevant.
Official guidance and our leadership checklist can support a more consistent comparison between suppliers.
This page is a general overview. A signed proposal, service agreement, data-processing agreement and service schedule take precedence.
Tell us what your school needs to assess and we will confirm what can be provided for the proposed service.