911 phones

Emergency phones that
still dial out.

A 911 phone with no dial tone, a blocked path, or a wrong location label wastes time when seconds matter. SchoolCheck runs a weekly readiness check and a monthly inspection so emergency phones stay powered, reachable, and correctly identified.
Why it matters

911 phones are a campus operations problem

Emergency phones fail quietly. Handsets go missing. Lines get repurposed during a network cutover. A phone still looks fine on the wall while the test call never completes. Location labels drift after a renovation, so a dispatcher hears “by the gym” and the campus has two gyms. The people who walk past the phone every day are not the people who own the analog line or the VoIP circuit.

SchoolCheck gives those walk-past staff a weekly check: the 911 phone is powered, accessible, and ready for emergency use. The monthly inspection is where hardware, the approved line-status or test procedure, dialing instructions, the location label, and an unobstructed path get documented. That split keeps the weekly round fast and still produces a record a safety coordinator can stand behind.

911 phones sit in the same location tree as doors and AEDs, so a campus that is green on door checks but red on emergency phones is visible. Findings can go to facilities, IT, or safety depending on who actually fixes a dead line — without inventing a second app for communications hardware.

  • Phones that look mounted but have no working line
  • Missing handsets, damaged keypads, or unreadable instructions
  • Location labels that no longer match the room or building
  • Paths blocked by vending, storage, or seasonal equipment
  • IT and facilities each assuming the other tested it
Checks and inspections

Fast rounds, documented depth

Same campus, two modes. A one-question check keeps cadence. A guided inspection captures the details you need on the record.

911 phone check

Weekly · one question

“911 phone is powered, accessible, and ready for emergency use”

Default is one check per week. Use it as the accountability signal between monthly inspections and whatever line testing your telecom or VoIP provider already runs.

911 phone inspection

Monthly · guided template

A guided inspection for hardware, the approved test procedure, instructions, location labeling, and a clear path to the phone.

  1. 1. Phone, handset, and keypad are intact
  2. 2. Approved line-status or test procedure passes
  3. 3. Emergency dialing instructions are present and legible
  4. 4. Phone location label or identifier is accurate
  5. 5. Path to the phone is unobstructed
What gets recorded

The round is not the record

SchoolCheck persists important state in the district’s history first. Realtime coverage is a view on top of that — not a substitute for it.
  • Findings stay attached
    A failed check or inspection item can open a finding with an owner, so a missing pad or a propped door does not disappear into a shared inbox.
  • Photos and comments
    Attach a photo of the empty bracket or the blocked path, then keep the thread on the record until someone closes the loop.
  • Audit-ready history
    Every completion keeps who, when, where, and the template version used. Export that history when leadership, insurers, or auditors ask.
FAQ

Questions about 911 phones

How districts usually run this type — and what SchoolCheck does not claim to replace.
Related

Other assets on the same platform

First-party types share one hierarchy, one findings workflow, and one coverage view.

Put 911 phones on the record.

Checks, inspections, findings, and exportable history — for this type and every other safety-critical asset on campus.