Elevator Consultant Compliance Submittal Guide
A technical checklist for consultants evaluating traction elevator brake and car-motion protection projects.
Elevator consultants need a defined evidence trail before they recommend a traction-elevator brake or car-motion protection retrofit. The equipment inventory, adopted code edition, required protection function, technical documents, field test plan, and AHJ acceptance process must line up. A product label alone does not establish project compliance.
This guide is a project-review framework. It does not replace the adopted code, the elevator professional of record, or the Authority Having Jurisdiction.
Start with the elevator inventory
Record the equipment that controls the code analysis. Identify the elevator type, machine type, brake configuration, rated load, rated speed, governor arrangement, controller, and whether the job is repair, modernization, or a jurisdiction-directed safety upgrade. A traction-elevator requirement should not be applied to a hydraulic elevator because both the equipment and applicable safety provisions can differ.
For older geared traction installations, identify whether a single-plunger brake configuration is present. New York City guidance for affected projects references Unintended Car Movement Protection under ASME A17.1-2013 Section 2.19.2. The consultant should confirm that the actual machine, scope, and DOB process match the project before selecting a corrective path.
Name the required protection function
Unintended Car Movement and Ascending Car Overspeed Protection are separate functions. They should not be treated as interchangeable search terms, test methods, or retrofit outcomes.
ASME A17.3-2020 addresses Ascending Car Overspeed Protection in Sections 3.10.13 and 3.13.1. It addresses Unintended Car Movement in Sections 3.10.14 and 3.13.2. Each provision has its own triggering conditions and test criteria. The adopted edition, local amendments, elevator configuration, and AHJ interpretation determine which function is required.
Write the required function into the specification. Avoid broad language such as “provide a code-compliant brake” without identifying the governing requirement. That wording forces the contractor and inspector to resolve a design issue after procurement.
Build a submittal package that can be reviewed
A technical submittal should identify the exact device configuration proposed for the elevator. Include the manufacturer data sheet, installation and maintenance instructions, device dimensions, rail interface, mounting arrangement, rated load and speed limits, electrical or hydraulic dependencies where applicable, and the proposed operating sequence.
Attach documentation that supports the claim being made. HydraSafe provides CSA Group and Liftinstituut technical documentation, finite element analysis reports, and available approval letters for review. Confirm the edition, scope, configuration, and applicability of every document. A document for one arrangement does not automatically establish acceptance for another.
The submittal should also include drawings showing the installed relationship between the device, guide rail, car frame, machine, governor, and controller. State any field modifications, clearances, structural work, and power or control interfaces. If a device is presented as independent of a particular system, describe exactly what that means in the proposed operating sequence.
Define the test and acceptance plan before ordering
The consultant should define a witness and acceptance plan early. Identify the installation checks, functional tests, load conditions, travel conditions, reset process, documentation to be delivered, and parties expected to witness work. Confirm whether the AHJ requires a pre-approval, a variance, a field evaluation, or a final inspection sequence.
Separate physical installation time from return-to-service time. Physical rail mounting may be completed within a limited work window, but permitting, inspection, testing, corrections, and AHJ acceptance control the date an elevator can return to service. The construction schedule should show those activities separately.
Confirm jurisdiction before making a deadline claim
State and municipal adoption does not create a uniform national retrofit deadline. Code edition, effective date, amendments, enforcement policy, and project type vary. The project team should obtain the current requirement from the local AHJ and document the response in the project record.
This is especially important for marketing and procurement documents. Do not state that a January 1, 2027 requirement applies to every traction or hydraulic elevator. Do not include Florida in a claim that it requires the A17.3-2020 UCM, ascending-car-overspeed, or emergency-brake provisions it excluded. A jurisdiction list is only useful when it is current, specific, and tied to the function being discussed.
Consultant record checklist
Before issuing a recommendation, retain the elevator inventory, governing code citation, local amendment review, technical data, drawing set, test plan, AHJ correspondence, and final acceptance record. This establishes a defensible basis for the specification and gives the owner a clear record for future maintenance and inspection.
HydraSafe Brake can provide product documentation for technical review. The consultant, contractor, and AHJ determine the correct application and acceptance path for each project.
Explore Topics
Technical guidance published by
HydraSafe Brake LLC
Product and code-context material for elevator project review. Confirm equipment, code adoption, document scope, and acceptance requirements for the specific project.
Read technical content standards