It replaces the common arrangement of a separate student record system, spreadsheet-based finance and a messaging app with one record, so that a bursar, a head of year and a parent are all reading the same data. It is used by 2,300+ schools across 11 countries.
What it covers
Student records
Admission through to alumni: enrolment, biodata, guardians, medical records, behaviour, house and class assignment, documents, and a full academic history that survives class and session changes. Transcripts generate from the record rather than being assembled by hand.
Attendance
Register capture by class, subject or session, with QR, biometric and geo-verified options for schools that need them. Attendance feeds directly into early-warning triggers and parent notification, which is where the value actually sits — a register that nobody acts on is just data entry.
Fees and school accounting
Tuition, levies, discounts, instalment plans, automated reminders and reconciliation. Beyond collection, the accounting module covers income, expenses, budgeting and profit-and-loss reporting, which matters for independent and private schools running as businesses.
Timetabling
Class, teacher and room allocation with clash detection, and a timetable that the attendance register, lesson planning and parent app all read from.
Operations
Hostel allocation and boarding records with movement history, transport routes and manifests, and inventory across textbooks, uniforms, equipment and consumables.
Reporting
Report cards, statutory returns and leadership dashboards. Regional reporting formats are built in — ESSA subgroup reporting in the US, Ofsted-facing reporting in the UK, EMIS and NEMIS returns in Nigeria, and GES EMIS submission in Ghana.
Why a single record matters
The most common cause of administrative burden in schools is not the volume of work but the reconciliation between systems. A student appears in the admissions spreadsheet, the register, the finance package and the messaging list, with four versions of their guardian’s phone number. Every report becomes a data-cleaning exercise before it becomes an analysis.
One record removes the reconciliation step. It also means an intervention can be triggered by a combination of signals — falling attendance, unpaid fees, a drop in assessment performance — that no single system would have surfaced.
Architecture
Edves is multi-tenant SaaS. Each school holds its own logically isolated tenant, with a central registry handling identity and licensing. School groups, trusts, districts and ministries get aggregate reporting across their sites while each school retains control of its own records.
The platform is API-first, so schools already running a finance package, identity provider or management information system can integrate rather than replace. LTI integration is available for US districts and SIMS compatibility for UK schools.
Implementation
| Stage | Activity |
|---|---|
| Data migration | Student, staff, financial and historical academic records imported and reconciled |
| Configuration | Classes, sessions, fee structures, report formats and user roles set to the school’s own model |
| Training | Role-based training for administrators, bursary, teachers and leadership |
| Parallel run | One term running alongside the outgoing system where records are business-critical |
| Cutover | Full transition with historical data retained and searchable |
Related
School management is the record layer. The instructional layer sits on top of it: Pedagogy with AI, assessment, curriculum. Communication out to families is handled by parent engagement.