Ask a head of operations how many systems their international/independent school runs on, and the answer usually leaves them scratching their head. There’s the MIS. The learning platform. The admissions tool. Something for trips, something for payments, something for the buses. A reporting tool somebody added for the IB. And a spreadsheet or two holding it all together.
None of it was a bad decision at the time. Tech builds up gradually and before you notice, it gets overwhelming. The thing is, nobody designed it as a whole, and that’s where the cost sits. Not in any single product, but in the joins between them.
This guide is for school leaders who are choosing, reviewing or replacing school software. It covers what education technology actually includes, where your MIS fits, the trade-off between integrated suites and best-of-breed tools, and how to make a decision you won’t be unpicking in three years.
EdTech is short for education technology. It’s any software or digital tool that supports teaching, learning or running a school. In practice, the term covers two quite different groups of products.
The first is classroom technology: the tools teachers and students use directly, such as learning platforms, assessment tools and digital resources.
The second is school software in the wider sense, sometimes called school management software, or operational software. These are the systems that run admissions, student records, curriculum planning, reporting, payments, transport and communication with families.
Most writing about EdTech focuses on the first group. This guide looks at how both fit together, because that’s where most schools feel the pain.
Whatever your size or curriculum, your software has to cover six broad jobs, particularly if you run an international or fee-paying setting. Some schools buy a separate product for each. Others buy several from one provider. Either way, it helps to see the whole map before you change any part of it.
Your MIS or SIS holds the core record: who your students are, which classes they’re in, attendance, contacts and permissions. Almost every other system needs some of this data. That makes it the hardest piece to change and the most important piece to connect.
Enquiries, applications, visits, assessments, offers, re-enrolment and alumni relationships. For international schools with year-round intake and globally mobile families, this is often where spreadsheets pile up first.
For more information, visit OpenApply.
Planning, assignments, assessment, gradebooks and reporting, plus communication with students and parents about learning. Teachers spend more of their day in this system than any other, so adoption matters as much as features.
For more information on teaching and learning, visit ManageBac+.
Mapping what’s taught, when and against which standards. Good curriculum software makes coverage visible across subjects and year groups, and makes accreditation and inspection far less painful.
For information on curriculum management, visit Atlas.
Activities, trips, bookings, payments, transport and the everyday messages between school and families. These tools touch parents more than any others, so they shape how families experience your school.
For information on how you can manage trips, bookings, events, and more, visit SchoolsBuddy.
Turning everything above into answers your leadership team can act on. In a well-connected stack, this comes almost for free. In a fragmented one, it’s somebody’s Friday afternoon.
Edu Intelligence securely sees the information a school collects, connects the dots, and answers staff’s questions in plain English. Find out more.
Many school software decisions start with the MIS, and for good reason. It’s the system of record. If it’s wrong, everything downstream is wrong.
But an MIS was never built to run admissions, map a curriculum or tell a parent the bus is running late. Treating it as the whole stack tends to end one of two ways. Either the school stretches it to do jobs it does badly, or tools get bolted on around it with no plan for how data moves between them.
A more useful way to think about it: your MIS is one piece of the stack. The question isn’t only “which MIS?” It’s “how will everything else connect to it?”
An MIS (management information system) and an SIS (student information system) do essentially the same job. Both hold the core student record. MIS is the more common term in the UK; SIS is more common in international and North American schools.
An LMS (learning management system) handles teaching and learning: planning, assignments, assessment and reporting. Most schools run both, and the connection between them is one of the most important in the whole stack.
When you’re assessing any school software against your MIS, look for four things:
Be careful with the word “integration”. It means different things to different providers. A two-way, real-time sync is not the same as a nightly export that someone checks by hand when it fails. Ask whether the connection is native or via middleware, which way data flows, how often it syncs and who fixes it when it breaks. Ourprocurement checklist for school leaders has the full set of integration questions.
Every school software decision eventually comes back to the same question. Do you buy the best specialist tool for each job, or one platform that covers most of them?
| Best-of-breed | Integrated suite | |
|---|---|---|
| What it means | The strongest specialist tool for each job, from different providers | One provider covers most jobs in a single platform |
| Strengths | Depth in each area. You can replace one tool without touching the rest. | One login, one data set, one contract, one support team |
| Risks | Data lives in silos. Staff re-enter the same information. Integrations break. | Some modules are weaker than specialist rivals. Switching later means switching everything. |
Best-of-breed usually wins on features. The cost shows up later, at the joins. Each new tool solves one problem and subtly creates a data handover. Over time, those handovers become workarounds, and the workarounds become somebody’s job. We call thisoperational debt, and it rarely appears on any budget line.
A suite solves the data problem by keeping everything in one place. The cost here is lock-in. If one module is weak, you live with it, because replacing it means replacing everything. And when the provider’s priorities drift away from yours, you have very little room to move.
The choice isn’t as binary as it looks. The strongest setups we see combine both ideas: specialist tools that each do one job in depth, designed to share data with each other and with the systems a school already runs.
That approach lets you start with the problem costing you the most, keep the systems that already work, and add more over time without starting again. When you’re evaluating providers, ask directly: can we buy one product on its own, and what happens to our data if we add or remove others later?
You don’t need a formal audit to get a rough answer. Try these three checks.
Count the systems. List every tool that holds school data, including the spreadsheets and shared inboxes. If the list surprises you, your stack has grown beyond what anyone designed.
Follow one piece of data. Take a new student from first enquiry to first day. How many times is their name typed? Every retype is a chance for error and a cost in staff time.
Ask a leadership question. Pick something your head should be able to see in minutes, such as applications by year group or reporting completion by department. If the answer means emailing three people and waiting until Friday, your data isn’t connected.
If two of these land, you’re not alone. Most schools recognise the problem long before they act on it. We’ve written aboutwhy international schools switch software providers, and why most wait too long.
Just like choosing a carpet for your home office, feature lists start to look the same after the third demo (or sample, in the carpet’s case). The schools that choose well tend to do five things differently.
Agree three to five things the new software must change, in language specific enough to measure. Then name one person who owns the decision. A committee can inform it, but it can’t own it.
Know which systems the new tool must connect to, and how data needs to move between them. This is the step most schools skip, and it’s the one that decides whether the new tool reduces work or adds to it.
Demos run on clean data and rehearsed workflows. Ask for a sandbox, load a sample of your own data, and let the people who’ll use the system most try it for themselves.
Two products with near-identical features can produce very different outcomes depending on who runs the rollout. Ask for a named implementation lead and a sample project plan before you sign. Here’swhat good implementation support looks like, and the red flags to watch for.
Find out how you’d export your data, in what format and at what cost. A provider that makes leaving easy is usually confident you won’t want to.
For the complete set of questions, use ourprocurement checklist for school leaders evaluating new software.
Two worries stop most schools from acting: how long a switch will take, and when to do it.
On time, the answer is usually shorter than expected. For most international and independent schools, active implementation runs 30 to 90 days, or three to five months including the planning before you choose a provider. Clean data and a named project lead push you towards the shorter end. We break it down phase by phase inhow long it actually takes to switch school software.
On timing, there’s rarely a perfect window, but there are sensible ones, and they depend on what you’re switching. Admissions systems are best changed before the next cycle opens. MIS and curriculum tools usually go live at the start of the academic year. Operations tools, like activities and transport, can often switch at the start of any term. Here’s how to weigh it up:switching software mid-year vs between cycles.
The bigger risk is the conversation that keeps getting deferred. If you’ve discussed switching more than twice in the past year, timing probably isn’t the real blocker.
We’ve spent 20 years building education technology for international and independent schools. Today, our software supports more than 10,000 schools in 155 countries.
We build specialist products, and we build them to work together. Each one does one job in depth and can be bought on its own. Many schools run them alongside their existing MIS, including iSAMS, PowerSchool and Veracross. Others use several together as their core platform.
Not sure where to start? Ourschool software page helps you match the problem costing you the most time to the right product.
What’s the difference between EdTech and school management software? EdTech is the broad term for any technology used in education, including classroom tools. School management software is the part of EdTech that runs the school itself: admissions, records, reporting, payments, transport and communication.
Do we need an MIS if we already have a learning platform? Most schools need both a system of record and a teaching and learning platform. Some platforms cover parts of both jobs, so the right answer depends on your size, curriculum and existing systems.
Can we replace school software in stages? Yes, and it’s often the safer route. Start with the system causing the most pain, and plan how it will connect to everything else before you add the next piece.
Who should own a school software decision? One named person, usually an operations director, bursar or deputy head, with input from the people who’ll use the system every day. A committee can advise, but a single owner keeps the project moving.
How do we get staff to use new school software? Role-based training, delivered in waves, works far better than one session for everyone. Start with administrators and a pilot group, then bring in wider teams with training focused on the tasks they actually do.
If you’re weighing up a change, ourSwitching hub brings everything in this guide together in more depth, including a five-phase framework for running the switch.
Primary CTA:Download the Free Switching Guide
Secondary CTA:Talk to Us
