Architectural Flashing Supply
Start a Quote
Scope identification, inclusions and exclusions · Lesson 3 of 4

Scope identification, inclusions and exclusions: methods and worked application

An eight-step review from collecting every addendum to a second-reader check, with worked examples on piece count, girth against AFS’s limits and addenda, and how AFS’s takeoff handles what a drawing does not say.

You will be able to: Run an eight-step scope review on a drawing set and specification, record what was not found, write inclusions, exclusions and clarifications that cannot be misread, and choose a takeoff scope on purpose.

13 min · 12 slides · 10 questions

All lessons in this module
Slide 1 of 12

The eight-step scope review

Collect the documents and every addendum. Sweep for scope terms and record what was not found. Build the scope matrix. Compare the documents and ask. Write the scope. Choose the takeoff scope. Acknowledge addenda and return the marked-up scope. Have a second reader check it.

This is a method assembled for this module from the sources on the next slides. It is not a published standard.

The eight-step scope reviewFlow chart of eight steps from collecting the document set and every addendum to a second-reader check. After comparing documents, a conflict or gap leads to a written RFI that loops back to the scope matrix. After acknowledging addenda, any open addendum means stop.Collect the set andevery addendum1Sweep for scope terms;record what is not found2Build the scope matrix3Compare documents;ask about conflicts4Write inclusions,exclusions, clarifications5Choose the takeoff scope;read what it left out6Acknowledge addenda;return the marked-up scope7A second reader checks8AFS Bid-SetAssistantAFS takeoffscope choiceConflictor gap?yesRFI in writingif clearAddendumopen? Stop.

Flow chart of eight steps from collecting the document set and every addendum to a second-reader check. A conflict or gap after comparing documents leads to a written RFI that loops back to the scope matrix. An open addendum after step 7 means stop.

1
Collect the set and every addendum
2
Sweep for scope terms and record what is not found
3
Build the scope matrix
4
Compare the documents and ask about conflicts
5
Write inclusions, exclusions and clarifications
6
Choose the takeoff scope and read what it left out
7
Acknowledge addenda and return the marked-up scope
8
A second reader checks
Every conflict or silence becomes a written question, not a guess. The method is assembled for this module; it is not a published standard.

Sources

Glossary

Scope matrix
A table with one row per item and columns for the drawing sheet, specification section, who furnishes, who installs, by others, basis and question. A working tool defined in this module, not a published form.
Scope directive
The AFS takeoff’s setting that limits what it reads: Full Takeoff, Roof Only, Flashing & Components Only, Roof + Flashing Combined, or Custom text of up to 300 characters.
Addendum
A written change to the bid documents issued before bids are due. Under FAR 52.214-3 bidders shall acknowledge receipt of any amendment.
Not found
The AFS Bid-Set Assistant’s status for a scope term it did not find on any sheet. It says to confirm with the architect before leaving the item out.
Allowance
An amount or quantity carried in a proposal where the documents lack detail. ASAMW says any allowances assumed need to be qualified and included in the scope.
Splice lap
The overlap at a joint between two pieces in a run. AFS’s piece-count rule gives up the lap at each joint after the first piece.