BuiltWorlds AEC Emerging Tech Boston 2026: define the pilot evidence before meeting vendors

Choose BuiltWorlds meetings around a specific preconstruction proof question and a pilot card that names the evidence needed to proceed.

Guide3 min read

Published

Tower crane above steel reinforcement

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. Separate the pre-event from the conference program
  2. Select one problem before selecting meetings
  3. Pilot evaluation card for the meeting
  4. Turn the discussion into an estimating decision

For a GC preconstruction leader, the useful reason to attend BuiltWorlds AEC Emerging Tech is a specific workflow question your team can test later. Choose a meeting or accessible session because it might help answer that question, and agree on the evidence your reviewer would need before a pilot proceeds. A polished demonstration alone does not establish that a tool can handle your project or that the team should deploy it.

Separate the pre-event from the conference program

The BuiltWorlds organizer page lists November 18–19, 2026, with Convene One Boston Place, 201 Washington Street, Boston, as the conference location. Its November 18 pre-event listing is Suffolk BOOST Cohort 7 Demo Day; the main conference program begins November 19. That explains why a one-day roundup may name November 19 while the organizer lists two dates. Confirm the venue and admission for each event individually, particularly the separate pre-event, before making plans.

The published program describes contractor-focused pilot-to-scale discussions and working groups. Some research-track sessions are restricted to track members, so confirm eligibility as well as registration before relying on a session. As of November 16, this is a future agenda, not evidence of completed discussions or outcomes.

Select one problem before selecting meetings

Start with an unresolved requirement that matters to an actual estimating workflow. For example, a team preparing a mechanical package may need to identify whether a revised controls requirement changes the electrical and mechanical scope boundary. A vendor meeting is relevant if it can help establish how the team would inspect that question across a controlled document set and its revision. A general pitch about AI is a weaker use of the same time.

Ask the prospective presenter to explain what the reviewer sees, which input version supports the result, and how an unresolved interface stays visible. Do not send project drawings or other restricted information simply to secure a demonstration. First establish internally what materials are permitted for evaluation; a synthetic fixture can frame the conversation.

Pilot evaluation card for the meeting

Use this card to make the proposed test comparable across conversations. The example is hypothetical, not a completed test or a product performance claim.

FieldExample to agree before a pilot
Input and revisionA permitted fictional mechanical and electrical drawing excerpt plus a labeled addendum revision
Known unresolved requirementControls wiring responsibility is not settled between two packages
Expected artifactA draft scope line for each affected package with its source reference and an explicit open question
Reviewer treatmentA senior estimator checks each line against both versions and records accept, revise or reject with a reason
Acceptance evidenceReview record shows the current source, unresolved interface, reviewer disposition and any correction needed
Stop conditionStop if permission for inputs is absent, the revision cannot be identified, or the reviewer cannot inspect the source basis

This card is a proposed evaluation design. Set the threshold with the estimator who owns the resulting work: for example, whether every critical line in this small fixture must have a reviewable reference and whether unresolved items must remain visibly open. A successful fixture would justify considering a broader test, not prove performance across every project. Keep a record of the input, output and manual review so another reviewer can reproduce the decision.

Turn the discussion into an estimating decision

After a meeting, classify the next step as a controlled test, a request for missing information, or no further action. Record who owns the follow-up and what evidence would change the decision. Compare any suggested output to the way your team defines the evidence behind each scope decision, including source version and package ownership.

The organizer's schedule does not establish actual session content, access for a particular attendee, or any vendor's results. Recheck session restrictions, timing and the individual pre-event location with the organizers.

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.