A practical starting point for classroom AV, account access, Wi-Fi, printing, and suspicious links. Start with the first question, narrow the cause, and know when to escalate.
Originally written as preparation in August 2026; revised September 2026. These are general troubleshooting notes, not a school’s approved operating procedure. Follow local policy for access, shared infrastructure, and incident response.
First question → likely causes → next steps → escalation
01Projector or AV dead, class starting
First question
Is there a power light? Any image at all?
Causes, in order
Check the input source, cable, and wake state before investigating the lamp or other hardware.
Ladder
Check input source → reseat or swap the cable → power-cycle, off a full 30 seconds → lamp warning light means hardware.
Override
Class in session? Restore the lesson first — spare cable, loaner, or move rooms. Fix the device after the bell. Restore teaching promptly, while following the team’s incident priorities.
02Password reset — staff
First question
Locked out, or forgot? Check the account’s lockout state and the configured policy before resetting anything.
The real job
The critical step is identity verification. Use the school’s approved process and an independently verified contact method. A familiar voice or urgent request is not enough to authorize a reset.
Pattern
Repeated lockouts on one account are usually a stale phone sync hammering old credentials, not the user.
03Password reset — student
Local policy first
Follow the school’s student account recovery policy, including who may authorize a reset and how credentials may be delivered. Use the approved secure channel and require a password change when the platform and policy support it.
04Wi-Fi dropping — the three-question fork
The fork
Just you? Just this room? Does a wired machine work?
One device, everywhere
The device. Forget and rejoin, driver, power-saver settings.
Everyone, one room
Check access-point and controller status, client load, and neighboring coverage. Coordinate a restart or configuration change with the network owner.
Everyone, everywhere
Upstream — the closet, then the ISP or vendor. This is the escalation tier.
School flavor
Compare the timing with class transitions and client counts. A congestion problem and an upstream outage can feel similar; check the controller evidence before choosing a fix.
05Printer won't print
First question
What does the printer's own screen say? It usually knows.
Ladder
Confirm the selected printer and device status, then inspect the user’s job, local queue, server queue, and driver. Coordinate shared-queue changes and preserve other users’ jobs; do not clear a server queue as a default first step.
Pattern
A recurring failure deserves a pattern check: collect the time, affected users, queue state, driver version, and device errors before rebuilding anything.
06"I clicked a suspicious link"
Tone first
Thank them. No blame, ever. The report you don't get is the expensive one.
Ladder
Record what was clicked or entered, the URL, and the time. Follow the incident process for containment and evidence preservation. If credentials were entered, promptly escalate account recovery and session revocation through the approved response workflow.
Escalate
Always, in a school. Anything touching student data or accounts goes up the incident procedure — never solo hero work.
The method line — covers everything else
"One variable at a time until it reproduces — and I write the fix down so the fifth time takes two minutes."