Architectural Flashing Supply
Start a Quote
Project lifecycle and contract documents · Lesson 3 of 4

Project lifecycle and contract documents: methods and worked application

A five-step intake for a bid set, reading what was not found, piece counts for a long run, a submittal clock, a notice calendar and a payment date, and how an AFS submittal package labels what is not established.

You will be able to: Run a five-step document intake on a bid set, test a flashing run against AFS fabrication limits, build a submittal timeline, and compute a notice date and a payment date, recording every assumption and unit.

12 min · 11 slides · 9 questions

All lessons in this module
Slide 1 of 11

A five-step document intake

A method for this course, not taken from any one contract:

  • List every document and its date, addenda included.
  • Find the precedence clause and the submittal section.
  • Pull flashing scope from Section 07 62 00 and related sections, and list the terms not found.
  • Test each run and profile against AFS limits.
  • Write the register entry and the notice calendar.

Glossary

Document intake
This course's name for the first pass over a bid set: list every document with its date, find the precedence and submittal clauses, pull the flashing scope and note what was not found, test runs against fabrication limits, and calendar the dates.
Splice lap
The overlap where two lengths of a long run join. AFS says to add any splice lap the project specifies when a run is split into pieces; the lap itself comes from the project documents.
Not established
A status on an AFS submittal checklist line meaning no AFS register holds the value; the value reads "Not established - request from AFS" rather than being filled in.
Business day
A working day, usually Monday to Friday. The VA counts submittal review in business days, so 30 business days is about six weeks of calendar time when there are no holidays.