New York Build 2027 public-project panel: prepare questions an estimator can use
Prepare public-project questions for New York Build, then turn owner comments into document requests and assumptions an estimator can verify before pricing.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 2 min
- Published
On this page
Use the public-project panel to improve the questions in your next pursuit file, not to create a bid opportunity from a broad program comment. Ask what document would establish a particular project's access, scope and delivery assumptions, then verify it when the solicitation exists.
This independent Piper guide was checked November 15, 2026. The organizer lists New York Build March 2–3, 2027 at Javits and its Lessons Learned from Public Projects panel March 3, 1:00–1:50 p.m. Check the organizer for registration and schedule changes. A panel listing does not establish a procurement commitment or its future conclusions.
Turn the answer into a document request
Consider an illustrative occupied public-building renovation. A participant says access will be coordinated with the occupant. That is a useful lead, but the estimator still needs the particular bid's phasing, permitted working hours, shutdown process and responsibility for temporary protection. Record who made the comment and its context; do not insert it into the estimate as a contract term.
| Question to ask | Evidence to request when issued | Estimating decision |
|---|---|---|
| Is this program outlook or an issued solicitation? | Solicitation and amendments | Whether a pursuit can be priced now |
| What delivery method is contemplated? | Procurement and contract documents | Who owns design and coordination assumptions |
| How mature is the design? | Issued drawings, specifications and outstanding design information | Clarifications and allowances requiring review |
| What access and shutdown windows are contemplated? | Phasing, access and operational restrictions | Sequence, staffing and temporary-work carry |
| Who coordinates occupant and third-party interfaces? | Contract responsibilities and interface documents | Scope ownership and unresolved exclusions |
Ask which agency or document owner can clarify an issue and whether an answer is specific to a project. A general statement about future programs is not the same as an issued project requirement. Avoid assuming a list of future projects from a panel discussion.
Keep the informal and issued records apart
After the event, create two columns in the pursuit log: discussion lead and verified project evidence. Assign a reviewer and a due date for each open item. When documents are issued, compare the actual version against the note, route conflicts through the project's authorized clarification process, and record any remaining assumption in the estimate. Company counsel and the bid team should determine the effect of applicable contract language.
For the pre-event itinerary see the New York Build guide. The AGC public-work workshop plan addresses bid-team commercial assumptions, while public bid leveling documentation explains how to retain the reasoning behind a carry.
For a project actually governed by New York City requirements, use the NYC building-code preconstruction review as a separate local check. A conference comment does not establish which code or approval applies to a particular project.
If the question concerns an agency’s future program rather than an issued project’s operating constraints, the ACEC agency-panel plan uses a separate pursuit record. Keep that outlook distinct from the phasing and access questions here.
Carry the questions into document review
Piper Survey applies company questions to project documents, answers supported questions and flags items needing a human response. For the occupied-building example, the team can keep the access question visible while a reviewer checks the applicable documents and decides what remains unresolved.
Related reading
Public bid leveling: the file is the evidence
Prepare a source-backed leveling file before a sealed public bid. Keep scope coverage, bid compliance and permitted post-opening procedures distinct under the governing rules.

NYC building code review before pricing: turn the applicable requirements into scope
For a NYC construction estimate, confirm the applicable code basis with the design team, then trace documented requirements into scope, logistics and pricing.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.