Guide
How to Choose a School Management System: Process and Demo Tests
How to run a school management system selection: who to involve, writing down current work, setting non-negotiable rules, shortlisting, what to test in a demo, comparing quotes and getting approval.
In short
Choose in this order: (1) form a selection team and name the decision-maker, (2) write down your current work and registers, (3) set the rules you will not change, (4) shortlist, (5) have every candidate run the same scenario in a demo, and (6) compare quotes on the same terms. In the demo, test who enters, who corrects, who approves and what comes out — not the length of the feature list.
Last updated: October 26, 2026
Selection team and decision-maker
When daily users and the approver are both involved, less is reworked after go-live.
- One person from each department that will use it daily (academic affairs, student affairs, office, classroom managers).
- Whoever handles fees and invoicing, if you will use them.
- Whoever is responsible for personal data and devices.
- The person who gives final approval, and the deadline — work back from your budget cycle.
Write down your current work
Collect your current registers and forms before looking at products. They become the test material: can the system produce the same thing?
- Registers: student list, attendance register, grade lists, invoices and payments, job placement and residence lists.
- Forms: certificates, report cards, transcripts, invoices, lists used for notifications and reports.
- Annual calendar: admission, term changes, grade finalisation, fee invoicing, notification and reporting dates.
- Pain points: heavy re-keying, deadline-driven work, tasks only one person can do.
Set your non-negotiable rules
Separate practices you can change to suit a system from rules you cannot. The rules you cannot change become your shortlist criteria.
- Attendance: lateness, early leave and approved absence (公欠), how the rate is calculated, when warnings are issued.
- Grade finalisation: who enters, who finalises, who approves corrections afterwards.
- Certificate approval: who approves between request and issue, and the issue record.
- Fees: invoicing period (monthly, per term, yearly), reductions, instalments.
- Visibility: which records homeroom teachers, subject teachers and office staff may see.
Shortlist
Shortlist by the type of solution that suits your school and by the price unit. Large university suites, packages built for a type of school, K-12 校務支援 systems, juku tools, in-house builds on kintone or similar, and Excel each suit different schools and cost structures.
Narrow to about three candidates and give each the same material: your registers, forms and rules.
What to test hands-on in a demo
Ask every candidate to run the same scenario in the same order. Rather than listening to a presentation, watch who enters, who corrects, who approves and what comes out.
- Vocational school
- Same scenario for every candidateTake lesson attendance → warn students with many absences → homeroom teacher records a meeting → finalise grades → approve and issue a transcript
- What should come outAttendance-rate list, meeting record, certificate
- Japanese-language school
- Same scenario for every candidateRegister a residence card → find students whose attendance fell → list upcoming expiry dates → output the list used for a notification
- What should come outExpiry list, attendance list, notification list
- University
- Same scenario for every candidateCourse registration → lottery for an over-subscribed course → enter and finalise grades → check missing credits against graduation requirements
- What should come outClass list, missing-credit list
- Private K-12
- Same scenario for every candidateGuardian reports an absence → register updates → enter term assessments → print report cards
- What should come outAttendance register, report cards
- Juku or lesson school
- Same scenario for every candidateGuardian reports an absence → books a make-up lesson → teacher writes a lesson report → invoice monthly fees
- What should come outMake-up record, lesson report, invoice
- Driving or training school
- Same scenario for every candidateRegister a trainee → record training progress → confirm completion
- What should come outProgress and completion records
Do not mark something “not supported” just because it could not be shown on the day; keep it as a question and get a written answer.
Compare quotes on the same terms
Ask for quotes on the same student numbers and scope, split into these five lines:
- Monthly (or annual) fee and its price unit — how students are counted.
- Set-up and onboarding support.
- Data migration and checking after import.
- Training.
- External services such as payments and messaging, and how you receive your data when the contract ends.
Approval and timing
Attach to the approval paper not only the comparison table but also what you saw in the demos and the answers to open questions.
Work back from the start of a school year or term, leaving time for data clean-up, a trial and staff practice.
Common mistakes
- Choosing by the length of the feature list without trying daily tasks.
- Watching a different scenario from each vendor, so nothing could be compared.
- Comparing only the monthly fee and missing migration, training and external services.
- Deciding within one department and clashing with another department’s rules.
- Not checking how data is returned when the contract ends.
In Classio
Classio has demo environments for each type of school. In a consultation we run the scenarios above on screen, as close as we can to the registers and forms you share. Prices are published, so you can check the monthly figure before asking for a quote.
Frequently asked questions
- How long does a selection take?
- Many schools allow several months from writing down registers to demos, quote comparison and approval. Start by working back from the year you want to go live.
- Do we need an RFP?
- It helps when there are many candidates or the decision must be explained inside the school corporation. A template keeps easily forgotten items — data export, exit terms — in every request.
Related pages
Sources
Regulatory statements follow the scope of the cited documents. External documents do not certify Classio’s behaviour or compliance.
Sources checked: October 18, 2026
Start from how you work today
Want to run the same scenario in Classio?
Tell us your type of school and current registers, and we will prepare a demo scenario.