CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Project closeout in a predictive project produces: (1) a final project report summarizing performance against baselines, lessons learned, and final status; and (2) formal acceptance documentation where the customer/sponsor acknowledges that all deliverables were received and accepted. These documents formally close the project and transfer product ownership.

**Why not B:** The scope baseline defines the approved project scope (scope statement, WBS, and WBS dictionary). It is a planning reference document, not a closure document. It does not capture final performance information or transfer product ownership.

**Why not C:** The risk register tracks identified risks and their responses throughout the project. It is a living project document used during execution and monitoring, not a closure document that transfers ownership or summarizes final performance.

**Why not D:** The project charter authorizes the project at initiation. It is not used during project closure to capture performance information or transfer ownership — it serves a fundamentally different purpose at the beginning of the project lifecycle.