NYC Elevator Permit Filing Guide: DOB NOW, Code References, and Structural Coordination

Start with the official NYC reference points

Elevator work in NYC should be grounded in the active DOB resources, not recycled assumptions from unrelated building filings. The most useful public starting points are the DOB NOW: Build Elevator Filings Resources, the broader DOB NOW: Build portal guidance, and the DOB NOW Public Portal for public-facing status review.

From a code perspective, the 2022 NYC Construction Codes page is the anchor reference. Elevator teams typically need to coordinate at least Chapter 30 for elevator requirements, Appendix K for NYC modifications to elevator-related standards, and often Chapters 11, 16, 17, and 33 depending on accessibility, structural design, inspection, and construction-safeguard issues.

How the filing team usually splits responsibilities

Elevator filings are rarely a one-person exercise. The elevator contractor or specialty consultant typically leads equipment-specific requirements. The architect and code team help coordinate the broader building pathway. The structural engineer supports the building-side scope when slabs, walls, pits, supports, roofs, or receiving structure are affected.

That split matters because many filing delays happen when the structural implications are assumed to be minor and then discovered late. If the receiving structure needs localized design or if openings must be framed, that work should be defined clearly enough to support the overall filing narrative.

Structural documents that often support elevator work

• Existing-condition observations or assumptions tied to the hoistway area.
• Localized drawings for slab openings, shaft wall changes, support framing, or pit-related work.
• Calculations or engineering notes for receiving-structure checks.
• Coordination narratives that explain what the structural scope covers and what remains specialty work.
• Inspection or construction-phase coordination where the scope triggers related structural oversight.

The exact package depends on the project, but the goal is consistent: make the building-side scope explicit enough that the rest of the filing team can proceed without ambiguity.

Common coordination misses

The most common problems are not abstract code errors. They are gaps between disciplines: assuming an opening can be field-cut without structural review, assuming pit work is isolated from waterproofing and below-grade conditions, assuming an MRL conversion has no receiving-structure implications, or relying on incomplete record drawings without early verification.

Good coordination means treating the structural scope as part of the filing strategy, not as a cleanup task after the elevator concept is already fixed.