Construction Documentation Development and Administration
The Construction Documentation Development and Administration domain tests how contract documents are assembled, issued, changed, and closed out over a project's life. Expect questions on the composition of the Project Manual, the division of information between drawings and specifications, document control during bidding and construction, and the administrative instruments - addenda, RFIs, submittals, change orders - that keep the record reliable.
What the contract documents are
- The Contract Documents typically comprise the Agreement, the general and supplementary Conditions, the Drawings, the Specifications, and all addenda and modifications. The Project Manual packages the procurement requirements (Division 00), the conditions, and the specifications; drawings are usually issued separately but are equally part of the contract.
- Drawings carry location, dimension, quantity, size, and relationships between components. Specifications carry quality, standards, workmanship, and submittal and closeout requirements. Neither substitutes for the other.
- MasterFormat organizes work results (Divisions 00 through 49). UniFormat organizes building elements and systems and is used for early design, cost estimating, and preliminary project descriptions.
Administration across phases
- During bidding, revisions are issued as addenda; each addendum becomes part of the contract and must be acknowledged.
- After award, changes move through change orders, construction change directives, or written field orders - never through marked-up drawings handed across a table.
- A submittal register, an RFI log, and a distribution matrix are your control instruments. They answer: who received which version, and when.
- Closeout administration (record documents, warranties, O&M data, final payment) begins at award, not at substantial completion.
Worked example
A drawing note reads "2-hour rated corridor wall," while Section 09 21 16 describes a 1-hour assembly. The contractor installs the 1-hour board and fails inspection. Reasoning: the documents conflict, and a contractor is expected to report a discrepancy before proceeding rather than resolve it alone. Absent a project-specific order-of-precedence clause, the more stringent requirement generally governs, and a unilateral choice is at the contractor's risk. The correct sequence is RFI, written interpretation from the design professional, confirmation of cost and time effect, then proceed.
Traps that cost marks
Assuming one document family outranks another by default; treating a verbal direction as an executed change; forgetting that addenda and modifications are themselves contract documents; confusing UniFormat with MasterFormat; and losing version control so two crews build to two different revisions.