Project lifecycle and contract documents
The steps of a flashing job and who signs with whom, what counts as a contract document and what outranks what, how submittals, payments and notices are timed, and how to read a bid set and keep a record that holds up.
4 lessons · about 55 min · 10 diagrams · 0 videos
Version 1.0.0
Builds on these modules
Related Academy lessons
Lessons
0 of 4 complete
Lesson 1 · 15 min · 12 slides · 13 questions
Project lifecycle and contract documents: principles and terminology
The steps of a flashing job, the three delivery methods, what counts as a contract document, the terms shop drawing, RFI and change order, where flashing lives in MasterFormat, and where AFS fits.
You will be able to: Place a flashing job on the project lifecycle, name who signs with whom, define the core contract-document terms, find flashing in the specification numbering, and say where AFS sits and what a contract cannot move.
Not startedStart →Lesson 2 · 16 min · 12 slides · 13 questions
Project lifecycle and contract documents: materials, standards and design constraints
What outranks what when documents disagree, how submittals are scheduled, reviewed and returned, what AFS can make, and the payment and Texas lien clocks that attach to fabricated material.
You will be able to: Apply a stated order of precedence, explain how submittals are governed and reviewed, compare what an owner and the AFS limits allow, and describe the payment and notice clocks that attach to a fabricated item without treating one owner's wording as universal.
Not startedStart →Lesson 3 · 12 min · 11 slides · 9 questions
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.
Not startedStart →Lesson 4 · 12 min · 11 slides · 9 questions
Project lifecycle and contract documents: defects, verification and case study
Five document defects and their documented fixes, a case study of a coping submittal returned with a note, a checklist of what the record should show, and how closeout documents and warranties tie back.
You will be able to: Diagnose five common document defects, choose the documented correction for each, and say what record proves it, then work a case from a returned submittal to a verified fix and a closeout record.
Not startedStart →
Practical task
Build an intake sheet for a fictional bid set that you invent or that your instructor supplies: list its documents, find its clauses, pull its flashing scope, test one run against AFS limits, and calendar the dates, then say where a late addendum changing a coping gauge must land.
Hand in
- A document list with a date beside every item, addenda included, and a note of which items the contract lists as Contract Documents
- The precedence clause and the submittal clause, each quoted by section number from your own (fictional) documents, with a one-line note of what each says to do
- A flashing scope extract from Section 07 62 00 and related sections, with a second list of the scope terms you looked for and did not find
- A piece-count calculation for one run of your own choosing, showing the run in inches, the AFS maximum of 126 in, the pieces needed and the length of each, with units
- A submittal clock and a notice calendar for the same job, each assumption labelled as from a document, from an AFS register or assumed
- A defect analysis: which of the five document defects the late addendum would cause if missed, the documented correction, and the record that proves it
Rubric
| Criterion | Meets the standard when |
|---|---|
| Document list | Every document carries a date, addenda are included, and nothing is called a Contract Document unless the contract lists it. |
| Clauses | The precedence and submittal clauses are found by section number and paraphrased, and the sheet says whose wording they are rather than calling them a rule for every contract. |
| Scope and silence | Flashing scope is taken from the documents, and the terms not found are listed as questions, not treated as excluded scope. |
| Piece count | The pieces are the run divided by the AFS maximum, rounded up, with units, the standard length distinguished from the maximum, and any splice lap taken from the project documents. |
| Clocks | Review days, fabrication and shipping time and notice dates are separate lines in the same units, with every assumption labelled. |
| Defect and record | The late-addendum defect is named, the documented correction is an RFI or a revised shop drawing, and the record that proves it is listed. |
| Boundaries | The sheet gives no legal advice, signs or waives nothing, and says that contracts do not move safety responsibility. |