ASME A17.1 and A17.2 Safety Code Records, State Elevator Mechanic Licensing, ADA Requirements and OSHA Lockout/Tagout Documentation: Compliance Rules for US Elevator Software

This article is part of our series on Custom Elevator Maintenance Management Platform Development for US Elevator Service Companies: Building a Route, Callback and Contract Billing System

The Code Defines the Work and the Record

Four compliance surfaces shape an elevator service platform, and the first defines both the work and the record. Elevator software compliance starts with the safety code, which governs maintenance, testing, and documentation. The code operates at a level of detail closer to a product specification than a general constraint. A companion inspectors’ manual shapes what an inspector actually looks for.

Those requirements must become more than reference material within the software. They need to appear in workflows, required fields, validation rules, inspection records, and audit trails.

This is where custom software development becomes relevant for equipment-specific workflows and jurisdictional compliance requirements. The same requirements follow mechanics into the field during inspections, maintenance, and service calls. A dedicated field mechanic application can guide technicians through required checks and capture records at the point of service. Those field records then remain connected to the broader service history.

One point should be established before anything else. The edition that applies is the one the authority having jurisdiction has adopted. It may not be the newest version. A company operating across jurisdictions may be working on several editions at once.

This is educational content, not legal advice. Specifics should be confirmed with the state elevator authority and each authority having jurisdiction.

The Safety Code, the Inspectors’ Manual, and Which Edition Applies

What the Code Governs

The safety code covers design, construction, installation, operation, inspection, testing, maintenance, alteration, and repair of elevators, escalators, and related conveyances. For a company, the maintenance, inspection, and testing provisions are the operative ones. They determine what must be done, how often, and what ASME A17.1 records must show. 

A separate code addresses existing installations, and the A17.2 inspection manual guides how inspections are conducted. 

The Adopted Edition Governs

The code is published on a revision cycle. Jurisdictions adopt specific editions through state or local action. The edition adopted where a unit sits is the one that applies. It may be several editions behind the current one.

A company operating across jurisdictions may be working on different editions of identical equipment. That makes edition a dimension of the platform, not just a detail. Adopted editions should be verified with each authority having jurisdiction and tracked as they change.

A Note on the Documents Themselves

These are copyrighted publications. A platform reflects what the code requires. It does not reproduce the code’s text, tables, intervals, or procedures. Any content produced about elevator compliance should reference the codes by designation and describe their role without quoting their contents.

The Maintenance Control Program Requirement in the Code 

The requirement that most directly shapes elevator software compliance is the written maintenance control program. The code requires one for each unit. It is a documented program setting out maintenance procedures and the intervals for performing them. The program must reflect the specific equipment rather than a generic template.

It must account for equipment type, age, usage, and manufacturer recommendations, and it must be available on demand. Records demonstrating the program was followed must be maintained. Those records are what an inspector or authority asks to see.

The software consequences follow directly. The program lives per unit, not per contract or customer. Tasks carry intervals that drive scheduling. Completion gets recorded against specific tasks rather than a visit simply closed.

The whole record stays retrievable per unit and producible on request. The whole record stays retrievable per unit and producible on request. How the maintenance control program requirement connects to the broader set of elevator maintenance software features a US service company needs to build around runs through Elevator Maintenance Software Features: Feature Priorities for a US Elevator Service and Repair Company Planning a 2026 Build. Predictive and condition-based maintenance informed by equipment data is genuinely valuable, and the trade is moving toward it. It supplements the program.

It never replaces the intervals the code requires. A platform must not be built or sold that way. Requirements should be verified against the applicable adopted edition.

State Elevator Mechanic Licensing and Inspector Certification

Who may perform elevator work, and who may inspect it, are governed separately. Requirements vary considerably by state. Many states license elevator mechanics and elevator contractors, covering experience, examination, apprenticeship completion, and continuing education. Some states also require registration of individual units or of the company operating in the jurisdiction.

Some states rely on other mechanisms instead. Inspection is a distinct role, certified under a separate accreditation regime. Inspectors may work for the jurisdiction, for an insurer, or independently, and they are not the maintaining company. That separation is the point.

