I failed a practice PMP question on close procurement vs close project the first time I saw it. Not because I hadn’t read the material — I had — but because the question was asking about sequencing and I’d been thinking about the two processes as basically happening at the same time, in the same closing phase. They don’t. Close procurement happens per contract, throughout the project. Close project happens once, at the end. And close project can’t happen until all the procurements are already closed. Once I understood that sequencing, the exam questions got easier. The actual work got easier too.
Table of Contents
What Close Procurement Actually Is
In PMBOK 6, Close Procurement is process 12.4 — completing each individual procurement. Not the project. Each contract, individually, when that contract’s scope is done.
The activities: verifying all contract deliverables have been received and accepted; settling final invoices, retentions, and performance bonds; documenting any claims or disputes; archiving procurement records. Standard stuff on paper. In practice the final invoice settlement and retention release are the ones that drag — there’s almost always something being argued about.
The thing worth being clear about: a project with five contractors goes through close procurement five times, at five potentially different points in the project. Not five times at the end. Five times when each contract is done.
Why Batching It to the End Is a Mistake
The hospital build I worked on had seven contracts running simultaneously — structural, mechanical, electrical, fit-out, medical gas, fire suppression, and a specialist lift contractor. The mechanical contractor finished their scope in month eight of a twelve-month project. We closed that procurement at month eight: final account agreed, retention released in part, defects liability clock started, contract file closed. Straightforward enough, though the mechanical contractor spent two weeks arguing about a variation claim that I’m fairly sure they’d inflated because they expected us to negotiate down. We settled at about 60% of what they asked. Annoying but resolved.
By month twelve, the mechanical contract was a closed file. When we got to project closure, the only procurements still active were the two contracts that had genuinely run to the end. We dealt with those, then closed the project. The alternative — deferring all seven to the closing phase — would have meant doing simultaneously what we’d spread across four months, with the added pressure of a project closure deadline and a client who wanted the formal completion certificate issued.
I’ve seen that alternative play out on other projects. It’s not a disaster exactly, but it’s unpleasant. Variation claims that nobody can properly remember the context of anymore. Retention release calculations being done under deadline pressure and getting wrong. Contractor representatives who’ve already moved on to other jobs and are hard to reach. The documentation that should be clean and complete is instead pieced together from email threads and call notes from eight months ago. Close it when it’s done.
Close Project: What It Covers and What It Requires
Close project — PMBOK 6 process 4.7 — is the process of formally ending the project. It happens once. Everything: all deliverables accepted by the client, all resources released, all project documentation archived, final lessons learned documented, formal completion certificate issued.
The part people miss: close project has a prerequisite. All procurement contracts must be in a closed state before the project can formally close. You can’t issue a project completion certificate while contracts are still open — there are financial, legal, and audit obligations attached to open contracts that prevent the project from being considered complete. This is the sequencing rule and it’s not optional.
What this means practically: if you get to project closure and discover a procurement that was never formally closed — the contract just… stopped, work finished, everyone moved on, nobody did the paperwork — you have to go back and close it before you can close the project. Which is an annoying situation to be in, especially if the contractor has been paid in full and considers themselves long done with you.
Close Procurement vs Close Project: The Sequencing Rule
Close procurement comes first — both in the project lifecycle and within the closing phase itself. In the lifecycle, procurement closures track contract completions, which happen throughout the project. In the closing phase, any procurement closures not yet done get completed before the final project closure activities happen.
The confusion in PMP prep comes from treating these as two options that happen around the same time, or from the exam question framing that makes it sound like a choice. It’s not a choice. When it comes to close procurement vs close project, procurement closure is a prerequisite — every contract formally closed before the project can be formally ended.
One nuance worth knowing: a project can have multiple procurement closures at different times, but only one project closure. A contractor who finishes in month six gets their procurement closed in month six. Another in month nine. The project closes in month twelve. That’s three closure events — two procurement, one project — and they happen in that order because that’s when the work is done.
| Close Procurement | Close Project | |
|---|---|---|
| Scope | One contract | Entire project |
| How many times | Once per contract — multiple times during the project | Once, at the end |
| When | When each contract finishes or is terminated | After all procurements are closed |
| Key output | Closed contract, final payment, archived records | Formal completion, lessons learned, resource release |
| Prerequisite for | Close project | Project formally done |
Terminated Contracts
When a contract is terminated before completion, close procurement still applies. Same process, worse conditions — you’re doing it while the relationship is broken down, deliverables are disputed, and someone is probably threatening to involve their solicitor. The documentation requirements are identical: what was delivered, what wasn’t, what was paid, basis for termination. The temptation to skip or abbreviate this because the relationship ended badly is understandable. It’s also how you end up in formal dispute proceedings eighteen months later with incomplete records.
“Terminated” is not “closed.” A terminated contract still needs to reach a formally closed state. Outstanding payment obligations, performance security releases, records retention — all of it still applies. The contract ended; the close procurement process didn’t disappear with it.
The PMBOK 6 vs 7 Issue
PMBOK 7 dropped the process-centric model. Close Procurement no longer exists as a named process — neither does Close Project in the same way. PMBOK 7 works through performance domains and principles rather than discrete processes, and the specific process numbers (12.4, 4.7) that appear in every PMP study guide written before 2021 are technically PMBOK 6 references.
This creates genuine confusion for people studying for the current exam, and also for project managers working in organizations where governance documents reference the PMBOK 6 process structure. The work hasn’t changed. Contracts still need to be formally closed; projects still need a formal completion process. The framing and numbering changed. If your organization’s procurement governance says “Close Procurements process,” it still means what it meant — it’s just not what PMI calls it anymore.
For PMP exam prep: questions may still reference the PMBOK 6 process names because a lot of exam material is slow to update. Know both framings — the PMBOK 6 process structure and the PMBOK 7 performance domain approach — and you’ll be fine on either version of the question.
The close procurement vs close project distinction is simpler than it looks on paper: close each procurement when that contract is done, close the project when everything’s done. For PMP exam questions, the sequencing (procurement before project) and the per-contract nature of procurement closure are the two things worth having firmly in your head. The rest follows from those.
For more on how project procurement management fits into the broader project lifecycle, the procurement management article covers the full process from plan through close.
I am a Civil Engineer in HES Consultancy Limited, experience as Director and Resident of Works and Technical, Financial and Administrative Project Audit. I have skills in the area of Procurement, Tenders and Contracting. I am PMP and PRINCE2 Certified. Monitoring and Control with the Earned Value Method.
