Lesson 15 of 16 · Level 4: Expert
Project Closure and Lessons Learned
- ⏱ 11 min read
- ❓ 4 review questions
- ✍️ Exercise with solution
In this lesson
- Follow a closure checklist from formal acceptance to archived files.
- Close contracts properly, including final payments and retainage.
- Write a final report that compares baselines with actual results.
- Run a lessons-learned session that produces changes, not just a document.
- Hand over the result and the benefits tracking to the people who'll own them.
Project closure is the phase where you confirm the work is accepted, settle contracts and payments, release the team, record what you learned and formally end the project. It's the phase most often skipped, because the deliverable is "done" and everyone is already busy with the next thing. That's a mistake: skipped closure leaves unpaid invoices, open warranty questions, unclear ownership and the same mistakes waiting for the next project. In this lesson you'll close the garden center construction job in Dayton, Ohio, which has followed us since the WBS lesson.
- Get formal acceptance
- Close contracts
- Write the final report
- Capture lessons learned
- Hand over and release
Step 1: get formal acceptance
Closure starts when the customer formally accepts the deliverables against the acceptance criteria in the scope statement. For the garden center, those criteria were: all city inspections passed, certificate of occupancy issued, punch list closed and owner walkthrough signed. The certificate of occupancy arrived on Friday, March 26, 2027, two workdays after the baseline date of Wednesday, March 24, and still ahead of the store's April 1 spring opening.
Acceptance must be written: a signed acceptance form or an email from the sponsor that explicitly accepts the deliverables. "Looks great!" at the walkthrough is not acceptance; it's a compliment.
1. What is the first step in closing a project?
Everything else depends on acceptance: final payments, contract closure and handover. Release the team too early and nobody is left to fix the issues the customer raises during acceptance.
Step 2: close contracts and payments
Every contract and purchase order needs to be formally closed: deliverables received, invoices checked against the work, disputes settled and final payments made. In U.S. construction, a common feature is retainage: the owner holds back a percentage of each progress payment until the job is fully complete. The percentage and the release rules come from the contract and can be limited by state law, so always check both.
The garden center contract had 5% retainage on the approved contract value of $304,500 (the original $290,000 plus change request CR-01):
Retainage held = 5% × $304,500 = $15,225
Released when: punch list closed + lien waivers from subcontractors
+ as-built drawings, warranties and manuals delivered
The contractor, in turn, closed its subcontracts the same way: final invoices from the plumber, electrician and HVAC sub, signed lien waivers so no sub can later file a lien on the owner's property, and warranty certificates for the roof and the HVAC units.
2. A contract worth $240,000 has 5% retainage. How much is held back until final completion?
5% × $240,000 = $12,000. $24,000 would be 10%, which some contracts use; the percentage is always set by the contract (within any state limits).
Step 3: write the final report
The final report compares what you planned (the baselines) with what happened, and explains the differences. Keep it short and factual:
| Area | Baseline | Actual | Variance |
|---|---|---|---|
| Cost | $304,500 (incl. CR-01) | $296,800 | −$7,700 (−2.5%) |
| Schedule | Certificate of occupancy Wed, Mar 24 | Fri, Mar 26 | +2 workdays (opening date met) |
| Scope | Original scope + 1 approved change | Delivered; CR-02 rejected, CR-03 deferred to phase 2 | As approved |
| Quality | Pass all inspections; close punch list | All inspections passed; 92 punch items closed | Met |
Where did the cost variance come from? By WBS branch, five came in under baseline and one over:
The story behind the numbers: the foundation ran $2,900 over because the crew hit rock at one corner, which the geotechnical report hadn't shown (an assumption that turned into a risk). Interiors came in $6,400 under, mostly because the new painting sequence from the quality lesson cut touch-up rework. Net result: $10,600 of savings minus $2,900 of overrun = $7,700 under.
3. A project's approved baseline is $150,000 and the final actual cost is $157,500. What's the cost variance as a percentage of the baseline?
(157,500 − 150,000) ÷ 150,000 = 7,500 ÷ 150,000 = 5% over baseline. Always compare against the approved baseline, including approved changes, not the original budget.
Step 4: capture lessons learned that change something
Most lessons-learned documents are never read again. To make yours useful, collect lessons throughout the project (at the end of each phase or sprint, while memories are fresh), then hold a final session of 60–90 minutes with the team and key stakeholders. Keep it blameless: the goal is to fix processes, not to find culprits. Every item answers three questions:
| What happened | Impact | What we'll change (owner) |
|---|---|---|
| Rock under one corner of the foundation, not in the geotech report | +$2,900, +1 day | Add two extra soil borings on sites next to older buildings (estimator) |
| Painting after doors and fixtures cut touch-ups sharply | About −$6,000 in rework | Make it the standard sequence on all interior jobs (operations manager) |
| Owner's change request handled in 4 days with a clear log | No disputes at final billing | Keep the change log template; add it to the kickoff packet (PM office) |
| Permit submitted early used the float on materials delivery | Kept the critical path intact | Submit permits the week the contract is signed (project coordinator) |
Then make sure the changes actually land: update the estimating checklist, the standard schedule template and the kickoff packet. A lesson that doesn't change a template, a checklist or a habit hasn't been learned.
What went well that we should repeat? What didn't go well? What surprised us? What will we do differently next time, and who owns that change? The same four questions work for a construction job, a software launch or a gala dinner.
4. When should lessons learned be captured?
Details fade fast and people leave the team. Capturing lessons at the end of each phase or sprint keeps them accurate; the closing session consolidates them and assigns owners for the changes.
Step 5: hand over, release and celebrate
The last steps make sure the result has an owner and the people have a next step:
- HandoverTransfer to operationsKeys, manuals, warranties, maintenance schedules and as-built drawings go to the store's facilities manager, who confirms receipt.
- BenefitsHand off benefits trackingThe garden center's first-season sales goal belongs to the store owner, not the contractor. Agree on who measures it and when.
- ArchiveStore the project recordsContracts, change log, final report, inspection records and lessons learned, in a place the next PM can find.
- ReleaseRelease the team, with thanksTell managers people are available, give specific feedback for performance reviews and celebrate the finish together.
Before you call the project closed, run the final checklist:
Common closure mistakes
Treating a friendly walkthrough as acceptance.
Get it in writing, against the acceptance criteria.
Releasing the team the day the deliverable ships.
Keep key people until acceptance and handover are complete.
A lessons-learned file nobody reads.
Turn each lesson into a change to a template, checklist or process, with an owner.
Ending projects that were canceled without closure.
Canceled projects need closure too: settle contracts, record why and save what was built.
Practice exercise
The Front Range Fitness member app in Denver has launched. After the earned value review, the sponsor approved a revised baseline of $196,000 (in-app payments moved to version 1.1). The final actual cost is $191,300. The revised launch date was July 30; the app went live on August 13.
(a) Calculate the final cost variance in dollars and as a percentage. (b) Name four closure activities specific to this project. (c) Write one lessons-learned entry using the three-column format.
See solution
(a) 191,300 − 196,000 = −$4,700 → −4,700 ÷ 196,000 = −2.4% (under the revised baseline)
(b) Get the marketing director's (Product Owner's) written acceptance; close the agency contract and pay the final invoice; transfer app store accounts, source code and hosting credentials to the gyms' IT owner; hand the version 1.1 backlog (in-app payments) to whoever owns the app now; agree who will track the benefit (for example, the share of check-ins done through the app).
(c) One example. What happened: the payment API integration took twice the estimated hours. Impact: CPI fell to 0.80 by month 3 and forced a re-plan. Change: on future integrations with an unfamiliar API, run a two-day technical spike before committing to an estimate (owner: agency tech lead).
Summary
- Closure starts with formal, written acceptance against the agreed criteria.
- Close every contract: final invoices, retainage, lien waivers, warranties and documentation.
- The final report compares baselines (including approved changes) with actual cost, schedule, scope and quality, and explains why.
- Collect lessons learned throughout; each one needs an impact, a change and an owner.
- Hand over the result and the benefits tracking, archive the records, release the team and celebrate.
Next lesson: CAPM and PMP Certification: How to Prepare. You'll see the current requirements and exam formats for both certifications and build a study plan.
Create your account in 30 seconds, mark your lessons and download your certificate at the end.