---
title: 'NYC building code review before pricing: turn the applicable requirements into scope'
url: 'https://piper-ai.com/resources/nyc-building-code-preconstruction-review'
description: 'For a NYC construction estimate, confirm the applicable code basis with the design team, then trace documented requirements into scope, logistics and pricing.'
contentTypes: [guide]
publishedAt: '2026-11-15T10:38:25.000Z'
updatedAt: '2026-11-18T15:33:08.493Z'
author: 'Ido Gedanken, CEO'
readingTime: 4
---

# NYC building code review before pricing: turn the applicable requirements into scope

1. Confirm the project's code basis instead of assuming a search result determines applicability.
2. Distinguish enacted future requirements from the rules governing today's filing.
3. Assign documented obligations to packages before accepting trade coverage.

An NYC building-code search is a starting point for finding the governing documents, not a determination of which requirements apply to a project. Before pricing, a GC preconstruction team should obtain the code basis from the responsible design professionals, identify the issued project requirements, and trace their consequences into trade packages, temporary work and the estimate.

The useful estimating output is a reviewable requirements register. It should show the source, affected work, responsible package, pricing basis and unresolved interpretation. It should not substitute an estimator's reading of a search result for a professional code determination.

## Start with the project and its confirmed code basis

Ask the design team to identify the applicable code editions, project filing basis and relevant approvals or determinations. Record the documents used to communicate that basis. An existing-building alteration and a new building can raise different applicability questions.

DOB's [codes directory](https://www.nyc.gov/site/buildings/codes/codes.page) points to the construction codes and related resources, while noting that its site does not contain every applicable law. Start with the current official materials and the project's issued documents rather than a saved summary from an earlier bid.

Record an unresolved interpretation as a question for the appropriate professional. A package lead can identify a scope consequence without taking ownership of the design team's determination.

## Keep enacted changes separate from their effective dates

As checked on November 15, 2026, DOB's [Existing Building Code page](https://www.nyc.gov/site/buildings/codes/existing-building-code.page) states that the new EBC takes effect July 17, 2027. The page describes the current framework before that date and the limited prior-code option under the Administrative Code.

That distinction matters for an estimate spanning a filing or regulatory transition. Do not assume that an enacted code is already the governing code, or that a project's start date alone resolves its filing requirements. Confirm the applicable transition provisions with the responsible design team using the current official text.

Keep the confirmation and source date with the estimate basis. If the filing approach or project scope changes, reopen the question before reusing the earlier package assumptions.

## Translate documented requirements into assignable work

Read the requirements alongside the drawings, specifications and project conditions. Ask what work is necessary, which package carries it, and what evidence supports that assignment.

An illustrative review might identify a temporary protection requirement that affects several trades. One proposal may exclude the protection, another may assume it is by others, and the GC's estimate may contain a general allowance with no defined quantity or duration. The issue is not solved by repeating the code reference in all three places.

The [scope-generation guide](https://piper-ai.com/resources/construction-scope-generation-guide) explains how a document requirement becomes a package boundary. The responsibility map should make shared obligations explicit enough to review against the actual proposals.

## Separate technical compliance from access and work-window permissions

A code basis does not answer every logistical or authorization question. Review the project's access, temporary works, inspections, noise controls and permitted work windows through the appropriate agency and contract sources.

Use the [NYC street-access review](https://piper-ai.com/resources/nyc-dot-street-work-restrictions-preconstruction) where right-of-way restrictions affect the sequence. Use the [night-work estimating guide](https://piper-ai.com/resources/nyc-after-hours-construction-noise-estimate) when the plan depends on evenings or weekends. Neither should be treated as permission to perform the work.

Bring confirmed obligations back into the estimate. A different access arrangement can change protection, deliveries, temporary services, supervision or duration even when the permanent installation remains the same.

Different local requirements need their own scope review. The [Local Law 11 facade guide](https://piper-ai.com/resources/nyc-local-law-11-facade-construction-scope) separates an inspection finding from a repair package. The [Local Law 97 retrofit guide](https://piper-ai.com/resources/nyc-local-law-97-retrofit-construction-scope) separates an emissions-compliance plan from the construction work being priced. The responsible professionals determine applicability on the actual building.

## Give each unresolved item an owner and an estimate treatment

Use a register the review team can act on.

| Register field | What belongs in it |
| --- | --- |
| Requirement source | Issued document and current agency or design reference |
| Applicability confirmation | Responsible professional's determination or the question awaiting one |
| Scope consequence | Work or constraint that affects a package |
| Coverage evidence | Proposal inclusion or other pricing support |
| Open decision | Named owner and required resolution date |
| Estimate treatment | Explicit basis carried while the question remains open |

This is a working estimating scaffold, not a DOB form. It keeps a missing technical answer from disappearing into a generic qualification or contingency line.

## Recheck the basis when the package changes

At final review, confirm that the estimate and selected proposals use the same issued requirement set. A revised detail, filing strategy or access plan can invalidate a scope decision that was reasonable when first made.

The [NYC public-bid review hub](https://piper-ai.com/resources/nyc-public-construction-bid-review-checklist) connects these technical and pricing questions with the separate submission review. A complete response folder and a supported estimate remain distinct checks.

## Apply company review questions to the project documents

Piper's [Survey workflow](https://piper-ai.com/use-cases/survey) applies a company's questions to project documents, answers what the sources support and flags items needing a human response. Findings stay with the project understanding used in later scope and review work.

A team can use that workflow to make its standing prebid questions repeatable. The responsible professionals still determine code applicability, the contractor verifies package coverage, and the relevant authorities govern permits and approvals. Piper does not certify code compliance or issue a permit.
