BEFORE YOU SELECT A VENDOR
A school ERP evaluation checklist
Pick the checks that matter to your school, then ask every vendor the same questions. A live demonstration and a written answer are stronger evidence than a feature name on a brochure.
Check 1
Compare the full cost
A monthly plan is only one part of the budget. Ask what changes with school size and what is billed separately.
- What is the price for our current student count, and what happens when it grows?
- Are setup, migration, training, taxes, payment fees, messages, calls, storage, or custom domains extra?
- What are the renewal, cancellation, and data-export terms?
Ask for: Keep a written quote with recurring and one-time costs separated.
Check 2
Test real school workflows
A long module list does not show whether the software handles the way your office and teaching teams work.
- Can the team move from an admission enquiry to an enrolled student record?
- Can the office review dues, record a payment, and find the receipt?
- Can teachers complete attendance and exam tasks using their own role?
Ask for: Ask each vendor to demonstrate the same tasks using the same sample scenario.
Check 3
Check academic fit
Make sure the assessment, timetable, report, and academic-year workflows match your school and its board.
- Can you set up our classes, sections, subjects, grading, and terms?
- Can you show a report card in the format our school actually uses?
- Can the school review and correct a result before it is published?
Ask for: Use a sample class and a real, non-sensitive report-card format in the demo.
Check 4
Plan migration and exit
Agree how existing records will move into the new system and how the school can retrieve them if it leaves.
- Which student, staff, fee, attendance, and academic records can be imported?
- Who checks errors and confirms that totals match after migration?
- What export formats and handover support are available at contract end?
Ask for: Request a sample import plan, validation steps, and data-export terms in writing.
Check 5
Try the family and teacher experience
Parents and teachers use the system differently from administrators. Test the app and notifications with those roles.
- Can parents find the information they need without navigating admin screens?
- Which devices, languages, and notification channels are supported?
- Can the school control who sees a student’s information?
Ask for: Have a teacher and a parent representative try the relevant tasks on their own phones.
Check 6
Review privacy and security controls
Student records are sensitive. Ask the provider to explain access, storage, recovery, and deletion in concrete terms.
- How are staff roles and permissions managed, and are important actions logged?
- How often are backups made, and how does a restore get tested?
- Where is school data hosted, how is it protected, and how is it deleted at exit?
Ask for: Read the privacy terms and request the provider’s written security and data-handling answers.
Check 7
Confirm implementation and support
A successful launch depends on clear ownership, staff training, and a support path after the demo.
- Who is responsible for setup, data migration, and staff training?
- What does the school need to prepare before go-live?
- What support hours, channels, escalation path, and response targets are included?
Ask for: Ask for an implementation plan and support terms that match the proposal.
Check 8
Check the school website separately
If a school website is included, check how your team edits it and what happens to the school’s domain and content.
- Can the school use its own domain and update notices, admissions, and contact details?
- Can staff control public pages and search metadata?
- What happens to the site and domain if the ERP subscription ends?
Ask for: Ask to publish a sample notice and confirm domain, hosting, and content-handover terms.