about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Closure is the most skipped process in real organizations and one of the most reliably tested on the
exam. The reason is simple: everything valuable that a project produces beyond the deliverable itself (the lessons, the historical estimating data, the clean contract file, the operations handover) is
produced during closure or not at all. A project that ends when the crew drives away has delivered a
house and thrown away everything the organization could have learned from building it.
The most important rule to memorize: every project is closed formally, including a project
that was cancelled. Termination changes what you document, not whether you close.
Closure runs in order: acceptance and contract settlement come first, then the
administrative steps of releasing the team, capturing lessons, and archiving and transitioning the
work.
Two kinds of closure
Contract (procurement) closure
Administrative closure
Scope
Each individual contract or purchase order
The project or phase as a
whole
Key activities
Verify all contracted work is complete and acceptable, settle claims,
release retainage, issue final payment, provide formal written notice of contract completion
Obtain final acceptance, close out financials, release resources, capture lessons learned,
archive records, transition the product to operations
Sequence
Happens first: contracts are closed before the project can be
administratively closed
Skipping lessons learned; releasing the team before punch list is
finished
Two supporting activities live inside contract closure. A procurement audit is a
structured review of the whole procurement process, from solicitation through administration, to
identify what should be repeated or avoided next time; it examines the process, not the
contractor's morals. Claims administration is how contested changes and disputed
payments are documented, processed, and settled, ideally through negotiation, using the dispute-resolution
mechanism the contract itself specifies.
Final acceptance is the hinge
Nothing else in closure proceeds until the deliverables have been verified against the requirements and
formally accepted by the customer or sponsor in writing. For GCHS that means the punch list is
complete, the final inspection has passed, and the homeowner or the county has signed the acceptance
document. Verification is the technical step (does it meet the requirement?); acceptance is
the authoritative step (the customer says so on paper).
Situational tell
If a closure question describes an outstanding punch item, an unverified requirement, or a
contractor's unresolved claim, the correct answer is essentially never “proceed with closure and
note the exception.” Resolve it, get acceptance, then close. Closing over an open item hands the
problem to a homeowner who has no way to escalate it.
Lessons learned and organizational memory
PMI's expectation is unambiguous: lessons learned are captured throughout the project,
not manufactured in a two-hour meeting at the end when half the team has already rolled off. At closure
the accumulated register is finalized and transferred into the lessons learned repository,
which becomes an organizational process asset for future projects. That repository is what
makes next year's analogous estimate credible.
Also updated at closure: templates and checklists that proved useful, historical cost and duration data
for the estimating database, risk categories that turned out to matter, and supplier performance
information. Adaptive teams reach the same destination by a different road: they hold a retrospective
every iteration and a release or project retrospective at the end, so improvement is continuous rather
than terminal. The predictive lessons-learned session and the agile retrospective share a purpose;
they differ in frequency and in how quickly the findings are acted on.
Transition to operations and benefits realization
A rehab that is finished but not properly handed over is not finished. Transition includes:
As-built drawings and specifications: what actually got installed, not what was
drawn.
Operations and maintenance manuals, warranties, and equipment registrations: with
clear dates and contact points.
Training for the homeowner or the operating team: how the new heat pump thermostat
works, how to maintain the ramp surface, who to call in the warranty period.
Open items and residual risks transferred with a named owner. Risks do not
evaporate at closure; they change hands.
Transition or exit criteria: defined back in planning, not improvised at
the end, so everyone knows what “ready to hand over” means.
Benefits realization usually outlives the project. Whether a retrofit actually reduced
a family's utility burden or allowed someone to age in place is measurable months or years later, long
after the project manager has moved on. The PM's closure responsibility is to hand the benefits management
plan, the measurement method, and the baseline data to the sponsor or benefits owner who will track them, not to certify benefits that have not happened yet.
Key points
Close contracts first, then close the project administratively.
Final acceptance is in writing, from the customer or sponsor, and it gates everything after it.
Lessons learned are captured continuously and archived at closure as an organizational process
asset.
Release resources after the work is accepted, and recognize the team's contribution when
you do.
Cancelled projects are closed formally too, documenting why, what state the deliverables were left
in, and what was learned.
Releasing resources, archiving, and the human side
Releasing the team too early is a classic error: the punch list stalls because the people who know the
job are gone. Release resources as their work is accepted, update their performance records and skill
inventories, return equipment and unused materials, and mark the ending: recognition at closure is a real
project management responsibility, not a nicety, and it materially affects whether good people volunteer
for the next one.
Archiving is the least glamorous and most audited part of closure. Project records, contracts, change
logs, inspection reports, financial documentation, and the final report go into the organization's
retention system according to its retention policy, which for federally funded housing work is typically
years, not months. If it is not archived, it did not happen.
Sustainable and responsible closeout
Closeout is where a surprising share of a project's environmental footprint is decided. Surplus
materials can be donated or returned rather than landfilled; demolition debris can be sorted and diverted;
fixtures, appliances, and cabinets can be routed to a ReStore instead of a dumpster; regulated materials
such as lead-painted components, refrigerants, and old ballasts have disposal requirements that are legal
obligations, not preferences. Recording diverted tonnage and disposal compliance in the closure
documentation gives the organization real ESG data instead of good intentions.
Do not do this
Do not let a sponsor's eagerness to start the next job cause you to skip closure. If pressure comes,
explain concretely what is lost (unsettled retainage, an unsigned acceptance that undermines the
warranty position, estimating data that will never exist, an operations team that was never trained)
and propose a time-boxed closure plan. Explaining the cost and offering a workable option is the
professional response; quietly abandoning closure is not.
Practice Questions
1. All construction work appears complete on a GCHS rehab. What must the project manager do FIRST before proceeding with the rest of closure?
Conduct the lessons learned session with the full team while the details of the work are still fresh in everyone's mind
Archive the project records
Verify deliverables against requirements and obtain formal written acceptance from the customer or sponsor
Release the crew to the next project so their billable time is not lost while the paperwork is finished
Answer: c. Formal acceptance is the hinge that everything else in closure depends on: until deliverables are verified and signed off, there is nothing to archive, hand over, or celebrate. Releasing the crew before acceptance is the classic error, because the punch list stalls once the people who know the job are gone.
2. What is the correct sequence relationship between contract closure and administrative closure?
Contract closure is optional if the work is complete and the final payment has already been made
Administrative closure occurs first, then each contract is closed once the project file has been archived
Contracts are closed first, then the project is closed administratively
They must occur simultaneously
Answer: c. Each procurement is settled (work verified, claims resolved, retainage released, final payment made, formal written notice issued) before the project as a whole can be administratively closed. Closing the project while a contract remains unsettled leaves financial and legal exposure with no project to manage it.
3. What is the purpose of a procurement audit?
To calculate the final payment amount owed to each contractor after retainage and back-charges are applied, and to close the payment file before closeout
To obtain the customer's formal acceptance
To determine whether the contractor acted in bad faith
To review the entire procurement process from solicitation through administration and identify successes and failures worth carrying forward
Answer: d. A procurement audit is a structured review of the process (how the solicitation, selection, and administration went) so future procurements can be improved. It targets the process rather than the contractor's character, and it is separate from the financial settlement and from customer acceptance.
4. A subcontractor disputes the final payment amount, claiming additional work was directed verbally. What should the project manager do?
Refuse to discuss it and close the contract as-is
Escalate immediately to legal counsel and stop all communication with the subcontractor until a lawsuit is resolved
Pay the disputed amount to close the contract quickly and recover the cost later by withholding the subcontractor's retainage on future GCHS jobs
Follow the claims administration and dispute-resolution provisions in the contract, documenting and attempting to settle by negotiation
Answer: d. Claims administration is exactly this situation: contested changes are documented, processed, and ideally settled through negotiation using the mechanism the contract itself specifies. Paying to make it go away rewards undocumented direction, refusing to engage invites litigation, and jumping to counsel skips the contractual step that usually resolves it.
5. When should lessons learned be captured on a project?
Only when a significant failure occurs
Only if the sponsor requests them
Only at project closure, in a single session
Throughout the project, with the register finalized and archived at closure
Answer: d. PMI expects lessons to be recorded continuously as they are learned, then consolidated and transferred to the organizational repository at closure. Waiting until the end means the details are lost and half the team has already rolled off, which is why end-only sessions produce generic, unusable findings.
6. Where do finalized lessons learned go at project closure, and what do they become?
Into the lessons learned repository, becoming an organizational process asset for future projects
Into the risk register of the current project
Into the contract file for each vendor, becoming part of that vendor's performance record and closed with the contract
Into the project charter, as a historical appendix
Answer: a. The lessons learned repository is an organizational process asset that future projects draw on, and it is what makes the next analogous estimate or risk identification credible. The charter is an initiating document that is not updated at closure, and the current project's risk register is closed rather than extended.
7. At closure, a sponsor asks the project manager to confirm that a completed retrofit reduced the homeowner's utility bills. What should the project manager do?
Extend the project schedule and hold the team and budget open until the utility savings have been proven over a full year
Hand off the benefits management plan, measurement method, and baseline data to the sponsor or benefits owner who will track it
Certify that the benefits were achieved before closing the project
Refuse to discuss benefits since they are outside the project manager's role
Answer: b. Benefits realization is usually measurable only months or years after closure, so the project manager's responsibility is to hand off the plan and baseline data to whoever will track it, not to certify a benefit that has not happened yet. Refusing to engage or stalling closure to wait for the benefit are both incorrect.
8. What should be included in the transition package handed to a homeowner or operations team at closure?
The original design drawings, unchanged, stamped and signed by the architect of record
As-built drawings and specifications reflecting what was actually installed
The contractor's internal punch list only
The project charter and the original project management plan, so operations understands the design intent
Answer: b. As-built drawings capture what was actually built, which is what an operations team or homeowner needs for maintenance and future work, not the original design intent. The charter is an initiating document with no place in an operations handover.
9. How do adaptive teams typically capture lessons compared with a predictive project's single end-of-project session?
Predictive teams hold a retrospective every iteration instead
Adaptive teams never formally capture lessons
Adaptive teams only assess lessons at the very end, like predictive projects
Adaptive teams hold a retrospective every iteration and again at release or project end, reaching the same goal on a different cadence
Answer: d. Adaptive teams reach the same destination as a predictive lessons-learned session by a different road, holding a retrospective every iteration plus a closing retrospective, so improvement is continuous rather than terminal. Both approaches share the same purpose; they differ in frequency and how quickly findings are acted on.
10. Construction on a GCHS unit looks finished, and the sponsor is pushing to move the crew to the next job. The punch list is not yet signed off. When should the crew be released?
Whenever the crew lead judges the job finished and the sponsor agrees the crew is needed elsewhere
At the midpoint of the closure process
Only after the work is verified and formally accepted, not before
As soon as the work visually looks done and the final cleaning has been completed
Answer: c. Releasing the team before acceptance is the classic closure error: the punch list stalls because the people who know the job have already left. Resources are released once their work is verified and accepted, not on appearance or schedule pressure.
11. Why does GCHS archive project records, contracts, and inspection reports according to its retention policy rather than discarding them once the punch list closes?
To satisfy audit and compliance obligations, since federally funded housing work typically requires retention measured in years, not months
Electronic files take up less physical space
Only if the homeowner specifically requests it
Archiving is a courtesy with no real consequence if skipped
Answer: a. Archiving is one of the most audited parts of closure, and for federally funded programs the retention period is typically years; if a record is not archived, an auditor treats it as if the work never happened. It is a compliance obligation, not a convenience.
12. During closeout of a demolition-heavy rehab, which statement about handling materials and waste is correct?
Recording diverted tonnage is just good public relations with no real requirement behind it
Disposal of regulated materials such as lead-painted components and refrigerants is a legal obligation, not a preference
Any leftover material can be landfilled once the project is administratively closed
ESG and sustainability reporting only applies to for-profit companies
Answer: b. Regulated materials such as lead-painted components, refrigerants, and old ballasts carry legal disposal requirements that do not disappear because the project is closing. Surplus materials can often be donated or diverted rather than landfilled, which is good practice, but hazardous-material disposal rules are mandatory.
13. A GCHS rehab loses its funding midway through construction and is terminated. What is the project manager's obligation regarding closure?
Skip formal closure, since no deliverable was completed and there is nothing for the customer to accept or verify
Wait until a future project can absorb the paperwork
Formally close the project, documenting why it ended, the state of the deliverables, and lessons learned
Close only the financial accounts and nothing else
Answer: c. Every project is closed formally, including one that was cancelled; termination changes what gets documented, not whether closure happens. Skipping closure would lose the very information, such as the state of the deliverables and what was learned, that a cancelled project most needs to preserve.
14. A newly installed HVAC system carries a five-year manufacturer's warranty. What happens to that warranty at project closure?
The warranty terms survive closure and are handed off with clear dates and contacts
The warranty ends automatically once the project closes and the final payment is released
The warranty transfers to the project manager personally
The warranty terms are renegotiated at closure
Answer: a. Warranty terms are part of what transitions to the homeowner or operating team, documented with dates and who to contact, and they are exactly the kind of thing lost when closure is rushed or skipped. Closure does not extinguish a warranty; it is when the warranty information must be properly handed over.
Glossary
Final acceptance
Formal, written confirmation from the customer or sponsor that deliverables meet requirements; the hinge that closure depends on.
Contract closure
Verifying and settling each individual procurement, including claims and retainage, completed before administrative closure.
Administrative closure
Closing out the project or phase as a whole: financials, resources, lessons learned, archiving, and transition.
Procurement audit
A structured review of the procurement process, from solicitation through administration, to find what to repeat or avoid.
Lessons learned repository
An organizational process asset holding finalized lessons learned, drawn on by future projects.
Benefits realization
Confirming that a project's intended benefits actually occurred, often measured well after project closure.
As-built drawings
Documentation reflecting what was actually constructed, as opposed to the original design drawings.
Claims administration
Documenting, processing, and settling contested changes or disputed payments using the contract's dispute-resolution mechanism.