Buying from Education Host
Institutional procurement and buyer brief
Prepare an institutional purchase: supplier details, scoping brief, review evidence, quote comparison, approvals and exit questions for Education Host services.
Buying an Education Host service starts with a scoped requirement and a written proposal for institutional review. Agree the intended platform, users, responsibilities, evidence and commercial assumptions before committing. Use the blank buyer brief to keep teaching or operational needs, IT review and procurement decisions aligned; it is available without an enquiry form.
Download the blank procurement brief (.txt)What should your institution prepare before asking for a proposal?
Start with the problem and a representative workflow, then describe the scale, target date and constraints. A useful brief records what needs proving and who owns each decision. Describe sensitive data by category; initial scoping does not need records or credentials.
The editable text download combines the brief and supplier-question register. Complete it locally, mark unknowns and share an appropriate outline through your institution's agreed process. Downloading it does not submit an enquiry or save your answers on this website.
- Platform/service, module or school workflow, current arrangement and exclusions.
- Users/accounts, simultaneous demand where relevant, retained cohorts and growth.
- Software, identity, MIS/integration permissions and institution-owned dependencies.
- Data/security review, recovery, retention, support and handover requirements.
- Budget comparison period, target decision date, reviewers and authorised approver.
How does an institutional purchase progress?
Use the stages below as a review framework. The actual sequence, documents, dates and approval route depend on your institution and the proposed service; a consultation or pilot is not approval for a full deployment.
| Stage | Institutional contribution | Evidence before the next decision |
|---|---|---|
| Define the need | Teaching/operations lead identifies the workflow and intended outcome | A shared brief with scope, exclusions and critical requirements |
| Scope and demonstrate | IT and service owners review fit, dependencies and proposed responsibilities | Recorded answers, gaps and a representative demonstration or test plan |
| Review a written proposal | Procurement, finance, security and data-protection reviewers assess their areas | Costs, inclusions, terms, evidence requests and unresolved issues |
| Pilot where appropriate | Named owners agree permitted data, scenarios, criteria and pilot terms | Evidence supporting proceed, revise or stop; pilot approval remains distinct from wider approval |
| Agree and onboard | Authorised approver confirms the applicable agreement and operational owners | Acceptance plan, handover, support and lifecycle arrangements |
What supplier details and documents are published?
Education Host Ltd is registered in England and Wales, company number 09377245, with its UK office at 15 Penrice Road, Droitwich, WR9 8NS. Education Host was founded in 2011 and focuses on education services.
Education Host's company certification is Cyber Essentials. The published infrastructure accreditation information concerns the data-centre operator and facility; check the scope and current evidence for the requirement you are assessing. Deployment-specific assessments and contractual terms are addressed during procurement.
How should procurement compare proposals?
Use the same scope, period and assumptions for each option. Identify confirmed amounts, estimates, included work and exclusions. A line that has not been priced or answered should stay open rather than being treated as free or included.
| Area | Record in the comparison | Clarify before approval |
|---|---|---|
| Scale and capacity | Users/accounts, concurrency, storage, usage and retained material | Limits, growth assumptions and the cost of a scope change |
| Setup and ongoing cost | Migration, configuration, licences, recurring service and institutional staff work | Comparison period, VAT treatment, exclusions and one-off versus recurring items |
| Support and recovery | Who supports platform, applications and teaching/operations; agreed recovery scope | Coverage, escalation, maintenance and evidence needed for acceptance |
| Term and renewal | Pilot or service term, billing and renewal assumptions | Approval authority, notice requirements and the applicable written terms |
| Exit and handover | Exports, retained material, access removal and institutional ownership | Formats, dependencies, timing, charges and how live/archive/backup copies are handled |
What should be resolved before committing?
Keep a question register with the answer, evidence link, scope, owner, status and review date. Distinguish a published general statement from a deployment-specific response and a term in the proposed agreement. Ask the relevant institutional reviewer to accept or escalate each material gap.
- Reconcile the written proposal against the agreed brief and exclusions.
- Complete required supplier, security and data-protection reviews through the institution's process.
- Confirm identity/integration permissions, software licensing and responsibilities.
- Agree acceptance, support, recovery, renewal and wind-down arrangements.
- Record who may authorise a pilot, purchase, scope change and wider rollout.
Institutional procurement and buyer brief — frequently asked questions
Direct answers for IT, security, procurement and teaching teams.
Is the buyer brief a quote or contract?
No. It is a blank planning template for institutional requirements and supplier questions. Pricing, scope and applicable terms are confirmed in the written proposal and agreement.
Do we need to provide student or pupil records to obtain a proposal?
An initial enquiry can describe data categories, approximate scale and workflows without sending records, credentials or confidential datasets. Agree any later transfer, permissions and safeguards through the institutional review.
Can Education Host complete a supplier questionnaire?
Supplier questionnaires and security assessments are handled during scoping and procurement. Identify the required documents, reviewers and deadlines in your brief; deployment-specific answers need the proposed scope.
Does a pilot mean we have approved a full purchase?
No. Agree pilot scope, terms, data permissions and the decision process separately. A wider deployment needs its own authorised approval and agreed scope.
Are institutional prices and terms fixed on this page?
No. Institutional services are scoped per deployment. Confirm setup, recurring cost, capacity, licences, support, tax treatment, renewal and exit arrangements in the applicable proposal and agreement.
Where can our reviewers find the published policies?
The legal section contains the published policies. Review them alongside the security and data-protection information and confirm which documents and deployment-specific terms apply to the proposed service.
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.