For a company operating across state lines, the practical burden is tracking credentials, expiry dates, and continuing education by jurisdiction. A mechanic dispatched somewhere they are not licensed is a problem for the work and the company.

For the platform, this means credential records per mechanic by jurisdiction and type, each with an expiry date. Assignment checking and expiry alerts, surfaced far enough ahead to renew, round it out. Requirements should be verified with each state’s authority, since they change.

ADA Elevator Requirements and What Downtime Actually Means 

Accessibility reaches this work in two ways, and the second deserves different thinking. The accessibility standards specify requirements for elevators in covered facilities. These include car and door dimensions, control heights and markings, audible and visible signals, and door timing.

Modernization work engages these standards directly, since altering a unit brings current requirements into play. A company proposing modernization should raise them rather than have a client discover them later.

The second way is more immediate. In many buildings, the elevator is the only accessible route between floors. A unit out of service does not merely inconvenience a wheelchair user. It excludes them from part of the building, potentially their own home or workplace.

That reality should carry into how downtime gets treated. It belongs in response prioritization, in communication with the building, and in how downtime itself gets weighed. Current alteration requirements should be verified before modernization work begins.

OSHA Lockout/Tagout Elevator Work and Site Safety Documentation 

Elevator work involves stored energy, moving equipment, height, and confined spaces. The safety obligations that follow produce records that matter. Energy isolation before working on equipment is the most important of them. Locking out and tagging the disconnect keeps the machine from energizing while someone works inside it.

It is a life safety practice with documented procedures, training requirements, and a record of application and removal. It is the practice that prevents the injuries this trade is most exposed to.

Fall protection applies to hoistway and car top work, and pit entry engages confined space considerations. Controller work engages electrical safety requirements, including arc flash assessment. Working near an open shaft door engages barricading, since building occupants are not part of the crew.

For the platform, the custom mobile app development behind the field mechanic application must keep lockout and tagout procedures accessible in the machine room, with or without a signal. Application and removal should be recorded with who and when, and training records kept per mechanic.

None of this is a checkbox on a job. The record is what a company relies on after an incident. Building it as a formality produces a record that does not help.

Establishing this scope is the first job of a technology discovery sprint, before any of it gets built.

Testing, Certificates, and Other Obligations

Periodic testing categories at different intervals are set by the adopted code. Some require witnessing by a certified inspector and filing with the jurisdiction. The unit’s certificate of operation depends on those records staying current.

How controller telemetry integration, remote entrapment monitoring, route scheduling and parts inventory connect to the testing and documentation layer across the broader platform architecture runs through Elevator Controller Telemetry, Remote Entrapment Monitoring, Preventive Maintenance Route Scheduling and Parts Inventory Integration for a Custom US Elevator Platform. Firefighters’ emergency operation testing carries its own requirements and recordkeeping. Two-way communication requirements in cars are set by the code and revised in recent editions. Some editions include provisions on messaging and video. The applicable edition should always be verified.

Record retention obligations attach to maintenance and test records, and insurers may impose their own. Union agreements govern classification, hours, and assignment across much of this trade. The scheduling layer must respect them.

What a Compliant Platform Actually Holds

If a company builds the maintenance program per unit as the code requires, the records match what an inspector expects. Tracking adopted editions across every jurisdiction served keeps that match intact as requirements shift. 

Checking credentials before assignment protects both the mechanic and the company. Why establishing compliance scope, controller access reality, and jurisdiction footprint through a structured technology discovery sprint before any of this gets built runs through Why US Elevator Service and Modernization Companies Should Run a Technology Discovery Sprint Before Committing to a Custom Maintenance Platform. Treating energy isolation records as evidence, not formality, is what elevator software compliance should aim for.

This content is educational, not legal advice. Specific requirements should be confirmed with the state elevator authority and each authority having jurisdiction. NewAgeSysIT works with elevator service and modernization companies to translate these obligations into a platform that holds up under review. Learn more about digital transformation solutions from a leading AI software development company in the United States.