AGC MA Innovation Summit 2026: use the published agenda to structure a preconstruction risk review

Use the archived AGC MA Innovation Summit agenda to frame project-specific preconstruction evidence and decisions.

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. Convert agenda themes into evidence requests
  2. Follow one issue through four review gates
  3. Use the archive in a current review

Archive: The AGC MA Innovation Summit was scheduled for November 5, 2026, at Bentley University in Waltham. This is an agenda-based planning exercise, not an event recap or an account of attendance. The organizer's published agenda lists preconstruction risk, contracting, AI, owner/GC/designer alignment and subcontractor prequalification among its topics.

For a preconstruction leader reviewing a live project, the value of the archived agenda is a set of prompts: ask what evidence would support each decision today. The topics do not establish that any AI system predicts project outcomes, or that a particular session reached a particular conclusion.

Convert agenda themes into evidence requests

This original worksheet is a suggested internal review, not a record of the summit's discussions.

Published themeQuestion for the current projectEvidence to put beside the decision
Preconstruction riskWhich assumption could change both scope and estimate?Current drawing and specification references, assumption owner and estimate treatment
ContractingWhich party is proposed to own an unresolved interface?Applicable draft contract and written project allocation for legal or commercial review
AIWhich output is being proposed for use and how will a reviewer check it?Input set and revision, output sample, source references and human disposition
Owner, GC and designer alignmentWhere do the parties need the same answer before the next estimate?Decision log, affected design references, decision owner and due date
Subcontractor prequalificationIs this an assessment of the firm or of a particular quote?Current project qualification criteria and separate proposal scope review

For example, a fictional estimate may carry a controls connection while the equipment package leaves the point of connection unresolved. The estimator records the assumption and source, the designer confirms the intended interface, and the commercial lead checks the proposed allocation. Until those steps occur, the carry remains an assumption rather than an agreed requirement.

Follow one issue through four review gates

Use a single unresolved requirement to connect the agenda themes instead of holding five separate conversations. The following controls example is illustrative; it was not presented at the summit and is not a finding about any named project.

A scope draft carries an equipment-to-controls connection. The equipment proposal excludes that connection, and the controls proposal has not identified its point of connection. The estimate has a line for controls, but the scope documents do not show whether it covers this interface. A senior reviewer cannot resolve the gap by accepting the total or by assuming an AI-generated scope sentence has assigned the work.

Review gateEvidence to inspectDecision and stop condition
RequirementCurrent equipment detail, controls specification and the referenced drawing issueConfirm what connection is required. If the documents conflict, obtain design clarification before calling the scope complete
Package allocationBoth proposals and the proposed trade scopeAssign the connection once, with adjacent-trade duties. If neither proposal carries it, retain the open item and identify the pricing evidence needed
Commercial treatmentEstimate line, qualification and proposed commitmentIdentify whether the carry has a supported scope basis. The commercial authority decides any provisional treatment; a plausible allowance is not an accepted allocation
Revision and approvalClarification, revised scope and reviewer dispositionUpdate the affected packages and record who approved the result. A source reference alone does not show that the open question was resolved

The exercise distinguishes three failures that can otherwise look identical on a dashboard: a missing design answer, an unassigned package responsibility and an unsupported estimate carry. Each needs a different next action. A design question goes to the responsible designer, a package choice to the GC's scope authority, and a commitment decision to the commercial approver under the actual agreement.

If software assists with extraction or comparison, ask it to expose the input revision, the disputed scope line and the supporting source. Then inspect whether the cited passage establishes the connection or merely mentions the equipment. This is a proposed proof exercise, not a test performed on a vendor or evidence that a system predicts risk.

Use the archive in a current review

Choose one material decision from your project and circulate its evidence before the meeting. Ask each participant to state whether the document supports the proposed treatment, contradicts it, or leaves it open. Assign an owner and date to resolve an open item. The scope generation and review guide shows how that decision can become a traceable trade responsibility.

The listed event date has passed. Check the organizer's listing if you need to verify the edition or retrieve any subsequently changed agenda material; do not use this page as registration information or as evidence of what speakers ultimately said.

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.