Focus area: Closing

The Closing focus area in PMI®'s PMBOK® Guide, Eighth Edition, holds a single process: Close Project or Phase. One process out of 40 makes Closing look minor. In practice it is where owners leave money, records and lessons on the table, because by the time the building is handed over the team is tired, the budget is spent and everyone is moving to the next job. This lesson covers what closing involves, why it happens more than once, and how Northgate's owner team runs it.

Learning outcomes

• Explain what Close Project or Phase covers and why it applies to each phase and contract as well as the whole project.
• Sequence Northgate's (fictional) closing events from Ready-for-Takeover to the end of the warranty year.
• Build an owner's close-out checklist covering acceptance, transition, contracts, money, records, people and lessons.
• Describe how to close a project that ends early.

The lesson

One process, many closings

Close Project or Phase sits in the Governance domain. Its job is to finish the work formally: confirm that what was delivered was accepted, hand it to the people who will use it, settle the contracts and the accounts, release the team, archive the records, capture what was learned, and record whether the project delivered the value it was approved for. The process name says "or Phase" for a reason. A project with several phases closes each one, and each close is a governance checkpoint: did this phase deliver what it promised, and should the next one proceed as planned?

On adaptive work, closing happens at every release. A team closes a release without closing the product. Building projects are usually hybrid, as lesson 4 explained, so the owner may close a design phase, several contracts and a construction phase before closing the project itself. Figure 1 shows Northgate's phase closes.

What a good close covers

Figure 2 sets out the work in the order an owner usually needs it. The order matters. Acceptance comes before transition, because operations should not inherit something nobody has formally accepted. Contracts and money come before releasing people, because the people who know where the open items are should still be on the team when the accounts are settled. Lessons and the value report come last but are planned from the start, because they depend on records kept during the project.

Closing is a governance act

Because Close Project or Phase belongs to Governance, closing is not just administration. Someone with authority, usually the sponsor, has to confirm that the project is done and release the remaining budget and people. Without that decision, projects drift: a small team stays on to "finish a few things", contingency stays committed, and nobody can say whether the project succeeded. A clear close also protects the owner's position. Open claims, outstanding deficiencies and unexpired lien periods should be listed with named owners before the project team disbands.

Lessons learned that change something

Most lessons-learned registers are written once and never read. Two habits help. First, collect lessons as they happen, through the decision log and the knowledge work described in lesson 14, so the close-out session reviews a list rather than relying on memory. Second, end every lesson with an action and an owner outside the project: a change to the owner's tender template, Supplementary Conditions or schedule specification. A lesson with no home is a story, not a lesson.

Value does not close with the project

The project ends at handover, but the benefits it was approved for arrive later. A warehouse delivers value when it ships orders, not when it gets its occupancy permit. Close Project or Phase confirms what can be confirmed at handover and passes benefits tracking to the people who will run the asset, as lesson 7 on the value principle described.

Closing early

Projects are sometimes cancelled, suspended or terminated. The same process applies, with more care. Record why the project stopped and who decided. Secure the site and the work in place. Settle or terminate contracts on their own terms, with legal advice. Capture what was spent and what was produced, because a partly built asset still has value and the next attempt will need the records.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan for Northgate Logistics Inc. (fictional). Halvorsen Builders Ltd. (fictional) builds it under CCDC 2-2020 for $34,950,000; Ridgeline Architects Inc. (fictional) is the Consultant. The owner's construction budget is $38,000,000 including $3,050,000 contingency. See the Northgate fact sheet.

Northgate's closing runs as a sequence of contractual and project events (Figure 3). Ready-for-Takeover and Substantial Performance are both targeted for M9, Friday January 14, 2028. The owner's racking contractor starts on Monday January 17 (M10). Final completion is M11, Friday March 31, 2028. The one-year warranty under GC 12.3 runs from Ready-for-Takeover. The statutory side, including publication of the certificate, lien periods and holdback release, is covered in contracts lesson 7; the owner's lawyer confirms those dates.

