Choose MIS assurance when your priority is the quality of supported records from your authorised MIS connection. Choose wider data assurance when important review questions also depend on agreed files, datasets or supported external sources. Both packages focus on visibility, action and evidence of progress.
When is MIS assurance the right starting point?
MIS assurance is the appropriate starting point when your priority questions concern supported pupil or learner records in the authoritative MIS. Examples include missing core details, enrolment inconsistencies and linked contacts requiring review.
The package brings available checks, searchable evidence, saved issue views, monitoring and assigned findings into a consistent process. Source-correction tasks and later-import verification help staff demonstrate follow-through. The exact fields and rules depend on the approved connection and mapping.
Read next: Define your first MIS checks
When should an institution choose wider data assurance?
Wider data assurance fits questions that depend on information outside the MIS as well as core records. Examples include reviewing a departmental spreadsheet or understanding an approved dataset alongside another source.
The wider package includes MIS assurance and agreed additional sources. Candidate coverage includes CSV/Excel datasets, supported API or SQL sources, and SharePoint lists or libraries subject to access and setup. Document search and OCR require configuration and verification; naming a source type is not a promise that every system is supported.
| Requirement | MIS assurance | Wider data assurance |
|---|---|---|
| Supported authorised MIS records | Included in agreed scope | Included in agreed scope |
| Checks, saved issue views and monitoring | For supported MIS data | Also for agreed additional datasets |
| Finding ownership and review | Included | Included |
| Additional sources and linked datasets | Outside the MIS-focused scope | Agreed and verified during scoping |
| Pricing and implementation | Quoted for your requirements | Quoted for your requirements and sources |
What should you prepare before connecting another source?
Prepare a clear purpose, data owner and access model for every additional source. Decide which records and fields are necessary, how current they must be and how you will handle changes or revocation.
Where datasets need linking, agree the matching key and review unmatched or duplicate keys explicitly. Retaining every source row can help reveal coverage gaps; silently losing unmatched records makes a reassuring report less reliable.
- Named source owner and authorised audience.
- Relevant fields and a defined review question.
- Expected refresh schedule and failure handling.
- Matching keys, exceptions and reference-data versions.
- Deployment, retention and support requirements.
What should a useful product demo prove?
A useful demonstration should follow one of your questions from source data to a finding, assignment and resolution evidence. Ask to see missing access or an incomplete import as well as a successful case.
Confirm how users see their authorised records, how an issue remains open and how later data verifies a correction. For colleges, ask specifically about learner mappings and any ILR-related scope. Keep a written record of requirements confirmed and work still needed.
Read next: View the product and package options
How do you get a package price?
Ask Education Host to quote against the institution, data scope and implementation requirements discussed in the demo. These guides do not publish a universal subscription price or setup timetable.
Agree the required connections, permissions, refresh schedules and support arrangements before committing to a rollout. Choose the smallest scope that answers your priority questions, with a clear plan for any additional sources.