IT support for schools is the work that keeps student devices, accounts, classroom technology, the network, and content filtering running. It also runs the request queue that ties them together. In 78% of US districts under 1,750 students, IT staffing is one to three full-time-equivalent positions.
Key takeaways
A helpdesk and PSA (professional services automation) a small IT team can run alone. No contract. No implementation project. No dedicated admin.
School IT support covers six areas, and in a small district the same people own all of them. Name them plainly, then decide which get scheduled time and which get handled as tickets.
| Area | What it includes | Busiest weeks |
|---|---|---|
| Student and staff devices | Chromebooks, laptops, and tablets: enrollment, repairs, loaners, refresh, and disposal | First two weeks of school, summer collection |
| Accounts and identity | Google Workspace or Microsoft 365 accounts, passwords, rostering, and multi-factor sign-in for staff | August onboarding, semester changes |
| Classroom technology | Interactive displays, projectors, document cameras, audio, and printers | All year, worst at the start of each term |
| Network and Wi-Fi | Internet connection, switches, wireless access points, and firewall | Testing windows and the first day back |
| Filtering and online safety | Content filter, monitoring of minors' online activity, and the internet safety policy | Start of year, policy reviews |
| Student data and apps | Which apps receive student data, vendor agreements, and access to student records | Before each school year |
The first four areas generate the tickets. The last two carry federal rules and student records, so give them calendar time: no teacher files a ticket asking for a vendor review.
CoSN's 2026 survey of 607 US district technology leaders shows why.
Devices come first: in a 1:1 district, they grow with enrollment, not with staff. On r/k12sysadmin, one solo technician manages "about 800 Chromebooks and 200 windows laptops"; another runs "a fleet or 1,400 devices" and does all the repairs.
Security is second. Cybersecurity ranks as the No. 1 priority for district technology leaders. Besides the staffing gap above, a separate 65% name the lack of a dedicated budget as a barrier. CISA's K-12 guidance starts with a short list of steps, multi-factor authentication first. A small team can cover a minimum like this one:
| Action | Owner | When |
|---|---|---|
| Multi-factor sign-in for administrators, then all staff | IT lead | Administrators now; staff before the school year |
| Back up key systems and test a restore | IT lead or provider | Backups on a schedule; one restore test per term |
| Close accounts of staff who leave | IT, notified by HR | On the last working day |
| One route to report a security incident, in a written plan | IT drafts; superintendent or principal approves | Published each August, rehearsed once a year |
CISA recommends testing partial and full restores regularly and keeping a written incident response plan, approved by the most senior leader and exercised regularly.
Money is third: in the CoSN survey, 38% of districts expect reduced funding for devices, which can stretch refresh cycles.
Four federal rules shape a US school IT team's daily decisions. Below is what the official sources state; your counsel decides how they apply.
The Family Educational Rights and Privacy Act gives parents rights to access their children's education records, seek corrections, and control some disclosure of identifying information from them. It applies to schools and agencies that receive funds under Department of Education programs.
For vendors, the key test has three parts. A contractor can count as a "school official" if it does work staff would otherwise do and is "under the direct control" of the school over the records. It must also follow FERPA's limits on using and redisclosing them.
Access also needs a "legitimate educational interest" and must be limited to the records that interest covers. The school's annual FERPA notice must state its criteria for both. So app approvals and vendor agreements belong in the IT queue.
The Children's Online Privacy Protection Act rule covers online services directed to children under 13 that collect their personal information. It also covers general-audience services that know they collect it from children under 13.
The FTC's FAQ, written in July 2020, says a school can consent on parents' behalf. It may do so only "where an operator collects personal information from students for the use and benefit of the school, and for no other commercial purpose". The FTC's 2025 amendments did not adopt the proposed changes for edtech companies in schools. The amended rule took effect June 23, 2025, with most compliance required by April 22, 2026.
To receive E-Rate discounts on Category One internet access or any Category Two service, schools must certify an internet safety policy with filtering; telecommunications-only applicants are exempt. The filter must block pictures that are obscene, child pornography, or harmful to minors (when accessed by minors). The policy must also cover monitoring minors' online activity and teaching safe online behavior. The FCC notes that CIPA does not require schools to track or retain browsing history.
E-Rate is a discount, not full funding: 20 to 90 percent based on poverty level, higher for some rural schools, and the school pays the rest. Category One covers data transmission and internet access. Category Two covers internal connections, managed internal broadband, and basic maintenance, with discounts capped at 85 percent for schools.
Category Two also has a five-year, pre-discount budget: for FY2026–2030, $201.57 per student, calculated at district level, or $30,175 per school if higher. Districts with 10 or fewer schools may instead calculate each school separately and add them up. Schools of 50, 100, and 200 students then get $100,664. Since September 2025, school bus Wi-Fi and off-premises hotspots are ineligible.
Schools staff IT support in-house, through an outside managed service provider (MSP), or as a hybrid. CoSN lists outsourcing among the factors that change how many IT staff a district needs.
| Model | Daily on-site presence | Cover when the technician is out | Network and security skills | Security incidents | Escalation and handoff |
|---|---|---|---|---|---|
| In-house | On a schedule, with the staff you have | None unless you arrange it | Only what your staff know | As your district agrees, after hours included | Internal; no handoff |
| Outsourced (MSP) | As contracted: resident technician, scheduled visits, or remote | The provider's team | The provider's specialists | As the contract defines | Write who owns records and response times into the contract |
| Hybrid | Your staff daily; provider as needed | The provider covers named gaps | Provider covers network or security | Named staff owner calls the provider | One staff escalation owner; shared ticketing or full context with each handoff |
The rule of thumb: keep your own team when its coverage is enough, add an MSP for missing capacity, and use a hybrid for specific gaps.
One r/k12sysadmin member ran a school's IT as the "sole SysAdmin/Helpdesk/coordinator", with a local MSP handling the firewall and networking. Budget cuts later handed the role to the MSP, so put handoff rules in writing.
Give every request an owner and a status, so nothing depends on remembering a conversation from second period.
One technician on r/k12sysadmin covers "5 buildings, 1500 students, and 250 staff members by myself" and doesn't take walk-up requests. The sole IT person at a 400-student charter school remembers "people inturrupting me in the hall and my office, just walking up to me hoping I'd drop everything".
Pick one support email address and one portal link, and publish both in the staff handbook and the start-of-year email. Forward the address into the helpdesk so every email becomes a ticket with a number and a timestamp.
Use categories that match the areas above: device, account, classroom technology, network, filtering, and new app or data request. Add the building and room, because "the projector is out" means nothing without them.
For example: a building offline comes first, a class that cannot teach right now next, one student without a device after that, and anything that can wait a day last. A suspected security incident, such as a phishing click or a compromised account, skips the queue and goes straight to the named incident owner. Our guide to ticket priority levels has a grid to copy, and our service level agreement template shows how to attach a response time to each level.
Common mistake: letting the requester set the priority with no definitions. Every ticket becomes urgent.
Pull last year's ten most common requests, such as password resets or printer setup. Write a short article for each and link it in your reply, so the next teacher can solve it before filing. The knowledge base guide shows how to structure them.
When a ticket names an asset tag or serial number, link it to the device record. After a year you can see which models or buildings generate the repairs: evidence for the refresh budget.
Expect resistance. The same solo technician says "30% of the staff did not like me much the first year". Two habits from that thread are worth copying. Put the ticket link in your email signature, and show the ticket queue on a screen in the IT office. Show ticket numbers and status only, never student names. More habits: helpdesk best practices.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Collect devices when students leave, repair and refresh over the summer, and plan it all in May.
Publish collection dates per building, decide which grades keep devices, and print check-in sheets from the inventory.
Check in every device by asset tag, note damage on its record, and open repair tickets in one batch. Missing devices go to the front office before families leave.
Retire devices near the end of update support. Order replacements by the date your supplier's lead time and your district's purchasing calendar require, so they arrive in time to enroll and tag.
Create accounts for new staff and students, test every classroom display, and update the how-to articles.
Keep a loaner pool at each building, pause projects, and review the queue daily.
Google says ChromeOS devices receive 10 years of updates from the platform release date. Devices from before 2021 that get extended updates may lose some features, and after the final update, technical support ends. Google lists each model's end date on the same page, so record it on each device record. Half of districts replace internet-only student laptops in four years or less.
Collecting every device is a choice. One r/k12sysadmin member's district later switched to take-home devices. Before that, collecting and reissuing "was at least 3 days at the end of the year and 3 days at the start- both horrible times to do it".
Another district collects all devices over two days with four people, which "allows us to clean/repair everything that doesn't get reported as broken during the school year". Decide in May, tell families, then put a number on the labor.
Estimate summer check-in hours
devices × minutes per device ÷ 60, rounded up. Repairs are extra. Your numbers stay in the browser.
Example: 900 devices at 4 minutes each is 60 hours, a week and a half of one technician's 40-hour weeks.
Plan next year's spending before the district's budget deadline, so the summer refresh runs on purchases already approved. List each line and agree with your business office who approves it:
Most mistakes are right work in the wrong place.
Test these during a trial with an anonymized device sample and typical teacher requests, not real student records.
To compare products, see our IT helpdesk software comparison and, for device tracking, IT asset management software.
How this works in SherpaDesk
You get a helpdesk and PSA a small IT team can run alone. You forward your support address to a SherpaDesk dropbox, and teachers' emails arrive as tickets; with Google Workspace, a public Google Group does the forwarding. Staff come in from your Google domain, filtered by organizational unit, and sign in with Google.
Asset Manager is part of the High Camp plan. There, Google Device Manager syncs Chromebooks into Asset Manager with their serial numbers, so a ticket can carry the device it is about. Loaner and Daily Loaner statuses keep spares apart from 1:1 devices, and an Asset Auditor can verify each building or mark devices missing.
For K-12 schools and districts, pricing is based on student enrollment. Ask our sales team at sales@sherpadesk.com for a quote for your district.
Helpdesk Software For Education →
Who this isn't for
Districts that must install their helpdesk on their own servers: SherpaDesk runs only in the cloud. Teams that want device management (remote lock, wipe, app pushes) inside the helpdesk: we don't build endpoint management, so that stays in your device console. Buyers who need a SOC 2 report or an ISO 27001 certificate on file from the helpdesk vendor: we don't document either, so ask before you buy.
Technical support in a school is the help staff and students get when a device, account, classroom display, the network, or an app stops working. It also covers planned work: inventory, summer repairs, filtering, and app reviews. In 78% of US districts under 1,750 students, IT staffing is one to three full-time-equivalent positions.
There is no reliable ratio. CoSN found that 78% of US districts under 1,750 students have one to three full-time-equivalent IT positions. It also warns that device variety, outsourcing, and automation make comparisons between districts difficult. Test your own queue instead: weekly tickets, first-reply time, and summer hours.
Outsource the work your staff can't cover well, such as network, firewall, or security monitoring, rather than the whole job by default. Name one staff member who owns escalations to the provider, and keep the inventory, accounts, and ticket history in a system the school owns.
E-Rate discounts US schools' internet access and data transmission (Category One) by 20 to 90 percent, and the internal network (Category Two) by 20 to 85 percent. The school pays the rest. Category Two has a five-year, pre-discount budget: $201.57 per student for FY2026–2030, or $30,175 per school if higher. Districts with 10 or fewer schools may sum per-school budgets.
Make the ticket faster than the hallway. Give staff one support address, answer tickets quickly in the first month so the habit pays off, and reply to emails, texts, and hallway requests with the ticket link. Expect pushback in the first year, and apply the rule to everyone, administrators included.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.