BSA AI ethics November 2026: a document-use and review question card
Use the published BSA AI ethics agenda to frame project-document permission and output-review questions for a preconstruction team.
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
- 3 min
- Published
On this page
Use the published topics of the November 17 Boston Society for Architecture (BSA) AI ethics discussion to frame a live question with a designer or owner about using project documents or reviewing AI output. This is a dated agenda-based question card, not an attendance invitation or an event recap. Its design-practice focus makes GC estimating a secondary fit; the project-specific decision remains with the relevant parties.
What the BSA listing establishes
As checked on November 17, 2026, the BSA event listing describes Ethics of AI: A Conversation with Practitioners and the BSA Ethics Committee, scheduled for November 17, 2026, from 6 to 7:30 p.m. at Payette, 290 Congress Street, fifth floor, Boston. It lists the event as free and open to the public. The published discussion topics include AI authorship, data privacy, environmental impact and workforce transformation.
Those are announced topics, not observed session findings. The listing establishes neither a GC estimating agenda nor an answer for any particular project. No actual delivery, recording or participant conclusions have been verified.
Decide whether the conversation fits the bid in front of you
The most useful agenda prompt for a preconstruction lead is an unresolved handoff between organizations. For example, a design team may issue a drawing set for pricing while the GC wants to use a document-processing tool to prepare trade scopes. The useful question is not simply whether AI is acceptable. It is who can authorize this particular use of this particular set, what the parties expect to be disclosed, and who will check the resulting scope before bidders rely on it.
Bring a designer or owner contact into the follow-up if their decision is needed. The event may help frame questions, but a general discussion cannot grant project-specific permission or settle contract obligations. If the only open issue is an internal preference about how an estimator formats a scope, an internal review is likely the more direct next step. Consult the relevant project agreements and appropriate advisers for the actual permission and disclosure decision; this guide is not legal advice.
Carry a document-use and output-review question card
Use the card below for one document set and one proposed use. Record unknowns as open items rather than treating silence as consent.
| Question | What to record before the discussion | What to resolve afterward |
|---|---|---|
| Source owner | Identify who supplied the set and who can answer for its use; list the issue and revision | Confirm the appropriate authority and any conditions on use |
| Permitted use | Describe the proposed tool, input documents and purpose, including whether material would leave the team | Obtain a project-specific determination through the appropriate channel before use |
| Decision owner | Name the person responsible for authorizing the use and the estimator responsible for reviewing output | Assign each decision and a due date; escalate an unresolved boundary |
| Disclosure needed | Identify who may need to know about the proposed use and what is still uncertain | Confirm what disclosure, if any, is required and document the response |
| Retained evidence | Identify the document version, request, response, output and review record to preserve | Keep the decision and its basis in the project record under the team's applicable process |
For an illustrative mechanical package, the output might assign equipment connections to the electrical trade while the documents leave the boundary unclear. The reviewer should return to the relevant drawing and specification revision, identify the ambiguity, and record an assumption or clarification request. A plausible sentence in a generated scope is not the decision. If the document-use decision is still open, resolve it before submitting that set for the proposed use; use an authorized review route in the meantime.
The scope-generation guide explains how to define the evidence behind each scope decision, including the source, revision, open item and responsible reviewer. The ethics question comes earlier: whether this set may be used for the proposed workflow and what the team needs to communicate about it.
Keep the source trail through scope review
Piper's scope-generation workflow builds trade-specific scopes from drawings, specifications and addenda with source references. An estimator still needs to review unclear boundaries. A source reference helps the reviewer inspect an output; it does not itself establish permission to use the input or resolve disclosure obligations.
Apply the question card to the current project
Use a question that can be discussed without exposing restricted project material. Confirm separately with the relevant parties whether the specific document set and proposed tool use are permitted. Record the decision, the person responsible and any unresolved conditions.
The published agenda describes the planned conversation. It does not establish what participants concluded or grant permission for a project document set. Keep the project-specific decision with the relevant parties and the estimator who will review the resulting scope.
Related reading
Construction scope generation: a practical guide for GCs
How general contractors turn drawings, specifications, addenda, and company standards into trade scopes a subcontractor can price, an estimator can trace, and a senior reviewer can challenge.

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.