The way a project gets delivered changes everything about how you document it. A traditional Design-Bid-Build set demands a fully prescriptive, complete package before the first shovel hits dirt. Switch to CM-at-Risk with fast-tracking, and suddenly you're releasing bid packages in phases while the design is still evolving. Design-Build flips the architect's position entirely; instead of producing a complete set for competitive bidding, you might prepare bridging documents that define intent while the design-builder's team handles the production drawings. And IPD? The documentation itself becomes a shared, continuously evolving deliverable among owner, architect, and contractor from day one.

Each delivery method carries distinct expectations for drawing completeness, specification type, release sequencing, and risk allocation. The ARE tests whether you can evaluate which documentation approach fits a given project scenario and why. Getting this wrong on the exam, or in practice, means misaligned expectations, change orders, claims, and blown budgets.

This topic covers the documentation requirements unique to each major delivery method, how document phasing and release strategies shift, and the contractual frameworks (AIA A101, A133, A141, A195) that govern what you produce and when. Matching the documentation strategy to the delivery method from the start of design prevents scope gaps, redundant effort, and contractual disputes about what was included in the construction document set.