Education IT: hundreds logging in at once
An office network handles people arriving over an hour. A school handles four hundred devices joining in the same four minutes, five times a day, and then nothing much until the next bell.
School networks fail on concurrency, not on bandwidth. Hundreds of devices authenticating in the same few minutes is a very different load from the same devices browsing all morning, and capacity has to be planned for the bell rather than the average.
Design for device density per room instead of coverage per building. A lecture hall with two hundred seats needs a different access point layout from a corridor of the same floor area.
Freeze changes during exam periods, plan the major work into the holidays, and accept that the calendar rather than the technology sets the rhythm.
The problem is concurrency, not bandwidth
Schools regularly buy more internet capacity to solve a problem that has nothing to do with internet capacity. The line is not saturated at nine in the morning; the access points are handling four hundred simultaneous authentication attempts, and the authentication path is the bottleneck.
The symptoms give it away: everything is slow for four minutes and then fine, it happens at the start of every period, and a speed test run at ten shows the connection is perfectly healthy. That is a concurrency problem and adding bandwidth does not touch it.
Design for density per room
| Space | What matters | Approach |
|---|---|---|
| Classroom, 30 seats | Every device active at the same moment | One access point per room, not per two rooms |
| Lecture hall, 200 seats | Very high density in a small area | Multiple units with reduced power and narrow channels |
| Corridors and common areas | Roaming while walking, low throughput | Coverage-driven, fewer units |
| Exam rooms | Reliability above all, sometimes restricted access | Wired where possible, separate segment |
Getting this wrong in a lecture hall is the most common design fault we correct. A single high-power access point covering two hundred seats produces a perfect heatmap and an unusable network.
Measure with the room full
Two hundred bodies absorb a considerable amount of signal. A hall that measures beautifully on a Wednesday afternoon in the holidays behaves differently with a class in it, which is why we measure under realistic conditions with Ekahau rather than modelling from a floor plan.
The method is described under Wi-Fi analysis. In education it matters more than in most sectors because the density is higher and the failure is more public.
Accounts move in September
Every school has an annual cycle no office has: a large intake, a large leaving group, and every class group changing at once. If account creation and removal are manual, September costs weeks and the leavers keep access far longer than they should.
Automating that from the student information system is the highest-value integration in most school estates. It removes the September backlog and it closes the access gap that every audit finds.
The calendar sets the rhythm
In retail we avoid December. In education the constraints are firmer and there are more of them: no changes in exam weeks, no changes in the first fortnight of the school year, and major work in the summer because that is the only genuine window.
That compresses a great deal of work into a few weeks, which means it has to be planned in the spring rather than agreed in June. Schools that plan the summer work in April get it done; schools that decide in June get half of it.
Shared and personal devices side by side
Most schools run both: managed devices in classrooms and personal devices students bring. Those need different treatment on the same network, with the managed estate on a segment that can reach internal resources and personal devices on one that reaches the internet and nothing else.
Keeping that boundary clean is what stops a student device from becoming a route into the administration systems. It is ordinary segmentation, and it is skipped surprisingly often.
Questions we get about this
What school IT coordinators ask us.
Why is our school Wi-Fi slow only at the start of a lesson?
Because hundreds of devices authenticate in the same few minutes. That is a concurrency problem in the access points and the authentication path, not a bandwidth problem, which is why a speed test taken later shows a healthy line. Buying more internet capacity will not change it.
How many access points does a lecture hall need?
More than the coverage map suggests, at lower power each. A single high-power unit covering two hundred seats produces good coverage and poor capacity. The number depends on the seat count and the device mix, which is why we measure rather than estimate.
When can major IT work be done in a school?
In practice, the summer holiday, with smaller work in other holidays. Nothing during exam weeks and nothing in the first fortnight of the school year. That means summer work has to be planned in the spring rather than decided in June.
How do we handle student devices safely?
On a separate segment that reaches the internet and nothing internal. Managed classroom devices sit on their own segment with access to school resources. Keeping that boundary intact is what prevents a personal device becoming a route into the administration systems.
Where this lands in our work
The services behind this.
Want this looked at for your own sites?
Half an hour on a call is usually enough to tell you whether we are the right party for it, and we will say so if we are not.