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

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.

12 min · 11 slides · 9 questions

All lessons in this module
Slide 1 of 11

Five common document defects

Each has a documented correction and a record that proves it.

  • A drawing and a specification disagree.
  • An addendum is missing from the set you quoted.
  • "Approved as noted" is treated as "Approved".
  • A spoken direction is never written down.
  • "The architect approved it" is read as a release.

Glossary

Approved as noted
A VA notation on a returned submittal: the contractor may proceed only if it incorporates the noted comments and makes the noted corrections. A drawing released without the note has not been approved as noted.
Punchlist
In the UT System general conditions, a list of items of Work to be completed or corrected by the contractor before Final Completion.
Record Documents
In the UT System general conditions, the drawing set, specifications and other materials the contractor maintains to record addenda, changes and the as-constructed conditions of the Work.
Written notice of a change
Under FAR 52.243-4, direction other than a written change order counts as a change only if the contractor gives written notice that it regards the direction as one, and then asserts its adjustment within 30 days.