View the data

Date	Event	Closing work
Fri Jan 14, 2028	M9: Ready-for-Takeover and Substantial Performance	Construction phase close; warranty starts
Mon Jan 17, 2028	M10: racking and occupancy start	Transition to operations
Fri Mar 31, 2028	M11: final completion	Project close
Sun Jan 14, 2029	Warranty year ends	Facilities warranty review

The owner's close-out checklist turns Figure 2 into named items. The table below shows a selection. Each item has an owner and a "done" test, so the sponsor can see at a glance what is still open on March 31, 2028.

Owner's move

• Plan closing at the start. Put close-out deliverables and the archive structure in the tender documents.
• Close every phase on purpose. Treat M0, M9 and M11 as governance gates, not just dates.
• Keep the team until open items have owners. Release people after the handover list is assigned, not before.
• Give each lesson a home. Change a template, a specification or a Supplementary Condition.
• Get a sponsor decision to close. It releases contingency and stops the project drifting.

Common mistakes

1. Treating Ready-for-Takeover as the end. Final completion, accounts and records still follow.
2. Handing over without acceptance. Operations inherits problems nobody owns.
3. Releasing the team too early. Open claims and deficiencies lose their memory.
4. Lessons-learned theatre. A meeting at the end with no actions changes nothing.
5. Leaving contingency committed. Unused money stays locked away from the next project.

Quick quiz

1. How many processes are in the Closing focus area of PMBOK Guide 8?

   1. 1
   2. 2
   3. 4
   4. 8

2. Which performance domain does Close Project or Phase belong to?

   1. Scope
   2. Finance
   3. Governance
   4. Stakeholders

3. Northgate reaches Ready-for-Takeover on January 14, 2028. What has closed?

   1. The whole project
   2. The construction phase, with close-out still to come
   3. The warranty
   4. Ridgeline's agreement

4. Why should acceptance come before transition to operations?

   1. Operations staff cannot read manuals
   2. So operations does not inherit work nobody has formally accepted
   3. CCDC 2 forbids training before acceptance
   4. Transition is optional

5. Which lesson-learned is most useful?

   1. "Communication could have been better"
   2. "Add a schedule-update specification to the tender template; owner: procurement lead"
   3. "The contractor was difficult"
   4. "Start earlier next time"

Show answers and explanations

1. A. Close Project or Phase is the only Closing process.
2. C. Closing is a Governance process: someone with authority confirms the project or phase is done.
3. B. M9 closes construction; final completion (M11) and project close follow, and the warranty runs on.
4. B. Formal acceptance first means any remaining issues have a named owner before operations takes over.
5. B. It names a specific change and an owner outside the project, so it will actually be used.

Key terms

Close Project or Phase

The single PMBOK Guide 8 Closing process; a Governance process that formally finishes a project or phase.

Phase gate

A decision point at the end of a phase where the sponsor confirms results and authorizes what comes next.

Transition to operations

Handing the finished asset, with its documents, training and warranties, to the people who will run it.

Final completion

On Northgate, milestone M11: all remaining work and deficiencies finished.

Lessons learned

Knowledge from the project recorded with an action that changes future practice.

Early termination

Closing a project before its planned end, with the reasons and state of the work recorded.

References

1. Project Management Institute, PMBOK® Guide, Eighth Edition (product page; published November 2025).
2. Project Management Compass, Inside PMBOK® 8: Governance performance domain.
3. Elizabeth Harrin, Rebel's Guide to PM, Project performance domains explained (updated for PMBOK 8) (January 2026, updated July 2026).
4. Learning Tree, PMBOK® Guide 8th Edition: the complete guide to what's new.
5. Project Together Office, PMBOK 8 focus areas: all 40 processes.
6. Gold Standard Certifications, PMBOK 8 focus areas explained: what happened to process groups (October 2026).
7. PM Exams, PMBOK 8 core governance models, metrics and control processes.

Verified on November 6, 2026.

Next lesson in this trackDomain: Governance