
Elevator phone inspection records are the proof that the phone in each car still reaches a person who can respond. A usable record shows which car was tested, when, by whom, what the call reached, and how the phone stayed powered. Placing the call takes a few minutes; the record is the part that has to survive a change of staff, a change of carrier, and a change of building owner.
What an Elevator Phone Inspection Actually Checks
The physical test comes first. Someone rides the car, presses the call device, and confirms three things: that a call is placed, that audio works in both directions, and that a person answers who knows which building and which car is calling. A voicemail box or an unattended desk passes the dial-out check and fails the test.
The accessibility half is written into the standard rather than left to an inspector's judgment. In the 2010 ADA Standards, §407.4.9 Emergency Communication sends emergency two-way communication systems to §308 for reach ranges, and requires that tactile symbols and characters be provided adjacent to the device. Those are measurable items, which is why they belong in the record and not just in the cab.
The elevator safety code side is jurisdictional. ASME publishes A17.1, the Safety Code for Elevators and Escalators, currently in its 2025 edition, and a separate guide for the inspection of elevators, escalators and moving walks, A17.2, whose 2023 edition ASME describes as covering equipment required to conform to A17.1-1955 and later editions and to A17.3. That guide carries its own caution — it may not reflect the latest requirements in the current A17.1 and A17.3 Codes — which is the reason a record should name the code edition the jurisdiction has adopted instead of saying "the code." Our breakdown of what the elevator codes require of the phone itself covers the substance of those requirements.
What Belongs in the Record
The fields do not have to be elaborate, but they do have to identify the car and the answering party without ambiguity.
- The identifier: building, elevator bank, car number, and where the device sits in the cab.
- The date, the time of day, and the name of the person who placed the test call — not the company name alone.
- The result: that the call connected, that audio was two-way, who answered, and how long the connection took.
- The answering location, and whether that location can identify the car rather than only the building.
- Power: whether the device ran on secondary power, and the date the battery was last replaced.
- The transport: copper line, IP path, or cellular communicator. For copper, add the carrier of record and the circuit number.
- The accessibility items: the reach-range measurement and a photograph of the tactile signage at the device.
- The code edition tested against, and the inspection guide's edition.
Where Elevator Phone Records Break Down
Four failures make a file thin or unusable.
Testing and filing are different jobs. The technician who runs the call is rarely the person who keeps the folder, so the result lives in an email or a vendor's portal that the building does not control. When the vendor changes, the history goes with them.
The record identifies a result, not a car. "Elevator phone tested, pass" tells an inspector nothing at a property with four banks and twelve cars. The car number is the field that makes the rest of the record useful.
The answering location changed and nobody updated the file. A monitoring vendor switch, a consolidation, or a change in front-desk hours all break the answer path while leaving the test log looking complete.
The line underneath changed hands. Before an incumbent carrier removes or disables copper, it owes public notice under the Commission's network change rules, and 47 CFR § 51.325 defines a copper retirement as the removal or disabling of copper loops, subloops, or the feeder portion of those loops, or their replacement with fiber-to-the-home or fiber-to-the-curb loops. Under § 51.333, that notice goes to directly interconnecting carriers and, from October 15, 2026, 911 service providers, not to the building whose phone hangs off the line, so the record is often the only place the change was noticed. Elevator phones and the copper sunset works through that specific problem.
How a Cellular Upgrade Rewrites the Evidence
Replacing a copper path with a cellular communicator is an installation change, and the old record set describes equipment that is no longer in the machine room. Three habits keep the file honest through it.
Start a new record for the new device, with the device documentation, the listing information the manufacturer holds, and its own battery replacement date. Do not append the new device to a log that still names the old line.
Test from inside the car, end to end. A test at the communicator proves the device transmits; it does not prove the call path from the cab, which is the path an inspection tests.
Keep the last test record for the copper line and the carrier's retirement notice together. They tie the change to a date and a cause, and the filing side of that event runs on a federal schedule the building may never see. Under 47 CFR § 51.333, as amended by FCC 26-19 effective October 15, 2026 (91 FR 62334), the carrier must give direct notice of a planned copper retirement at least 90 days before implementation, or 15 days for copper not being used to provision services to any customers.
Keeping the File Across a Portfolio
A single-building file can live in a binder. A portfolio needs one shape applied everywhere, because the value of these records is comparative: the same fields per site is what lets an owner see which properties are carrying risk before an inspection finds it.
Use one folder per site with the same field names, put one owner's name on the whole set, and note for each car whether the path is copper, IP, or cellular. The copper sunset risk assessment walks a portfolio site by site and shows where the remaining copper exposure sits, and the compliance audit checklist for facility managers covers the rest of the life-safety portfolio the same file has to hold.
Two operational rules save the most trouble. Record the transport on every test, so a carrier notice can be matched to the car it affects without a site visit. And when the answering location changes, re-test and re-file rather than editing the old entry — the record's value is that it shows what was true on the day someone stood in the cab.
If your elevator phone records are thin, or the person who kept them has moved on, our voice team can map what each site needs and what the file should contain. Tell us how many cars you are responsible for and we will start with the sites that still depend on a copper path.
About the author
Carter Dewey
Carter Dewey is CEO & Founder of TrustedNetworx, helping multi-site organizations navigate telecom modernization, POTS replacement, and AI-powered operations — translating complex infrastructure challenges into practical, phased migration roadmaps.