Your School Has No IT Person. Does That Rule Out a Platform?

"We're a small private school. Two hundred students, ten teachers, one administrator, and a bookkeeper on contract. We don't have an IT person and we never will — there's no budget for one. We'd love our own platform, but who would actually run it?"

That's the objection we hear most often from heads of private schools, independent language centres, and small colleges.

Let's start with the uncomfortable part: the objection is fair. A learning platform genuinely does need someone who owns it. Schools that buy a system and assume the teachers will figure it out on their own tend to drift quietly back to group chats and shared drives within six months.

But there's a substitution buried in that reasoning. From the correct premise "we need someone accountable," people draw the incorrect conclusion "we need an IT specialist on staff." Those are two different things, and this entire article is about where the line between them actually falls.

Who runs the learning platform in a private school with no IT specialist on staff?

The head of studies or the academic coordinator runs it — the person already accountable for teaching, not for technology. In schools with 100 to 300 students, the platform administrator role almost always lands with someone on the academic side: they create the groups, assign teachers, and make sure a new student has access on day one. That is administrative work, not engineering, and it doesn't require a single line of code.

An IT specialist is needed where the system is self-hosted, updated, patched, and extended in-house. That's precisely the part a school stops owning when it takes the platform together with the team that runs it.

Here's how responsibility actually splits in a working school — read this list next to your own staff roster and see whose name lands on each line:

• The academic side decides which subjects and groups exist and who teaches what. That's a pedagogical decision; you can't hand it to a vendor, and you shouldn't want to.
• The administrator enrols students and issues access. If the system is built sensibly, that's a few minutes per group, not a job description.
• The teacher uploads materials and marks work inside their own course, and never has to step outside it.
• The platform team keeps the server, the updates, the backups, the integrations, and everything that breaks for reasons that have nothing to do with your school.

The first three lines are covered by people already on your payroll. The fourth — the one supposedly requiring an in-house technician — shouldn't appear on your payroll at all.

How much admin time does a learning platform take in a school of 100 to 300 students?

Less than the school is already spending without one. That sounds counterintuitive, so let's run simple numbers. Take a school with 150 students and eight teachers. Say each teacher spends just 15 minutes a week sending materials through chats, fishing homework out of direct messages, and reconciling who submitted what. That's two hours a week across the school. Over an academic year, it adds up to nearly two full working weeks spent forwarding files.

And that's only the teachers. On top of it sits the administrator's September, when a new intake has to be sorted into groups, and the head of studies' end of term, when attendance and grades get pulled together from eight separate sources — one per teacher.

It's worth looking at what administration costs if you buy it on the open market as a standalone service. On the English-speaking market there is an entire service category called "LMS administration as a service," and according to the public price lists of those providers, an external platform administrator starts at roughly $75 an hour — precisely because a small organisation can't justify that person as a permanent hire. For comparison, our own technical support is $1 an hour, content setup is $5 an hour, and custom development is $10 an hour. That isn't a product-to-product comparison; it's an illustration of the principle. Administration is a service you can buy by the hour, not necessarily a new line on the staff roster.

If you're comparing a managed platform with self-hosted Moodle — where the school still owns the server, updates, and security — there's a dedicated EduSystem vs Moodle comparison.

There's a second reason this matters for independent schools specifically. Your competition for a parent's attention isn't a bigger school with a bigger IT budget — it's the perception that a small school can't run a serious learning process. Every hour your academic staff spends forwarding files is an hour not spent on the thing parents are actually paying for.

Why do learning platform rollouts in schools usually stall?

Because of the teachers, not the technology — or more precisely, because nobody worked with the teachers. Industry reviews of LMS rollouts consistently find that a significant share of projects fail to meet expectations, with estimates running as high as seven in ten, and the factor they name as decisive isn't the feature list. It's whether teachers actually started using the system.

The failure mechanics look the same almost everywhere. The school picks a platform from a feature comparison, launches it in August, runs a single all-staff training session at the start-of-year meeting — and by October half the teachers are back in the old chats, because that's faster and more familiar.

The good news is that the stall is visible within the first month. Check yourself against these signs if you're mid-rollout right now:

• Teacher training happened once, for everyone at once. Two weeks later nobody remembers where to click, and there's no one to ask.
• The old channel stayed open. As long as homework can be sent to a messenger, it will be sent to a messenger.
• Nobody migrated the existing materials. A teacher asked to upload three years of their own course from scratch simply won't start.
• There's no human being on the other end. A knowledge base and a support form are not implementation support.

Not one of those four is fixed by software. All four are fixed by who is standing next to you in the first two months.

What does the platform team take on, and what stays with the school?

The team takes the technology and the setup; the school keeps the pedagogy and the people. The split is simple: anything about what and how you teach is yours, and anything about where and on what it runs is ours.

EduSystem is a technology partner for launching online learning and a white-label LMS platform: the team personally configures a branded learning system around one specific school's process, migrates its materials, trains its administrator, and keeps running the platform after launch. EduSystem partners teach from Ukraine, Germany, and Armenia, 10+ active partners run on the platform, and the interface is available in English, Ukrainian, and Russian.

Take the list below into a conversation with any vendor and ask them to confirm it line by line — you'll see immediately where they start hedging:

• Build out your school's structure: subjects, groups, roles, access rights. You verify that it matches your real academic setup rather than the demo template.
• Migrate the existing materials. Not "provide upload instructions" — migrate. Those are different offers, and they're priced differently.
• Train one or two people on the academic side to the point where they can set up a group in September without calling support.
• Handle updates, backups, and uptime. This is the line your school should never have to think about again.

And here's what stays with you and isn't going anywhere: deciding how the programme is structured, who teaches which group, and what counts as submitted work. That's your methodology. A good vendor won't touch it, and a bad one couldn't.

A school without a building is normal now

A word specifically about private schools with no premises of their own, and about hybrid setups where some lessons happen in person and some online. A parent choosing a school like that asks exactly one question: how will I know my child is learning rather than just sitting in a video call. The answer doesn't come from a building — it comes from the environment. A schedule, visible progress through the programme, submitted work, and teacher feedback, all in one place, answer that question better than a reception desk ever did.

This matters more in some markets than others. Where families move between countries, or where a school draws students from several cities at once, the learning environment is the school as far as the parent is concerned.

Some EduSystem partners run entirely online while remaining full organisations with their own methodology and teaching teams — you can see them on the partners page. And what a teacher actually sees inside their own course is covered in the section for teachers and tutors. How an institution with several teachers brings this into one system is on the educational institutions page.

What to do next

If you've read this far and recognised your own school, the cheapest next step isn't buying — it's looking. Open the platform demo and test it against your own scenario: create one group exactly the way it's structured at your school, and see how long that took. If it isn't obvious how to map your academic setup onto the system, describe your case and we'll work through it together. We'll also tell you honestly if a platform isn't what you need yet. For a school with twenty students and one teacher, it genuinely isn't.

In short

Conclusion

The objection "we don't have an IT person" protects a school from the wrong danger. The real risk isn't that nobody can fix the server — you won't be fixing the server. The risk is that six months after launch half your teachers are back in the chats, because nobody was there to see them through. When you're choosing a platform, look past the feature list and ask a simpler question: who will be sitting with us in September?