IT support for a school has to handle three things an office never does: hundreds of devices connecting inside one lesson change, pupil data that raises the cost of a mistake, and exam windows with no second attempt. Listonics covers the infrastructure those depend on, with a written freeze during assessment periods.
What does a school need from an IT provider that an office does not?
A school runs to a timetable, not to working hours. The network's hardest moment is the first ninety seconds of a lesson change, repeated eight times a day, and equipment sized for an office of the same headcount fails there while looking healthy from the comms room.
Three requirements follow, and a provider who has only done offices will usually miss all three: capacity planned per classroom rather than coverage planned per floor, network separation strict enough that a pupil device cannot reach staff systems at all, and change control tied to the academic calendar rather than to convenience.
- Wi-Fi capacity for a whole class connecting at once, not signal strength in a corridor.
- Pupil, staff, guest, building-systems and AV traffic separated at network level.
- A written freeze on changes during exam and assessment windows.
- Support hours that cover term-time mornings, open days and parents' evenings.
- Documentation you own, so the next inspection or provider starts from fact.
How should a campus network be built for classroom density?
The usual finding on a campus is not missing Wi-Fi but too few access points working too hard. A radio shares a finite amount of airtime, and thirty pupils on tablets is a far heavier demand than thirty adults typing, so the answer is more access points at lower power rather than fewer powerful ones. The Wi-Fi Alliance sets out what current-generation certification adds for exactly this density.
We survey the spaces as they are used: classrooms, but also sports halls, science labs with fixed metal equipment, and libraries that fill with a whole year group. Each access point needs a cable and power from a switch, so the structured cabling and switch capacity are designed first and the wireless plan follows. Our Wi-Fi installation page covers the survey itself.
How is pupil data kept separated and access controlled?
Safeguarding notes, medical information and assessment data are not ordinary business records, and access to them should be narrow by default. We set up role-based access so a teacher sees their own classes, cover staff get access that expires, and administrative roles are separated from safeguarding ones.
Two mechanical controls matter more than any policy: multi-factor authentication on every staff account, and a leaver process that actually runs each term in a sector with high seasonal turnover. Both are part of a managed agreement rather than a project, and the security baseline is on our cybersecurity for small business page.
- Role-based access, with expiring accounts for cover and temporary staff.
- Multi-factor authentication on every staff account, without exceptions.
- Termly access review, with a written record of who holds what.
- Pupil devices unable to reach staff, finance or safeguarding systems.
What happens during exam and assessment windows?
Digital assessment makes the network part of the exam room, so we treat it that way. Before each window we agree a written freeze: no firmware updates, no configuration changes, no cabling work, and automatic updates on pupil devices suspended in advance rather than hoped about.
During the window the assessment platform's traffic is prioritised, the guest network is throttled or closed, and a fallback is agreed in advance: who decides if connectivity fails mid-paper, and whether the firewall switches automatically to a second internet path. An hour of planning beforehand is the difference between an incident and a sitting.
What does each part of a school campus need?
Different spaces on one campus have genuinely different requirements, and treating them all as classrooms is the most common design shortcut.
| Space | Main requirement | Usual mistake |
|---|---|---|
| Classrooms | One access point per room, cabled AV outlet | One access point covering three rooms |
| Science and IT labs | Dense cabling, fixed machines, segmented devices | Surveying the room empty of equipment |
| Sports halls | Long-range coverage, mounted out of ball strike | Office-grade mounting at head height |
| Library and study areas | Capacity for a whole year group at once | Planned on floor area, not headcount |
| Reception and admin | Separated from pupil traffic, reliable print and phone | Sharing the staff network with guests |
| Comms room | Cooling, UPS, lockable, room to grow | A cupboard with no ventilation |
How are one-to-one device programmes supported?
A device programme turns a school into an IT department, and the management is the part usually left out of the budget rather than the hardware. We set up central control so applications, settings and web filtering are pushed without touching each device, filtering follows the device home rather than stopping at the gate, and a lost or stolen unit can be locked or wiped. Microsoft's school-specific tooling for this is documented in Intune for Education.
We also plan for breakage, which schools consistently underestimate: a swap pool sized for real rates, a repair route, and charging and storage designed per classroom before the first delivery. Our guide to school and campus IT covers the wider picture.
Working around a school term, not through it
We are an office IT company, and it is worth being exact about which half of a school's technology that covers. Ours is the infrastructure layer: structured cabling and comms rooms, switching sized for access point density, campus Wi-Fi designed per room, network segmentation, firewalls and filtering, Microsoft 365 and identity, backup with tested restores, and managed support with written response times. Engineers attend on site across the UAE and the support line runs 24/7.
The teaching layer is not ours and we would not claim it. Student information systems, assessment platforms and curriculum software belong to specialist vendors; our job is to make them work reliably and to coordinate with those vendors rather than replace them. Private schools in Dubai are regulated by the Knowledge and Human Development Authority and Abu Dhabi schools by ADEK; requirements differ by emirate and curriculum, and no IT provider can make a school compliant. What we can do is produce the evidence that a control exists and works.
We have not published school references yet, so ask us for one directly rather than take this page's word for it. A free school IT assessment covers the network, Wi-Fi density, segmentation, access review and backup, and you keep the findings either way.
Frequently asked questions
No provider can, and any who says so is overselling. Compliance judgements belong to the regulator and your own adviser. What we do is implement and evidence the controls: who has access to pupil data, when it was last reviewed, when leavers were removed, what filtering applies, and when a backup was last restored.
Plan roughly one per classroom rather than one covering several rooms. The constraint is how many devices share the airtime, not whether the signal reaches. Halls, labs and libraries behave differently again and are surveyed separately, with the equipment and furniture in place.
Yes, and we ask for it in writing. Before each assessment window we agree a freeze on firmware updates, configuration changes and cabling work, suspend automatic updates on pupil devices, prioritise the assessment platform and agree a fallback if connectivity fails mid-paper.
Not as the vendor. Those are specialist platforms and we do not claim to replace them. We make the infrastructure they run on reliable, configure the identity and access they depend on, and coordinate with the vendor when an issue crosses the boundary between the platform and the network.
Yes. Nurseries are smaller but carry the same duty of care over children's records. Training institutes have adults bringing their own devices, which shifts the work from managing devices to managing identity and access. The infrastructure principles are the same in both.
We size, source and set up the fleet with central management, filtering that applies off-site, and remote lock and wipe. We also plan the swap pool and repair route, because a programme without spares leaves a pupil without a device for weeks. The devices themselves are quoted as part of a fixed-scope project.
Written by Srinivasan Ramachandran, Founder, Listonics · Last reviewed September 27, 2026