The most expensive mistake in school technology is treating a school as a small business with a bell.
It’s an easy assumption. A school has staff, devices, a network, email, a finance system. On paper it looks like a mid-sized business with unusually short users. Providers who make that assumption write a proposal that would work perfectly at a logistics firm, and then discover, usually in week three, that almost none of the operating assumptions transfer.
The user base is nothing like a business
In a business, users are adults, employed, contractually bound, trainable, and broadly motivated to follow IT policy because their job depends on it.
In a school you have staff, but you also have hundreds of students who did not sign an acceptable use policy in any meaningful sense, have enormous amounts of time, are frequently more technically capable than the staff, and treat circumventing restrictions as a recreational activity rather than misconduct.
You also have relief teachers who have never seen your systems, walking into a classroom with fifteen seconds to get a screen working before thirty children notice the gap. Any system that requires familiarity to operate will fail in that moment, repeatedly.
The calendar is immovable
Businesses have busy periods. Schools have a calendar that does not negotiate.
Term starts on a fixed date whether your migration finished or not. There is no equivalent of “we’ll push the go-live back a fortnight”. If the network is not ready on day one of term, the failure is immediate, visible to every parent, and lands on the principal.
The flip side is that schools have something businesses would kill for: genuinely empty buildings for weeks at a time. School holidays are the single most valuable resource in education IT, and the good providers plan their entire year around them. Any proposal that schedules significant infrastructure work during term has not understood the sector.
Duty of care changes the risk calculation
A business assesses risk commercially. A school has legal obligations regarding the safety of children that sit above commercial considerations entirely.
This changes the shape of a lot of decisions. Content filtering is not an optional productivity control; it’s a safeguarding requirement. Communication systems must work during a lockdown, which means they need to work when the network is degraded and when the office is unstaffed. Data about students carries obligations that data about customers does not.
It also means “we’ll fix that next quarter” is sometimes not an available answer, in a way that has no business equivalent.
The budget is not just smaller, it’s differently shaped
School funding arrives in cycles, is frequently tied to specific purposes, and often has to be spent within a window or lost. That produces a purchasing pattern that looks irrational from outside: capital spend that appears suddenly, operating spend that is fought over for months.
A provider who understands this helps the school get capital-funded infrastructure right while the money exists, and keeps ongoing costs genuinely predictable, because an unexpected invoice in October is a much bigger problem for a school than for a business of equivalent size.
Density and simultaneity break naive network design
An office of 200 people spreads its network load across the day. A school of 800 has every device in a year level hit the same resource in the same ninety seconds because a teacher said “open the site now”.
Wireless density in a classroom is a genuinely hard engineering problem. Thirty devices in one room, brick walls, a building designed in 1974, and an access point budget calculated on square metres rather than concurrent clients. The classic failure is a network that tests perfectly during the holidays and collapses in week one.
What good actually looks like
- Design for the worst ninety seconds, not the average day.
- Assume the operator is unfamiliar. If a relief teacher cannot use it cold, it will generate tickets forever.
- Do infrastructure work in the holidays, and finish with a week of buffer before term.
- Make failure modes safe. Ask what happens to the phone system, the door access and the filtering when the internet drops.
- Document for the school, not for yourself. Staff turnover in school IT coordination roles is high.
None of this is exotic. It’s mostly the discipline of designing for the actual operating environment rather than a generic one. But it’s the difference between a school that quietly gets on with teaching and a school where technology is a running sore that everyone has learned to work around.