Architectural Flashing Supply
Start a Quote
Product selection and substitutions · Lesson 3 of 4

Product selection and substitutions: methods and worked application

A step-by-step method for comparing a proposed product with a specified one, four worked examples with every input sourced, the review clock in one owner’s template and what a request packet holds.

You will be able to: Produce a documented substitution comparison with sourced inputs, units, assumptions and inspection points, and read the review clock and request packet.

12 min · 11 slides · 9 questions

All lessons in this module
Slide 1 of 11

Six steps of a documented comparison

1 Read the specification and list every attribute it names. 2 List the proposed product’s values with units. 3 Compare and mark each attribute. 4 Record assumptions and missing evidence. 5 Assemble the request. 6 Send it and wait for the decision.

This order is built from the University of Houston request contents and AFS's four statuses; neither source fixes a sequence.

Substitution request pathA flow of a substitution request. 1 The contractor finds a need, a substitution for cause. 2 A written request with a comparison of significant qualities. 3 The architect checks the conditions: documents, schedule, warranty, compatibility, approvals; where a code alternative is involved the authority having jurisdiction approves. 4 The architect decides; if more information is needed the request returns to step 2. Accepted by Change Order, Construction Change Directive or Architect’s Supplemental Instructions, or rejected, or no decision in time and the specified product is used.A substitution request, step by stepOne owner’s template; your contract rulesContractor finds a need(a substitution for cause)1Written request with acomparison of significantqualities2Architect checks the conditions:documents, schedule, warranty,compatibility, approvals3Where a code alternative isinvolved: approval by theauthority having jurisdictionMore informationneeded?4YesNoArchitect decidesAccepted: Change Order,Construction Change Directive,or Architect’s SupplementalInstructions (minor changes)Rejected, or no decision intime: the specified productis usedor

A flow of a substitution request. 1 The contractor finds a need, a substitution for cause. 2 A written request with a comparison of significant qualities. 3 The architect checks the conditions: documents, schedule, warranty, compatibility, approvals; where a code alternative is involved the authority having jurisdiction approves. 4 The architect asks whether more information is needed; if yes the request returns to step 2. Then the architect decides: accepted by Change Order, Construction Change Directive or Architect’s Supplemental Instructions, or rejected, or no decision in time and the specified product is used.

1
The contractor finds a need for a change
2
A written request with a comparison of significant qualities
3
The architect checks the conditions
4
The architect asks whether more information is needed
The path in the University of Houston template, Section 01 25 00 (one owner’s template; your contract rules).

Sources

Glossary

Evidence missing
An AFS comparison status meaning the specification asks for proof, such as a standard, a test or a coating class, that AFS does not hold yet.
Request packet
The documents sent with a substitution request: a comparison of significant qualities, product data, samples, test reports, similar installations, schedule and cost effects, and the contractor’s certification.
Review clock
The days a contract gives the architect to ask for more information and decide on a request; in one owner’s template, seven days to ask and 15 to decide.
Form of acceptance
The written instrument that accepts a substitution: a Change Order, a Construction Change Directive, or Architect’s Supplemental Instructions for minor changes.