Bisnow New York construction conference 2026: questions before committing a budget

Prepare for Bisnow’s New York construction conference with a decision log linking design gaps, owner choices and estimate treatment to the next review.

Guide3 min read

Published

Construction scaffolding interior

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
On this page
  1. Ask what the budget assumes the owner has decided
  2. Separate conversion evidence from ground-up choices
  3. Carry the decision into the trade scope

An early budget is useful when the team can say which design facts support it, which owner decisions remain open and what would change the carry. Bring that decision record to Bisnow's New York construction conference, rather than asking for a single cost benchmark that may not fit the project.

This independent Piper planning guide refers to the organizer's agenda and registration page. Bisnow lists December 3, 2026 at 8 a.m. EST at the Marriott Marquis in New York. Planned discussions include predevelopment cost and timeline, building upgrades and ground-up development. Check the organizer for changes.

Ask what the budget assumes the owner has decided

Before a discussion, identify one budget with a live decision behind it. Ask which design information fixes the scope, who can authorize the unresolved choice and when the estimate must be updated. A target budget is not itself a scope definition. A number can be useful for planning while still being unsuitable as a commitment.

For an illustrative office renovation and fitout, suppose the owner has not decided whether existing building services will be reused. The estimator can carry a stated assumption, but should not present it as a confirmed condition or let a trade quote quietly settle the owner's choice.

Unresolved itemEvidence nowOwner decisionTemporary estimate treatmentRevisit when
Services reuseExisting narrative is incompleteConfirm intended reuse after design reviewCarry a clearly labeled provisional basis and identify exclusionsDesign team issues service strategy
Occupied workOccupancy plan not issuedSet access and operating constraintsSeparate assumed off-hours work from base scopeOwner approves phasing plan
Finish extentPreliminary concept onlySelect extent and qualityDescribe allowance basis and what it excludesFinish schedule or decision is issued

These are examples, not requirements or prices. Give each row an owner and a due date. Record whether the carry is an allowance, a provisional estimate or excluded work according to the actual estimate's conventions. Avoid covering the same unknown both in a trade carry and in a separate contingency without making that treatment visible.

Separate conversion evidence from ground-up choices

An existing building invites questions about verified conditions, remaining services and access while the property operates. Ground-up work also has open decisions, but the team may be comparing site, system and design choices rather than relying on inherited conditions. In either case, ask what document or owner decision will close the assumption, and what scope packages must change if it does not.

Before using the number as a proposed ceiling, follow the guaranteed maximum price estimate review. For a different event focused specifically on existing buildings, use the conversion due-diligence question plan. The broader conference planning guide helps choose which discussion warrants a team's time.

When a budget gap prompts an alternate, use the value-engineering scope review to preserve the accepted performance and changed scope, rather than recording only a lower total.

If the unresolved decision is how to evaluate a preconstruction workflow rather than how to qualify an owner budget, the New York Build planning guide prepares a different kind of test. Select the event according to the decision the team can actually review afterward.

Carry the decision into the trade scope

After the event, assign an estimator to reconcile the log with the project documents, package assumptions and owner decisions. If the owner selects new services, revise the affected scope and estimate together; keep the prior basis visible for the reviewer. Piper's Scope Generation turns project requirements into trade scopes with source-linked findings. The project team still decides how to treat its open assumptions.

ShareLinkedInX

Related reading

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.