Inspection Documentation, Codes, and Project Specifications
Documentation Purpose
Inspection records must be accurate, timely, and traceable. Each observation should identify the location, the condition, the specification or code reference, the disposition, and the follow-up. Photographs should be dated and labeled. Daily reports should distinguish conforming work, nonconforming work, and work not yet inspected.
Codes and Specifications
Know the hierarchy: the adopted building code sets minimum requirements, the project specification and manufacturer instructions set the actual requirements, and the more stringent governs where they conflict. EIFS requirements often appear in the code's exterior wall provisions and in referenced standards for water resistance and installation. Specifications typically govern substrate tolerances, materials, mockups, and testing.
Traps
Common traps include citing a code section that does not apply, accepting a manufacturer's generic detail over the project-specific detail, and documenting a verbal direction without confirming it in writing. Another trap is failing to record a nonconformance because it was corrected on the spot; the record should still show the observation and correction.
Worked Example
If field work conflicts with the specification, the correct action is to stop, document the conflict, and request a clarification from the design professional rather than choosing one document. Record the date, the condition, and the request.
Rule of Thumb
Write each entry so a reader who was not on site can locate the condition and understand what was required, what was found, and what happens next.