Most of a school helpdesk queue is the same six problems wearing different rooms. This is the triage guide I wrote before working a single school ticket — first question, likely causes in order, fix ladder, when to escalate — so the common cases run on rails and attention stays free for the genuinely weird ones.
format per ticket: first question → causes in order → ladder → escalate when
Is there a power light? Any image at all?
Wrong input source (half of all cases) → cable → sleeping unit → lamp.
Check input source → reseat or swap the cable → power-cycle, off a full 30 seconds → lamp warning light means hardware.
Class in session? Restore the lesson first — spare cable, loaner, or move rooms. Fix the device after the bell. A down classroom outranks everything.
Locked out, or forgot? Lockouts can clear themselves in fifteen minutes.
The reset is trivial; the job is identity verification — badge in person, or a reply from a known account. Never on a voice alone: the phone call that says "just reset it real quick" is the #1 social-engineering vector in a school.
Repeated lockouts on one account are usually a stale phone sync hammering old credentials, not the user.
A minor's reset routes through an adult, always. The teacher confirms the request, the temporary password goes to the teacher, and the student sets their own at first login. A temp password never goes to a student in writing.
Just you? Just this room? Does a wired machine work?
The device. Forget and rejoin, driver, power-saver settings.
The access point. PoE power-cycle, check controller status.
Upstream — the closet, then the ISP or vendor. This is the escalation tier.
The library AP carries the heaviest load. Thirty Chromebooks hitting it at the bell looks like an outage and isn't.
What does the printer's own screen say? It usually knows.
Right printer — the name is on the label → cancel and resend → clear the server-side queue (the real fix about 80% of the time) → power-cycle → reinstall the driver.
Same printer twice in a week: drain the queue and re-add it. Stop treating symptoms.
Thank them. No blame, ever. The report you don't get is the expensive one.
Disconnect from the network → find out exactly what was entered → a password means change it now, from a different, clean device, plus everywhere it's reused → note the URL and the time.
Always, in a school. Anything touching student data or accounts goes up the incident procedure — never solo hero work.
"One variable at a time until it reproduces — and I write the fix down so the fifth time takes two minutes."