HKSM

A formal, approved summary of a project or phase at closure that captures performance against objectives and key results. It records what was delivered, how it performed versus plan, and essential closure outcomes for governance, audit, and transition.

Key Points

• Produced during Close Project or Phase and approved by the sponsor and governance body.
• Concise executive-level summary of results, not a detailed log.
• Covers objective attainment, scope completion, schedule and cost performance, quality results, benefits status, acceptance, procurement closure, and final risk/issue disposition.
• Becomes the authoritative closure record used for audit, archival, and organizational learning.

Purpose

• Document closure decisions and demonstrate that the project or phase met agreed acceptance criteria.
• Provide a clear record of actual performance versus baseline to support accountability and future estimating.
• Enable smooth transition to operations, benefits realization tracking, and financial and contractual closeout.

How to Create

Compile verified data, analyze variances, and present concise findings with approvals.

• Collect inputs: project management plan and baselines, performance data and reports, change log, risk and issue logs, quality reports, test results, acceptance records, procurement and contract files, business case, and benefits management plan.
• Analyze results: variance and trend analysis, earned value performance, schedule and cost indices, quality outcomes, final risk/issue disposition, and supplier performance.
• Structure the report: executive summary, objectives and acceptance, scope/deliverables completion, schedule summary, cost/financial summary, quality results, change summary, risk/issue closure, procurement closure, benefits status and handover plan, transition readiness, compliance/audit notes, and approvals.
• Validate facts with workstream leads, finance, procurement, and quality; then obtain sponsor/governance sign-off.
• Ensure clarity and traceability with references to source documents and version control identifiers.

How to Use

• Secure final acceptance and formal closeout decisions from the sponsor and governance board.
• Trigger operational handover, service introduction, knowledge transfer, and support arrangements.
• Authorize financial close: finalize accruals, release reserves and retentions, and close charge codes.
• Confirm procurement closure and supplier performance evaluations.
• Feed organizational process assets: archive records and inform estimating databases and playbooks.

Ownership & Update Cadence

• Owner: Project manager. Contributors include workstream leads, finance, procurement, quality, and business owner.
• Approvers: Sponsor and, where applicable, PMO or steering committee.
• Timing: Created at the end of each phase or the entire project. Once approved, it is baseline and typically not revised; any post-closure clarifications are added as controlled addenda. Benefits updates occur in separate benefits realization reports.

Example

CRM Upgrade Project — Final Report (Executive Summary Excerpt)

• Objectives and Acceptance: All eight prioritized capabilities delivered; sponsor sign-off received on 15 Aug; UAT pass rate 97%.
• Schedule Performance: Baseline finish 10 Aug; actual finish 14 Aug; SPI 0.96; primary variance due to data migration defects resolved in Sprint 6.
• Cost Performance: BAC 1.20M; EAC 1.18M; CPI 1.03; final actuals 1.17M with 30K contingency unused.
• Quality Results: 1,240 test cases executed, 28 critical defects fixed, zero open critical defects at close.
• Risks/Issues: 112 risks tracked; all closed or transferred; two residual risks handed to operations with mitigation plans.
• Procurement: SaaS subscription contracted; implementation partner contract closed; all deliverables accepted and retentions released.
• Benefits Status: Year-1 forecast uplift 8% in lead conversion; early indicators at 6%; benefits owner assigned and tracking via benefits register.
• Transition: Knowledge transfer completed; support runbook approved; hypercare active for 30 days post go-live.
• Approvals: Sponsor, PMO Director, and Procurement Manager approvals recorded in Doc ID FR-2025-018.

PMP Example Question

At project closure, the sponsor asks for a concise document summarizing actual scope delivered, schedule and cost performance, final acceptance, and procurement closure to archive for audit. What should the project manager provide?

1. Project management plan.
2. Final report.
3. Lessons learned register.
4. Work performance data.

Correct Answer: B — Final report.

Explanation: The final report summarizes performance against the plan and key closure outcomes in an approved, archival document. The plan outlines how work is managed, the lessons learned register captures insights, and work performance data are raw measurements.