---
title: 'New York Build 2027: a GC preconstruction planning guide'
url: 'https://piper-ai.com/resources/new-york-build-2027-gc-preconstruction-guide'
description: 'Plan New York Build 2027 around an estimating bottleneck, with role-specific preparation and a reviewable way to turn conversations into a project test.'
contentTypes: [guide]
publishedAt: '2026-11-17T09:04:43.746Z'
updatedAt: '2026-11-17T09:04:43.790Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# New York Build 2027: a GC preconstruction planning guide

A chief estimator should take one unresolved scope decision to New York Build and return with a test owner, not a collection of vendor claims. A preconstruction director should decide which handoffs or commercial assumptions need attention across pursuits. Both should reserve time for follow-up while the source and limitation of each claim are still clear.

This independent Piper planning guide is based on information checked November 15, 2026. The organizer lists [New York Build](https://www.newyorkbuildexpo.com/exhibitors/new-york-build) for March 2–3, 2027 at the Javits Center, covering New York and Tri-State construction, design and real estate. Use the organizer's page for registration and the current agenda; sessions can change.

## Choose the question before the stage

For an illustrative commercial renovation, assume the mechanical drawings show a new duct through a rated partition, while the quote excludes patching. The estimator's question is who carries the opening, firestopping and finish restoration. Bring the relevant drawing, specification and quote only if the company permits sharing; otherwise use a synthetic example. Redaction is not a substitute for permission.

| Role | Question to take | Evidence to bring | Output after the event |
| --- | --- | --- | --- |
| Chief estimator | Can the team trace a trade gap into its carry? | Approved scope excerpt and quote exclusion | Owner and test for the unresolved interface |
| Preconstruction director | Which handoff creates repeat ambiguity? | Anonymized process map and decision log | One accountable owner and pilot boundary |

The [construction scope generation guide](https://piper-ai.com/resources/construction-scope-generation-guide) explains how to structure the scope itself. At the event, ask a prospective provider to show the original requirement, the relevant exclusion and what remains for a person to decide. A polished summary alone cannot settle ownership of the carry.

## Separate the organizer's schedule from your plan

The organizer lists a [practical AI workshop](https://www.newyorkbuildexpo.com/new-york-build-conference-agenda-2027/workshop-ai-action-practical-plan-built-environment) on March 2 at 2:00–2:50 p.m. and a [preconstruction-tools panel](https://www.newyorkbuildexpo.com/new-york-build-conference-agenda-2027/panel-preconstruction-tools-changing-way-new-york-gets-built) at 3:00–3:50 p.m. Its [public-project panel](https://www.newyorkbuildexpo.com/new-york-build-conference-agenda-2027/panel-lessons-learned-public-projects) is listed March 3 at 1:00–1:50 p.m. Recheck the agenda before travel. These listings establish planned sessions, not what speakers will conclude.

Choose the AI track only if someone owns a follow-up evaluation. Use the controlled demo sheet for that test and the separate public-project question sheet for owner interfaces. The conference selection guide helps compare this trip with other events.

## Capture a decision, not just a contact

For each useful conversation, record the claim, who made it, the material shown, the missing evidence, a next action and its owner. Within the team, distinguish a demonstration from a result on your package. If the example cannot be shared, arrange an authorized internal test later instead of uploading it on the floor. The broader process for [evaluating AI preconstruction software](https://piper-ai.com/resources/evaluating-ai-preconstruction-software) includes the procurement and review questions that a conference conversation cannot resolve.
