It can operate as the school’s management information system or alongside an existing MIS, depending on what the school wants to consolidate.
What it covers
Admissions and pupil records
Application through to on-roll, with pupil and contact details, medical information, consents, SEND status, pupil premium and service premium eligibility, EAL status, and full history across the pupil’s time in the school. Records survive phase transitions, which in many schools is where history is currently lost.
Timetabling and attendance
Timetable construction with room and staff allocation, driving registers and the parent app so a change propagates once. Session-level attendance with statutory codes, persistent and severe absence flagged automatically. See attendance.
Assessment and reporting
Curriculum-referenced assessment with progress tracking and group disaggregation, and reports to parents generated from the record rather than assembled from collected mark sheets. See assessment and progress.
Behaviour and rewards
Incident recording on a shared taxonomy so the data can be analysed, positive recognition recorded alongside sanctions, and distribution analysis by pupil group and by staff member.
SEND
Register, provision mapping, delivery logging and structured plans — see SEND and inclusion.
Statutory returns
Census and statutory data generated from operational records rather than compiled separately, so what is returned matches what the school actually holds.
The join is the point
Most UK schools have each of these functions covered by something. What they do not have is the join.
A head of year asked why a Year 9 cohort is underperforming needs attendance, assessment, behaviour, SEND status and intervention history in one view. In most schools that requires four logins and a spreadsheet, so it happens once a term rather than when it would be useful.
Under a framework grading six evaluation areas separately, that join stopped being a convenience. See report cards.
Replacing or complementing an existing MIS
Schools arrive at this from two directions, and both are legitimate.
- Replacement. Usually driven by a contract renewal, a price increase, or frustration with a system that has not changed in years. Requires proper migration and is not a mid-year exercise.
- Complement. Keeping the MIS as the statutory record while Edves handles curriculum, assessment, SEND provision, observation and parent engagement. Lower risk, and sensible where the MIS is stable but the layers around it are fragmented.
Which is right depends on what is actually broken. A school whose MIS works but whose assessment lives in six spreadsheets has a different problem from one whose MIS is the problem. Be wary of any vendor who recommends replacement before understanding which you are.
Implementation
| Stage | Activity |
|---|---|
| Data assessment | Review of existing records against a real sample — before contract, not after |
| Migration | Pupil, staff, structure, assessment and attendance history imported and reconciled |
| Configuration | Year structure, assessment framework, report formats, behaviour policy, roles and permissions |
| Training | Role-based for office, pastoral, SENCO, teaching staff and leadership |
| Parallel period | One term alongside existing practice where records are business-critical |
| Cutover | Full transition with historical data retained and searchable |
Record quality in the outgoing system is almost always the limiting factor, and almost always worse than the school expects. Start at the beginning of an academic year where possible; any vendor comfortable with a mid-year MIS migration is prioritising the sale.
Access and safeguarding boundaries
Role-scoped access down to field level: a subject teacher sees their own classes, a SENCO sees SEND detail, safeguarding records sit behind separate permissions, and every access is logged. This is a KCSIE and UK GDPR requirement as much as a feature — see KCSIE and UK GDPR.