A school buys a good internet package, installs two home routers, and declares itself WiFi-enabled. Then 300 students and 40 teachers connect, the network collapses, and everyone concludes "WiFi doesn't work in schools." The problem was never WiFi. It was planning: school networks need to be designed, not improvised.
This guide walks through school WiFi infrastructure planning for a school with 500+ devices — the bandwidth maths, the coverage design, the filtering and safety requirements, and realistic costs in Pakistan. Whether you hire a vendor or do it in-house, this is the checklist to hold them to.
Why School WiFi Usually Fails
School WiFi fails for four predictable reasons. Under-provisioned bandwidth: the package was sized for the office, not for hundreds of devices. Wrong hardware: home routers are built for 10-20 devices in a small space, not 50 devices per classroom through concrete walls. No segmentation: students, teachers, guests, and office systems share one network, so one student's video stream slows the fee system. No management: nobody owns the network, so passwords leak, settings drift, and problems get fixed by restarting the router.
The fix for all four is the same: treat school WiFi as infrastructure, like electricity — planned, budgeted, and maintained. A school would not wire a building with extension cords; it should not network one with home routers.
Bandwidth Math: How Much Do You Really Need?
Bandwidth planning starts with concurrent users, not total students. A school of 800 students might have 300 devices online at peak (a few classes using devices, teachers, office, plus phones). Next, estimate per-device need by activity: browsing and school software need 1-2 Mbps per device; standard video needs 3-5 Mbps; HD video or video conferencing needs 5-8 Mbps.
A practical formula: peak concurrent devices × 2 Mbps = baseline bandwidth, then add headroom for video-heavy periods. For 300 concurrent devices, that is 600 Mbps baseline — which is why serious school networks use fibre (100-500 Mbps packages are now available in most Pakistani cities) rather than DSL. If your budget cannot reach the full number, plan for it in stages: prioritise classrooms and the office on the fast connection, and use scheduling (only certain classes online at once) to manage demand in the meantime.
Two more bandwidth decisions matter. Upload matters too: if teachers upload video lessons or the school runs video classes, a package with symmetric or high upload speed is essential — many cheap packages offer fast download but crawl on upload. Redundancy matters: a single connection means a single point of failure on exam-result day. A backup connection (a second ISP, or even a 4G/5G failover device) costs little and saves the school on the worst possible day.
Coverage Design: Access Points, Not Routers
The core hardware of a school network is the access point (AP) — a device whose only job is providing WiFi to an area. A realistic rule: one business-grade AP per classroom (or per two small adjacent rooms), mounted on the ceiling, wired back to a central switch with ethernet cable. Ceiling mounting matters: WiFi signals spread downward and outward, and a router sitting on a desk behind a cupboard reaches a fraction of the room.
For a 20-classroom school, budget roughly 20-25 APs plus switches and cabling — this is the single biggest hardware cost, and the one schools most often underestimate. Prioritise in stages if needed: office and staff room first, then computer lab and library, then classrooms in batches. Concrete walls, metal roofs, and multi-storey buildings all reduce range — a proper site survey (walking the building with a signal-measuring app) beats guessing.
Segment the network into at least three separate networks (VLANs/SSIDs): Staff (teachers and admin, full access), Students (filtered, limited bandwidth per device), and Office/Systems (fee system, CCTV, biometric devices — isolated from student traffic). Segmentation is a security measure and a performance measure: a student's download cannot slow the office's fee system if they are on separate networks. Use a proper router/firewall device to manage this — not a home router's guest mode.
Planning Checklist
Filtering, Safety, and Student Protection
A school network without content filtering is a safeguarding failure. At minimum, the student network must block adult content, gambling, and known malware sites, and the school must be able to see which device accessed what (logs, not spying on content). Business-grade routers and cloud filtering services (many offer free or low-cost education tiers) provide this. DNS-based filtering — pointing the student network at a filtered DNS service — is the simplest effective option for schools on a budget.
Filtering is a complement to, not a replacement for, supervision and a clear acceptable-use policy. Publish the policy: devices are for learning, the school monitors network use, and misuse has consequences. Students should know the network is filtered and why. Parents should know too — it is a reassurance point at admission. For the broader picture of keeping students safe online, pair network filtering with classroom supervision and digital-citizenship teaching, not with the illusion that a filter alone solves the problem.
Realistic Costs for Pakistani Schools
Costs vary by city and building, but realistic 2026 ranges for a 20-classroom school: internet (fibre 100-300 Mbps) Rs. 8,000-25,000/month plus a backup link Rs. 3,000-6,000/month; access points Rs. 15,000-35,000 each (business-grade), so Rs. 300,000-700,000 for 20 APs; switches, cabling, and installation Rs. 150,000-400,000; router/firewall Rs. 50,000-150,000. Total upfront: roughly Rs. 500,000-1,250,000, plus Rs. 15,000-35,000/month in connectivity.
That is real money — so phase it. Year 1: office + staff room + computer lab + library, with the backbone cabling that future phases will use. Year 2: classrooms in batches. Phasing works because the expensive part done early (backbone cabling, firewall, fibre) serves every later phase. And weigh the cost against the alternative: a school that cannot run digital attendance, online payments, or digital homework because the network fails is paying for software it cannot use.
Maintenance and Everyday Management
A school network needs an owner. Assign one staff member (or a part-time vendor) responsibility for: password changes each term, firmware updates, checking that APs are online, reviewing filtering logs monthly, and keeping a one-page network map (where APs are, what the passwords are, who the ISP contact is). Without an owner, networks decay — passwords leak to students, settings get "fixed" by whoever is nearby, and the network slowly stops working.
Day-to-day rules that prevent most problems: change the student WiFi password every term; never give students the staff network password; keep the office/systems network physically and logically separate; and test the network under load before any high-stakes day (result day, online exam, admission rush). Good school WiFi is not a purchase — it is a plan, a budget line, and a named owner. Get those three right and the technology largely takes care of itself.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app, that can answer questions, explain ideas in simple words, and help you draft plans or checklists. A school admin can ask Muse to estimate bandwidth for a given number of students or to draft an acceptable-use policy for student WiFi.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.