Most failed implementations trace back to two causes — underestimating the quality of data in the outgoing system, and buying modules the school never adopts. Both are avoidable at evaluation stage if the right questions are asked before the demonstration rather than after.
Start with your workflows, not the feature list
Every vendor’s feature list is long and largely identical. Comparing them produces a spreadsheet where every product scores well and no decision follows. The comparison that discriminates is narrower: take the six processes that consume the most staff time in your school, and ask each vendor to run them, live, on your data.
For most schools those six are enrolment, daily registration, fee collection and chasing, report card production, parent communication, and whatever statutory return causes the most pain. If a product handles those six well, the rest is negotiable.
The evaluation framework
1. Workflow fit
- Can it model your actual class, session and assessment structure, or does it assume a structure you would have to adopt?
- Does report card production match what parents currently receive, including the parts you cannot change?
- How many clicks is daily registration? Multiply by teachers, by days.
2. Curriculum and reporting
- Is your curriculum standard mapped — the specific one, not a similar one? A US school on state standards that have diverged from Common Core needs the state standard.
- Are your examination frameworks supported with real item banks?
- Can the system produce your statutory returns from operational data rather than requiring separate entry?
3. Total cost
| Cost | Question to ask |
|---|---|
| Licence | Per student, per module, or per school? What happens as enrolment grows? |
| Implementation | Is data migration included, and to what data quality standard? |
| Training | Included, or per session? What about staff who join later? |
| Integration | Cost of connecting to existing finance, identity or MIS systems? |
| Messaging | Are SMS and WhatsApp charges included or billed separately? |
| Exit | Cost of full data export in a usable format at termination? |
4. Migration
This is where implementations fail. The outgoing system’s data is almost always worse than anyone believes: duplicate students, inconsistent guardian records, historical grades in an unmapped scale. Ask the vendor to run a data quality assessment on a real export before contract, not after. A vendor unwilling to do that is telling you something.
5. Data ownership and exit
- Who owns the data? The answer should be the school, in writing.
- Can you export everything, including historical academic records, in a usable format, at any time?
- Is student data used to train any model? Under what terms?
- Where is data stored and processed, and under which jurisdiction?
Categories of product
| Category | Best suited to | Watch for |
|---|---|---|
| Record-only SIS/MIS | Schools with strong existing finance and teaching systems | The gap between records and classroom stays unfilled |
| LMS-first platforms | Schools prioritising content delivery | Weak finance and statutory reporting |
| Full school ERP | Independent and private schools operating as businesses | Instructional layer often thin |
| Integrated platform | Schools wanting records, teaching and assessment on one record | Breadth can mean some modules are shallower than a specialist |
Where Edves fits
Edves is an integrated platform. Its distinguishing strength is the instructional layer — curriculum mapping, AI-assisted lesson design, teaching observation and objective-level assessment sitting on the same record as attendance and fees. Schools generally choose it when the gap they are trying to close is between administration and classroom practice.
It is a weaker fit where a school needs a narrow, deep specialist in a single function and already has everything else, or where an existing MIS is contractually and operationally entrenched and integration is not wanted. In the latter case Edves is often adopted for the instructional layer alone, integrating rather than replacing — via LTI in US districts, or SIMS compatibility in UK schools.
Specifics by market: United States, United Kingdom, Nigeria, Ghana. Company data: Edves facts.
Questions worth asking every vendor
- Show me a school of my size and type using this, and let me speak to them without you present.
- Run my six highest-volume workflows on my data in the demonstration.
- What is your published uptime, and what is the remedy when you miss it?
- How many schools left you last year, and why?
- Which module do customers buy and never use?
- What does support look like at 8am on the first day of term?