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

A final project performance report comprehensively summarizes the project: final performance against scope/schedule/cost baselines (how did we do vs. plan?); how major issues were resolved; lessons learned; deliverable acceptance status. This document becomes part of organizational process assets and provides accountability for project outcomes.

**Why not A:** Financial data alone is far too narrow for an end-of-project performance report. A comprehensive report must also cover schedule performance, scope delivery, issues resolved, and lessons learned. Limiting the report to cost ignores the multidimensional nature of project success.

**Why not C:** Recommendations for the next project are only a small part of what belongs in a final report. The report's primary purpose is to document how this project performed against its baselines, what was delivered, and what was learned — not solely to advise future projects.

**Why not D:** The project charter and stakeholder register are initiating documents, not closing documents. A final performance report summarizes outcomes and results, not the inputs that launched the project. Including only these would provide no information about actual project performance.