---
title: 'Boston Built Week 2026: choose meetings by the preconstruction decision they can inform'
url: 'https://piper-ai.com/resources/boston-built-week-2026-preconstruction-event-selection'
description: 'Select independently hosted Boston Built Week events by the decision, access, and evidence a preconstruction leader actually needs.'
contentTypes: [guide]
publishedAt: '2026-11-18T06:32:11.791Z'
updatedAt: '2026-11-18T06:32:11.807Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# Boston Built Week 2026: choose meetings by the preconstruction decision they can inform

Start with a live decision, then find an event that can inform it. A preconstruction leader investigating a controlled technology pilot has a more direct reason to attend a contractor working group than a general investor networking event. Build the schedule around accessible sessions and leave time for follow-up; a week-wide listing is not a single admission pass.

[Boston Built Week](https://bostonbuiltweek.com/) describes a decentralized program running November 15–21, 2026, with independently hosted events and separate registrations. The anchor calendar identifies a leadership forum, founders and investors gathering, demo day and BuiltWorlds conference. Individual hosts control access and schedules. For example, the [Built Leadership Forum](https://builtleadershipforum.com/) lists the past November 16 event at the UMass Club and says registration was closed and the event sold out. This past listing is not a current attendance option. The two sites give different ending times, so use the host's current details rather than assuming the roundup governs.

## Select by problem, access and next decision

This is an estimating team's selection aid, not a statement that any session delivers a particular outcome.

| Problem to resolve | Host and location | Access or fit | Question and evidence to request | Follow-up decision |
| --- | --- | --- | --- | --- |
| Define a pilot for scope review | BuiltWorlds at Convene One Boston Place | Check registration and individual research-track restrictions | What input revision and reviewer evidence would make a test meaningful? | Authorize a bounded evaluation or defer |
| Review a past market-direction listing | Built Leadership Forum at UMass Club, November 16 | Past event; not a current attendance option | If published material becomes available, identify claims to verify independently; the listing does not establish delivered conclusions | Decide whether further source research is useful |
| Meet founders and investors | Builders and Backers, check host venue | Secondary fit for a live estimating question; check host registration | Is there a relevant project problem and a person who can discuss it? | Arrange a focused follow-up only if useful |
| Review startup demonstrations | Suffolk Technologies BOOST demo, check host venue | Secondary to project scope review; check admission | Can a proposed workflow be evaluated with an authorized test set? | Decide whether a separate pilot conversation is warranted |
| Social networking | Independent hosts and locations | Poor fit when the only objective is resolving a current package question | Identify a specific contact and question before allocating time | Follow up selectively |

The [BuiltWorlds event page](https://builtworlds.com/event/2026-aec-emerging-tech/) lists November 18–19, with the main program on November 19 and some restricted research-track sessions. Do not infer that every session is included with a general registration.

## Resolve overlap before booking

Check each host's latest time, address and access conditions. Where two useful events overlap, favor the one that can answer a decision due soon, then ask a colleague attending the other for a specific follow-up. Record the question, person responsible, and evidence expected; a contact list alone does not resolve an estimate assumption.

For questions that become package decisions, [define the evidence behind each scope decision](https://piper-ai.com/resources/construction-scope-generation-guide). The event descriptions are prospective, not reports of delivered findings.
