The short answer
To choose a school management system, start with the problems you need to solve, not a feature list. Write down your must-have workflows, involve the people who will use the system every day, score each vendor against the same checklist, test with your own data in a pilot, check data security and privacy terms in writing, and compare the total cost over several years, including setup, training and migration. The best system is the one your registrar, teachers and families will actually use every day.
A note on fairness: Borderset sells a school management system, so we have an interest in this decision. The checklist below is vendor neutral and works for evaluating any product, including ours. If you want a ranked comparison, see our separate review of school management systems for 2026.
Step 1: Start with your problems and goals
Before you look at any product, list what is going wrong or what needs to change. Typical examples:
- Attendance is taken on paper and entered twice.
- Families get messages from three different tools.
- The registrar rebuilds report cards in spreadsheets every term.
- Timetable changes lead to double-booked rooms or teachers.
- Leaders cannot see enrollment, attendance or payments across campuses in one place.
Turn each problem into a measurable goal, such as cutting the time to produce report cards or getting attendance into the system by a set time each morning. These goals become your success criteria for the pilot.
Step 2: Build a small selection team
Include one person from each group that will rely on the system: a school leader, the registrar or office manager, two or three teachers, someone responsible for IT and data, and someone from finance if the system will handle fees. For language academies and tutoring businesses, include a front desk or scheduling coordinator. A small team decides faster, but every group should see the shortlist before you sign.
Step 3: Use a feature checklist
Score every vendor against the same questions. Mark each item as must have, nice to have or not needed for your school.
Student records
- One profile per student that follows them from enrollment to graduation or exit.
- Guardian and emergency contacts, with more than one household per student.
- Custom fields for your context, such as program, level, campus or language.
- Document storage for forms, consents and health information with restricted access.
- Easy transfers between classes and campuses without losing history.
Attendance
- Fast attendance taking on a phone or tablet, by period or by day.
- Custom absence codes that match your policies and any reporting rules.
- Automatic alerts to families and staff when a student is absent or late.
- Reports on chronic absence and trends by class, grade and campus.
Grading, exams and progress
- Gradebooks that support your scales: letters, percentages, standards or levels.
- Exam scheduling and results entry with clear deadlines.
- Report cards and transcripts generated from the same data, not retyped.
- Progress views that teachers, students and families can understand.
Timetables and scheduling
- Class, room and teacher schedules with conflict checks.
- Support for make-up lessons, substitutions and term changes.
- Calendars that families and staff can see.
Parent and family communication
- Announcements to the whole school, a class, or individual families.
- Language and channel options that match your families.
- A family portal or app with attendance, grades, schedules and invoices.
- A record of what was sent, to whom and when.
Payments and administration
- Invoices, payment tracking and reminders tied to each student.
- Teacher management: assignments, schedules and records.
- Dashboards for leaders across campuses.
Step 4: Check data security and privacy
A school management system holds some of the most sensitive data your school has. Ask every vendor for written answers to these questions and have someone qualified review the contract.
| Question | Why it matters |
|---|---|
| Who owns the data, and how do we export it if we leave? | You need your records back in a usable format. |
| Does the system offer role-based access and audit logs? | Staff should see only what their role needs, and you should be able to see who changed what. |
| How is data encrypted in transit and at rest? | Basic protection against interception and breaches. |
| Is single sign-on and multi-factor authentication supported? | Reduces password risk for staff accounts. |
| Where is data stored and who are the subprocessors? | Some schools and regions have residency or contract requirements. |
| What is the breach notification process? | You need to know how quickly you will be told. |
| Will the vendor sign your data privacy agreement? | Many US districts and states require one. |
| What independent security reviews or certifications can the vendor show? | Ask for evidence, not just claims on a website. |
In the United States, the US Department of Education's Student Privacy Policy Office publishes guidance on FERPA and working with online service providers. If children under 13 use the system directly, the Federal Trade Commission's COPPA Rule may also be relevant. Many states have their own student privacy laws. Schools outside the US should check local rules such as GDPR. This is general information, not legal advice.
Step 5: Check integrations and migration
A system that does not connect to your other tools creates double entry. List the tools you already use, such as Google Workspace for Education, Microsoft 365, rostering services, accounting software and your learning platform, and ask how each connection works, who maintains it, and whether it costs extra.
Then ask about moving your data in. Good questions include: which records the vendor will import, how they handle duplicates and messy historical data, how long migration usually takes, and whether you can run old and new systems side by side for a short period. Our SIS data migration and cleanup checklist covers this step in detail.
Step 6: Run demos and a pilot with real tasks
Vendor demos show the best path through a product. Ask instead for a demo of your own scenarios, and then a pilot with real users. A useful demo script:
- Enroll a new student with two households and a custom field.
- Take attendance for a class on a phone and send an absence alert.
- Move a student to another class mid-term and check that history is kept.
- Enter exam results and produce a report card.
- Change a teacher's timetable and see what conflicts appear.
- Send an announcement to one class's families and check the delivery record.
- Create an invoice and record a payment.
- Log in as a teacher and confirm what data they can and cannot see.
During the pilot, measure against the goals from Step 1 and collect feedback from teachers and office staff, not only leaders.
Step 7: Compare total cost, not just the price
Pricing models vary: per student, per teacher, per school or flat fees. Compare the full cost over three years:
- Subscription fees at your expected enrollment, including growth.
- Setup, data migration and training fees.
- Charges for integrations, extra modules, storage or support tiers.
- Internal staff time for setup and ongoing administration.
- Contract length, renewal increases and exit terms.
A simple vendor scorecard
Weight each area by how much it matters to your school, score each vendor from 1 to 5, and multiply. The weights below are only an example.
| Area | Example weight | Vendor A | Vendor B |
|---|---|---|---|
| Student records | 15% | 1 to 5 | 1 to 5 |
| Attendance | 15% | 1 to 5 | 1 to 5 |
| Grading and exams | 15% | 1 to 5 | 1 to 5 |
| Timetables | 10% | 1 to 5 | 1 to 5 |
| Family communication | 15% | 1 to 5 | 1 to 5 |
| Data security and privacy | 15% | 1 to 5 | 1 to 5 |
| Integrations and migration | 5% | 1 to 5 | 1 to 5 |
| Total cost and contract terms | 10% | 1 to 5 | 1 to 5 |
Also call two or three current customers similar to your school and ask what onboarding was really like and how support responds.
Common mistakes when choosing a system
- Choosing on features alone without testing everyday tasks.
- Leaving teachers out until after the contract is signed.
- Underestimating data migration and training time.
- Accepting security claims without written answers.
- Ignoring exit terms and how to get your data back.
- Rolling out everything at once instead of in phases.
Where Borderset fits
Borderset is a cloud school management system for tutors, language academies, K-12 and multi-campus schools. It covers student profiles, guardians and attendance, scheduling and make-up lessons, exams and progress, payments and invoices, teacher management and announcements to families, with role-based access and audit trails. Plans and the pilot option are on our pricing page. Use the checklist above to test it against your needs, and if it is on your shortlist, book a demo with your own scenarios.
Related reading on Borderset
If you are still on spreadsheets, start with why one student information system beats spreadsheets. Once you have chosen, plan the rollout with our SIS rollout checklist for school IT and training teachers on new school management software.
Frequently asked questions
What should I look for in a school management system?
Look for strong student records, fast attendance, grading and report cards from one data source, conflict-free timetables, family communication with a delivery record, role-based access, clear data ownership and integrations with the tools you already use.
How long does it take to choose a school management system?
Many schools take one to three months to define needs, compare vendors and run a pilot. Allow extra time for data migration and training before the start of a term.
What is the difference between a school management system and an LMS?
A school management system runs school operations such as enrollment, attendance, schedules, grades, fees and communication. A learning management system delivers lessons, assignments and course content. Many schools use both and connect them.
What security questions should I ask a school software vendor?
Ask who owns the data, how to export it, how data is encrypted, whether role-based access, audit logs, single sign-on and multi-factor authentication are supported, where data is stored, how breaches are reported, and whether the vendor will sign your data privacy agreement.
Should we run a pilot before signing a contract?
Yes, if possible. A pilot with real users and your own data shows whether everyday tasks are actually faster, which demos rarely reveal.
How should we compare school management system pricing?
Compare total cost over about three years, including subscription fees at expected enrollment, setup, migration, training, add-ons, support tiers, renewal increases and exit terms.