CSI Northeast Conference 2026: give a product substitution an evidence trail
Use CSI Northeast product-selection topics to review substitution evidence, design approval, connected trade changes and the complete price of an alternate.
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
- 2 min
- Published
On this page
Keep an unapproved product substitution separate from the base carry. A lower product quote is only a proposed alternative until the responsible designer and owner have the evidence, the project review route is followed, and the estimator has priced the connected trade changes.
The CSI Northeast Region conference was listed for May 14–16, 2026 in Buffalo. Its published abstracts described product selection and competing priorities and coordination of specifications and drawings. They are published topics, not evidence of what panelists said or which substitutions were approved. This is independent analysis.
Build a substitution evidence sheet
| Record | Question to answer | Owner or decision |
|---|---|---|
| Specified basis | Which issued drawing, section, product and revision define the base? | Estimator records source |
| Proposed product | What differs in dimensions, performance, installation and warranty? | Supplier provides comparison and supporting data |
| Retained requirements | Which project functions and test evidence must be demonstrated? | Designer identifies review needs |
| Review route and status | What submission and approval process does this contract establish? | Design lead tracks formal response |
| Interfaces | Which adjacent trades, supports, seals, testing or sequencing change? | Package leads identify scope and quotes |
| Time and price | What lead time and complete added and deleted work are assumed? | Estimator records separate base and alternate |
Do not assume a universal right to substitute or a hierarchy between specifications and drawings. Read the actual contract, its substitution procedure and any clarifications. A product data sheet is evidence for review, not itself an approval. If the supplier's comparison is incomplete, request the missing test reports, details or installation constraints and show the alternative as unresolved.
Worked envelope example
In a fictional facade package, a supplier proposes a different exterior panel at a lower material price. The issued basis calls for a particular assembly; the proposed panel changes thickness and attachment spacing. The GC asks the supplier for assembly performance and attachment information, the facade designer to review the formal submission, and the installer to price revised supports and edge details. The sealant trade must also check its interface. The scheduler compares procurement lead time only after allowing for the project-specific review route.
Until the authorized response arrives, retain the specified assembly as the base estimate and report the proposed panel as a separate conditional alternate. If accepted, preserve the response and revised scope basis; update the relevant packages and estimate together. A product saving without the support, sealant and review consequences is not a complete comparison. The value-engineering guide develops that full comparison, while the specification review helps locate obligations that cross trade boundaries. Use the project's formal clarification process and connect the answer to the affected number as described in prebid RFI review.
For an enclosure alternate, the Facades+ New York 2027: assign enclosure mockups, tests and acceptance before bid day extends the review to specimen, access, correction, retest and acceptance evidence.
Keep the changed scope traceable
Piper's Scope Generation turns project requirements into trade scopes with source-linked findings. That can support review of affected scope; it does not approve a substitution. The responsible project parties retain that decision. The conference selection guide puts this historical specialist event alongside other choices.
Related reading
Construction value engineering: compare the complete alternative, not one cheaper item
A value-engineering proposal can shift scope across trades. A comparison of checking function, interfaces, schedule, costs and approval before savings.

Construction specifications and MasterFormat: section numbers do not define trade scope
MasterFormat organizes project information; it does not assign work to a bidder. A method for turning specification requirements into trade packages.

Construction RFIs: connect the answer to the scope and number it changes
An answered construction RFI can leave the estimate stale. Review tracing clarifications into trade scope, proposals, pricing and approval records.

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.