Evaluate before wider rollout
Pilot programme and decision framework
Scope a Cloud Pulse, student-hosting or school-software pilot with representative scenarios, evidence owners, success criteria and a proceed, revise or stop review.
An Education Host pilot is a scoped evaluation of a real platform against an institution's agreed requirements. Choose a representative module, cohort or school workflow, agree terms and permitted data, then collect evidence for a proceed, revise or stop decision. Scope, duration, capacity, support and any charges are agreed before the pilot begins.
Discuss your pilot requirementsWhat should each platform pilot demonstrate?
Choose scenarios that expose the requirements driving the purchase, including an exception or failure case. The examples below are evaluation prompts, not promises of compatibility or a standard pilot package. Include the intended platform name in your pilot enquiry.
| Platform | Real scenario to agree | Evidence to collect |
|---|---|---|
| Cloud Pulse | One practical module using the required apps, operating systems, access method and lab-network design | Students complete the exercise; access, lecturer preparation, capacity assumptions and recovery issues are recorded |
| Student Web Host Manager | One representative cohort with publishing, lecturer access, a late joiner and an assessment/lifecycle exception | Account reconciliation, correct roles, working coursework, restore and agreed marking access |
| Cover Manager | A school-approved absence/approval/cover workflow, with manager review and a timetable or availability exception | Staff access, explainable manager-reviewed suggestions, daily information and the handling of missing/unavailable data |
| Trip Manager | A representative visit through the school's configured approvals, parent involvement and register/report workflow | Appropriate staff/parent access, agreed data handling and a realistic exception or update |
What should you send to scope a Cloud Pulse pilot?
Use the Azure Lab Services Migration Planner to prepare an ungated, downloadable module brief. Confirm software/licensing, image suitability, operating systems, identity, network boundaries and recovery needs; planner output identifies questions to resolve and does not certify compatibility or a migration date.
- Module, intended exercise and teaching/technical owners.
- Total students, expected simultaneous use and target teaching/decision dates.
- Operating systems, apps, licences, storage/persistence and permitted network activity.
- Current delivery arrangement, including any Azure Lab Services dependency.
- Identity, data/security, support and procurement requirements, plus unknowns.
What must be agreed before a pilot starts?
Agree the platform, scope, exclusions, dates and evidence needed. Confirm permitted users/data and institutional approvals before real teaching or records are involved. A demo, trial access and a supported operational pilot can have different scopes; the proposed terms should identify which activity is being agreed.
- Any charge, capacity/usage limits, licences and included support.
- Institutional and provider responsibilities, authorised contacts and escalation.
- Data/security review, permissions, retention, recovery and any safeguards.
- Success criteria, evidence owners, decision authority and review date.
- Stop conditions, export/wind-down and the approval needed for any later rollout.
How should success criteria and observations be recorded?
Agree thresholds with the people who will use and operate the platform. Record the scenario, expected result, actual observation, evidence owner and unresolved action. The scorecard is a template; missing evidence is not a pass and a small trial does not establish institution-wide savings.
| Criterion | Evidence to record | Who should review |
|---|---|---|
| Workflow fit | Representative task completed, unsupported steps and configuration used | Lecturer or school workflow owner |
| Access and permissions | Intended roles, restricted visibility, joiner/change/leaver or parent/staff exception | Identity/technical and service owners |
| Operational effort | Observed setup/support work and recurring tasks; comparable baseline if available | Operational owner and budget holder |
| Recovery and lifecycle | Agreed restore/export/restriction scenario and retained assessment/operational evidence | Technical and records owners |
| Security and data | Required reviews, permissions and unresolved blockers for the intended data/use | Institutional security/data reviewers |
| Commercial readiness | Costs, responsibilities, scope changes, ongoing support and exit assumptions | Procurement and authorised decision owner |
When should you proceed, revise or stop?
Proceed when the agreed critical criteria have evidence, required approvals are complete and the wider scope is understood. Revise when a bounded issue has an owner, a proposed change and a retest. Stop when a critical requirement cannot be met or the unresolved risk/work makes the proposed service unsuitable.
Record the decision, remaining actions, data/export arrangements and next approval. Agree whether pilot configuration can be reused and what needs testing for a larger deployment. Do not treat the pilot as automatic approval or assume its scale, price or support scope carries forward unchanged.
| Decision | Record | Next action |
|---|---|---|
| Proceed | Criteria met, accepted conditions, remaining actions and authorised approval | Scope and agree the next deployment; use the implementation acceptance plan |
| Revise | Issue, owner, proposed change, permitted data and retest criteria/date | Retest the affected scenario before changing the decision |
| Stop | Critical gap, decision authority and approved wind-down | Complete agreed exports, retention/deletion, access removal and commercial closure |
Pilot programme and decision framework — frequently asked questions
Direct answers for IT, security, procurement and teaching teams.
Is a pilot free?
Do not assume that. Any pilot charge, duration, capacity, licensing and support are agreed during scoping. A demonstration or trial and a supported teaching/operational pilot may have different terms.
Can we use live pupil or student data before review?
Agree permitted data, access, required documents and institutional approvals before a pilot uses real records. A trial is not an exemption from the institution's review process.
How long should the pilot run?
Agree a duration that tests the representative workflow and critical criteria, including simulated exceptions where appropriate. There is no fixed duration promised on this page.
What if an important scenario has not been tested?
Record it as untested with an owner and next decision. Obtain the missing evidence or revise the scope rather than assuming a pass from the demonstration or another platform's behaviour.
Will the pilot automatically become a full contract?
A wider purchase and rollout need the agreed approval and terms. Confirm the pilot end, any continuation, data wind-down and the conditions for further deployment before starting.
How do we request a pilot?
Use the pilot enquiry route and include the platform name, representative workflow, approximate scale, target dates and questions to prove. Leave sensitive records and credentials out of the initial enquiry.
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.
