KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesClosing the Project: Procurement, Handover and LearningProject Delivery · Principles of Project ManagementLesson 47/58← PrevNext →
GuidePublished 13 Aug 20268 min readBy Kevin Joginproject managementproject deliveryprinciples of project managementclosing
On this page

Ask about this page

KEVOS AIClosing the Project: Procurement, Handover and Learning

KEVOS knowledge first · trusted web sources when needed

Home/ Project Delivery/ Principles of Project Management

KEVOS® Project Delivery Handbook

Closing the Project: Procurement, Handover and Learning

Most project managers are trained to start well. Far fewer are trained to finish well.

8 min read1,577 words Guide 46 of 57Reviewed 2026-08-13
In this handbook article
  1. Why Closing Matters
  2. Close Procurements
  3. What It Is
  4. Contract Administrator Responsibilities
  5. Procurement Closure Activities
  6. Make-or-Buy Analysis
  7. Contract Types — Closing Implications
  8. Close Project or Phase
  9. What It Is
  10. The Closing Workflow
  11. The Project Owner
  12. Key Closing Deliverables
  13. Lessons Learned: The Most Undervalued Closing Activity
  14. What to Capture
  15. The Complete Project Lifecycle — Integrated View
  16. Process Groups Mapped to the Lifecycle
  17. Your Career Beyond the Classroom
  18. Professional Certification
  19. Benefits of Certification
  20. Common Pitfalls
  21. Key Takeaways
  22. Series Conclusion

Source and edition context

Source basis: This handbook article is adapted from the supplied file(s): 47. Closing the Project.md.

Interpretation rule: Named scenarios, schedules, percentages, monetary values and thresholds are source examples or illustrative proposals unless an identified authority, contract or approved baseline makes them mandatory.

PMI edition context: The supplied notes primarily teach fifth- and sixth-edition process groups and knowledge areas. PMI currently publishes the PMBOK® Guide—Eighth Edition, which retains the principles and performance-domain foundation while presenting evolved, non-prescriptive process guidance. Historical counts in this article remain for source/course context, not as a claim about the current edition.

Contracting caution: Contract formation, termination, payment and notice rules depend on jurisdiction and contract terms. In NSW construction work, consult the current Security of Payment guidance and obtain legal advice for an actual transaction.

Career information check: The RegPM certification structure was checked against the AIPM certification pages on 2026-08-13; current eligibility and fees should always be confirmed directly.

Most project managers are trained to start well. Far fewer are trained to finish well. The closing phase is treated as an afterthought — a box-ticking exercise before the team disperses to the next initiative. This is a profound mistake.

Closing is where value is crystallised, where contracts are formally settled, where knowledge is captured, and where the organisation's capacity to deliver future projects is either strengthened or squandered. A project that closes poorly leaves a trail of unresolved contracts, undocumented lessons, and organisational amnesia.


Why Closing Matters

Core Principle: A project is not complete when the deliverables are built. It is complete when the deliverables are accepted, the contracts are closed, the knowledge is captured, and the resources are released.

The Closing Process Group formalises acceptance of the product, service, or result and brings the project — or a project phase — to an orderly end. This can involve commissioning the product and handing it over to the owner for operation.

According to the PMBOK® Guide (5th Edition), the two closing procedures are:

  1. Close Procurements
  2. Close Project or Phase
Process and relationship map
Close — Procurements
Close — Project or Phase
• Contract completion — • Formal acceptance — • Dispute resolution — • Documentation
• Final deliverable acceptance — • Lessons learned — • Resource release — • Archive project records
Relationship details
FromRelationshipTo
Close — Procurementsleads toClose — Project or Phase
Close — Procurementsleads to• Contract completion — • Formal acceptance — • Dispute resolution — • Documentation
Close — Project or Phaseleads to• Final deliverable acceptance — • Lessons learned — • Resource release — • Archive project records

Close Procurements

What It Is

Closing procurements involves settling each contract — including resolving any open items — and formally closing each procurement relationship associated with the project.

Contract Administrator Responsibilities

At formal closure, the contract administrator should provide:

  • Formal notice of project completion to the contractor
  • Formal notice of acceptance to the contractor
  • Internal notice to senior management (buyer side)

