Every project delivery method creates a different web of contractual relationships, and those relationships dictate who produces documents, when they are due, and how they flow between parties. A design-bid-build project generates a fully prescriptive set of construction documents before any contractor is selected. A design-build project may require only bridging documents from the owner's design consultant before the design-builder takes over final document production. CM-at-risk introduces a construction manager who reviews and comments on design documents throughout the process, adding layers of constructability analysis and bid package coordination that don't exist in traditional delivery.

For the PjM exam, you need to evaluate which documentation policies apply to a given delivery scenario and judge how shifting from one method to another changes the architect's documentation responsibilities. This means understanding not just what documents are required, but who authors them, who reviews them, and at what project milestones they must be submitted.

The stakes are real. Choosing the wrong documentation protocol for a delivery method can mean missed regulatory approvals, uncoordinated bid packages, or gaps in the project record that expose the architect to liability. Documentation policies also shape how digital data is managed. AIA digital practice documents like E203, G201, and G202 establish protocols for BIM model development and electronic data exchange that cut across all delivery methods but require different implementation depending on the contractual structure.

Getting this right protects the project team, satisfies regulatory requirements, and keeps the construction process moving without avoidable disputes.