From scope to service
Implementation, acceptance and handover
Plan an Education Host rollout with platform dependencies, institutional owners, acceptance tests, recovery decisions and operational handover requirements.
Implementation connects the agreed service scope to tested institutional workflows. Identify the platform dependencies, allocate responsibilities and agree the evidence needed for acceptance before teaching or school operations depend on the service. Dates, migration, support and recovery arrangements are scoped for the deployment; the roadmap below is a planning framework.
Review the rollout roadmapWhat should happen before an operational rollout?
Use a staged plan with an owner and a decision at each handover. These are example institutional contributions, not a fixed delivery schedule or a statement that every task is included in every proposal.
| Stage | Owners and dependencies to agree | Evidence for the next decision |
|---|---|---|
| Scope and baseline | Service/teaching/operations owner; workflow, users, data and commercial brief | Representative use case, exclusions, critical requirements and open-question register |
| Environment and access | Technical and identity owners; software, permissions, roles and integration access | Configured access tested with authorised representative roles and reconciled account/data scope |
| Workflow and exceptions | Lecturer or school operational lead with technical support | The real exercise/workflow plus an agreed exception, recovery and restricted-access scenario |
| Pilot or phased acceptance | Evidence owners and authorised decision maker | Criteria reviewed against observations, remaining issues and a proceed/revise/stop decision |
| Handover and review | Named ongoing service/support/policy owners | Support route, maintenance, recovery, access/lifecycle review and change/exit arrangements |
Which dependencies differ across the platforms?
Confirm the requirements of the actual workload. Successful sign-in is only one part of readiness, and a demonstration using sample data does not establish readiness for all institutional integrations.
| Platform | Prepare and confirm | Demonstrate before reliance |
|---|---|---|
| Cloud Pulse | Module exercise, image/apps/licensing, capacity, lab networks, permitted activity and SSO where configured | Student access from intended devices/networks, lecturer workflow, workload fit and agreed recovery/closure checks |
| Student Web Host Manager | Hosting stack, unique accounts/cohorts, naming, identity, assessment and lifecycle policy | Cohort reconciliation, appropriate student/lecturer access, publishing, restore and marking/exception workflow |
| Cover Manager | Staff roles, school rules, absence/approval workflow, duty arrangements and Wonde/MIS permissions where used | Approved absence to manager-reviewed cover workflow, authorised visibility and a missing-data/exception case |
| Trip Manager | Visit types, school approvals, parent involvement, registers and Wonde/MIS permissions where used | Representative visit through the agreed workflow, authorised parent/staff access and register/report handling |
How should responsibilities be divided?
Name people or roles for the work retained by the institution as well as the proposed Education Host tasks. The written scope should identify platform/infrastructure work, institution-owned identity and permissions, application/content maintenance, school or academic policy, training and support. The matrix below is an allocation checklist, not a pre-agreed responsibility contract.
| Work area | Institutional owner to identify | Confirm in the service scope |
|---|---|---|
| Identity and integrations | Authorised IT/identity or school MIS owner | Permissions, configuration, source data, joiner/leaver changes and troubleshooting route |
| Teaching or operational policy | Module lead, school manager or visit/cover owner | Acceptance rules, permitted activity, assessment/approvals and exceptions |
| Applications and content | Technical or content owner | Software/licences, updates, student-created content and support boundaries |
| Platform operations | Institutional service contact with Education Host | Setup, maintenance, monitoring, backup/recovery and issue escalation |
| Records and commercial decisions | Records/data-protection and procurement owners | Retention, access reviews, renewal, scope changes and wind-down approval |
What makes an acceptance check useful?
Write a scenario, expected result, agreed threshold, evidence owner and decision owner. Record the date, configuration, actual observation and unresolved issue. An untested item stays open. Use representative roles and permitted data, including a failure or exception case that matters to your workflow.
- Reconcile users or records against the intended scope, including an exception.
- Prove authorised access and demonstrate the relevant permission boundary.
- Complete the real teaching or operational workflow, not only a login.
- Test the agreed recovery/export and lifecycle action without risking live records.
- Record the decision and the conditions to resolve before wider use.
What if a test fails, and what is needed at handover?
Agree the stop conditions, safe fallback and decision authority before a pilot or migration. A rollback or return to an earlier arrangement depends on data changes, access and technical constraints; record what can actually be reversed and test it where appropriate. A failed critical check should trigger a decision, not an automatic wider rollout.
At handover, confirm authorised contacts, support/escalation, maintenance, recovery, training needs, retained issues and the next review. Include how later user, integration or policy changes are approved and how the service can end. These records should be usable by the people operating the service after the project team changes.
Discuss your institutional requirementsImplementation, acceptance and handover — frequently asked questions
Direct answers for IT, security, procurement and teaching teams.
How long does implementation take?
Dates depend on platform scope, readiness, permissions, integrations, migration and acceptance requirements. Agree the schedule and dependencies during scoping; this roadmap is not a fixed delivery commitment.
Does Education Host do every implementation task?
Responsibilities are agreed in the proposal. The institution normally needs owners for its identity/permissions, source data, teaching or operational policy, review and acceptance. Identify the exact split before starting.
Does successful SSO mean the platform is ready?
No. Also test provisioning/roles, the real workflow, integrations, exceptions, recovery and handover requirements relevant to the deployment.
Do all MIS connections work automatically?
No universal connection or data availability is implied. Cover Manager and Trip Manager use supported Wonde routes subject to school onboarding, permissions and available MIS data. Confirm and test the intended fields and workflow.
Can a failed rollout always be rolled back immediately?
Do not assume that. Agree stop conditions, data handling, fallback and decision authority in advance. What can be reversed depends on the deployment and changes already made.
What happens after acceptance?
Hand over the agreed support and maintenance arrangements, authorised contacts, recovery/lifecycle procedures, unresolved actions and review dates to named ongoing owners. Confirm later change and exit arrangements too.
Every deployment starts with a conversation
Tell us about your institution, modules and requirements — we will answer the technical and commercial questions honestly, including where something is not the right fit.