Exam Tip: Letters of commendation to all project staff are NOT a required closure activity. The correct combination is items I, III, and IV: formal completion notice, formal acceptance notice, and internal notice to senior management.

Procurement Closure Activities

Activity Purpose
Product Verification Confirm all work was completed correctly and satisfactorily
Financial Closure Reconcile payments, process final invoices, close purchase orders
Lessons Learned Document what worked, what did not, and why
Contract Archive Store all contract documentation for future reference
Formal Acceptance Obtain signed acceptance from the contractor and the buyer

Make-or-Buy Analysis

Note: The make-or-buy analysis is a procurement planning technique (from Phase 2), not a general management technique. It determines whether work should be performed internally or contracted out.

Contract Types — Closing Implications

Different contract types carry different closing considerations:

Contract Type Closing Focus
Fixed Price Verify deliverables meet specifications; final payment against agreed price
Cost Reimbursable Audit actual costs; verify allowable expenses; reconcile fee calculations
Time & Materials Verify hours worked; confirm material costs; reconcile against ceiling price if applicable

Close Project or Phase

What It Is

This process formalises acceptance of the project's final deliverables (or phase deliverables) and brings the project to an orderly end.

The Closing Workflow

Process and relationship map
Verify all deliverables — are complete
Obtain formal — customer acceptance
Transfer ownership — to the project owner
Conduct lessons — learned session
Archive all — project documents
Release project — resources
Formally close — the project
Relationship details
FromRelationshipTo
Verify all deliverables — are completeleads toObtain formal — customer acceptance
Obtain formal — customer acceptanceleads toTransfer ownership — to the project owner
Transfer ownership — to the project ownerleads toConduct lessons — learned session
Conduct lessons — learned sessionleads toArchive all — project documents
Archive all — project documentsleads toRelease project — resources
Release project — resourcesleads toFormally close — the project

The Project Owner

Definition: The project owner is the party that needs the change resulting from the project and who will be its custodian on completion.

The owner is not always the sponsor. The sponsor authorises and funds the project. The owner lives with the deliverable after the project team has moved on. In a zoo relocation, the sponsor might be the city council; the owner is the zoo's operational management team.

Key Closing Deliverables

The final phase produces two primary categories of output:

  1. Project Finalisation — all deliverables verified, accepted, and handed over
  2. Documentation and Reports — lessons learned, final reports, archived records

Lessons Learned: The Most Undervalued Closing Activity

Every project is unique and temporary — which means every project fails or succeeds in its own unique and temporary way. This is precisely why lessons learned are so valuable: they are the mechanism by which organisational knowledge compounds over time.

What to Capture

Category Questions to Answer
Scope Was the scope well-defined? Did scope creep occur? How was it managed?
Schedule Were estimates accurate? Which activities took longer than expected? Why?
Cost Did the project finish within budget? What drove variances?
Quality Were quality standards met? What defects were found and when?
Risk Which risks materialised? Were responses effective? What risks were missed?
Communication Were stakeholders adequately informed? Where did communication break down?
Team What worked well in team dynamics? What would you change?
Procurement Did vendors perform as expected? Were contracts well-structured?

The Uncomfortable Truth: Lessons learned sessions are often skipped because the team is eager to move on, the budget for the project is exhausted, and no one wants to revisit uncomfortable truths. This is precisely why they must be mandated — not optional.


The Complete Project Lifecycle — Integrated View

With all five topics now covered, the full lifecycle can be seen as an integrated whole:

Process and relationship map
Starting — the Project
Organising — & Preparing
Carrying Out — the Work
Closing — the Project
PROJECT — COMPLETE
Relationship details
FromRelationshipTo
Starting — the ProjectProject Proposal — Project CharterOrganising — & Preparing
Organising — & PreparingProject Mgmt Plan — WBS, Schedule, BudgetCarrying Out — the Work
Carrying Out — the WorkCompleted Deliverables — Practical CompletionClosing — the Project
Closing — the ProjectFinalisation — DocumentationPROJECT — COMPLETE

Process Groups Mapped to the Lifecycle

Lifecycle Phase Primary Process Groups Active
Starting the Project Initiating
Organising and Preparing Planning
Carrying Out the Work Executing + Monitoring & Controlling
Closing the Project Closing

Remember: Monitoring & Controlling spans the entire lifecycle — it is not confined to Phase 3.


Your Career Beyond the Classroom

Professional Certification

With the foundations of project management now in place, the next step is professional recognition. In Australia, the peak body for project management is the Australian Institute of Project Management (AIPM).

Current RegPM level Title Typical professional scope
CPPP™ Certified Practising Project Practitioner Contributes to project plans and delivery activities
CPPM™ Certified Practising Project Manager Plans and manages projects and project teams
CPSPM™ Certified Practising Senior Project Manager Manages complex and/or high-risk projects
CPPD™ Certified Practising Project Director Directs projects or manages programs
CPPE™ Certified Practising Portfolio Executive Evaluates projects and programs across an organisational portfolio

Current structure verified from AIPM on 13 August 2026; eligibility and assessment requirements vary by level.

The AIPM RegPM Certification Program is based on National Competency Standards and comprises both a competency-based assessment and an underpinning knowledge assessment.

Benefits of Certification

  • Identify skill gaps and improve capability
  • Achieve industry and organisational PM recognition
  • Inclusion on the AIPM Register of Project Managers
  • Career path from team member → project manager → program director
  • Competitive advantage over non-registered project managers

Current-membership note: AIPM offers a student membership category. Check the official AIPM site for current eligibility, inclusions and fees rather than relying on the older supplied note.


Common Pitfalls

Treating closure as administrative overhead. Closure is a process group with defined outputs and acceptance criteria — it deserves the same rigour as planning.

Skipping lessons learned. Every unrecorded lesson is a mistake the organisation is choosing to repeat.

Informal contract closure. Without formal acceptance notices, disputes can resurface long after the team has dispersed.

Failing to release resources. Team members left in limbo between projects create cost overruns and morale problems. Release them formally.

Not archiving documentation. Project records are organisational assets. Without an archive, future project managers start from zero.

Confusing Close Procurements with Close Project. They are separate processes. You can close all procurements and still have project closure activities remaining.


Key Takeaways

  • The two closing procedures are Close Procurements and Close Project or Phase.
  • At formal closure, the contract administrator provides: formal completion notice, formal acceptance notice, and internal notice to senior management.
  • The project owner is the custodian of the change the project delivers — they live with the outcome after the PM moves on.
  • Lessons learned are the most undervalued closing activity and must be mandated, not optional.
  • The complete lifecycle flows: Starting → Organising & Preparing → Carrying Out the Work → Closing.
  • Monitoring & Controlling spans the entire lifecycle — it is not limited to a single phase.
  • AIPM currently lists five RegPM levels: CPPP → CPPM → CPSPM → CPPD → CPPE; select a level by demonstrated role scope and current eligibility.
  • Check AIPM's current student membership eligibility, inclusions and fees before applying.

Series Conclusion

Across these five articles, we have traced the complete arc of project management — from the foundational frameworks and organisational structures that define the discipline, through the initiation documents that authorise a project, the planning processes that establish the baseline, the execution and control activities that deliver the work, and the closing procedures that formalise acceptance and capture knowledge.

The discipline of project management is not a set of templates to fill in. It is a way of thinking about work — structured, measurable, and continuously improving. Whether you are relocating a zoo, constructing a naval vessel, or deploying a manufacturing line, the principles remain the same.

Master the framework. Apply it with judgement. And never skip the lessons learned.

Continue learning

Lifecycle HandbookCarrying Out the Project Work8 min readSuccess Failure And CloseoutProject Closure and Finalisation6 min readFrameworks Processes And ControlsProject Management Process Groups9 min readLifecycle And Planning FoundationsThe Project Lifecycle: From Concept to Handover9 min read

Prepared for the KEVOS® Knowledge Library. Apply the governing contract, approved project method and current standards to live work.

Continue learning

Carrying Out the Project WorkGuide · Principles of Project ManagementNEXT LESSON →Zoo Relocation Project—Part 1: From CEO Letter to Signed CharterGuide · Principles of Project ManagementOrganising and Preparing the ProjectGuide · Principles of Project ManagementZoo Relocation Project—Part 2: Stakeholder Power and EngagementGuide · Principles of Project Management
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®