UPI Study › Courses › Project Management › Free lessons › Lesson 10.2 Free with a free account
Developing a Thorough Project Closure Report
Project Management · Chapter 10: Project Closure and Post-Completion ReviewSection 10.2 · lesson 64 of 7311 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Cost Variance: Definition, Calculation, and Interpretation →← Project Closeout Procedures and Their ImportanceNext lesson: Cost Variance: Definition, Calculation, and Interpretation →
In this lesson
Write an evidence-based closure report and lessons future teams can use.
- Identify the standard sections of a closure report and the evidence each needs
- Rate objectives as met, partly met or not met using measured results
- Rewrite opinion-based statements as evidence-based statements tied to records
- Run a lessons-learned session and write entries with a situation, cause and recommendation
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,550 words). Read along, or search it.
Opening Question
Leading With Budget, Blaming the Weather
The Riverside clinic is closed out, and Priya is drafting the closure report. The build finished within budget, but six weeks later than its forty-week plan. The figures are made up. Helen, the sponsor, would like the report to lead with the budget, and to put the delay down to the weather. It's tempting. Who will read this report, and what should it say about those six weeks?
Purpose
Writing for Readers Who Were Not There
A closure report is the formal record of what a project did, what it achieved, and what it taught. It's written at the end, because only then can the whole story be told, and it's written down, because the people who know it will disperse. Its readers are the sponsor, who needs to know how the money and time were used, and the governing body, which decides whether closure is complete. But most of all, it's for people who never met the project, like the manager of a future clinic build, asking what happened last time. So it must be accurate, complete, and easy to search.
Objectives Versus Outcomes
Met, Partly Met or Not Met
The report has a standard set of sections, each with its source of evidence, and a one-line test a reviewer can apply. The first compares objectives, the results the project set out to achieve, with outcomes, what it actually achieved. Each objective is marked met, partly met, or not met, with a sentence of evidence. Met: the result reaches the target. Partly met: it improves on the start, but falls short. Not met: no improvement. Riverside aimed to cut average patient check-in from nine minutes to three. The result is five. The improvement made is nine minus five, four minutes. The improvement planned was six. Four over six is about sixty-seven percent. So it's partly met, and the report says so, with the number, rather than rounding it up to met or down to not met. And an objective reached by changing its definition midway is reported as changed, not as met.
Report Sections
From Deliverables to Sign-Offs and Open Items
Then the deliverables, each with a dated acceptance behind it. Schedule performance, with planned and actual dates, and the difference. Cost performance, as a short summary pointing to the full cost analysis. Approved changes, each with its reason, approver and effect. Risks and issues: what occurred, how it was handled, and what was never resolved, because the next team needs that. Lessons learned and recommendations, kept apart. A lesson is why something happened. A recommendation is what to do differently. Mixed, they're neither clear observations nor usable instructions. And sign-offs and open items: who approved the closure, and what remains, each item with an owner and a date.
Risks and Issues
Following a Risk as It Becomes an Issue
Two distinctions help in the risks and issues section. A risk is an uncertain event that might happen. An issue is a problem that has already happened, and needs action. A risk that occurs becomes an issue, and the report follows the chain. Risk five, a supplier delay, occurred in week nine and became issue four. It was escalated, and resolved in five days with a backup supplier. A risk that never occurred is worth a line too, because it shows a precaution was effective, or unnecessary. And cross-check counts against the baseline. If fourteen deliverables were baselined and thirteen accepted, the report must account for the fourteenth: deferred to an open item with an owner, or removed by an approved change.
Quick Check
Where a Dropped Rooftop Sign Belongs
Quick check. Priya has this statement for the report: in week thirty, Helen agreed to drop the rooftop sign, saving four thousand dollars. Which section does it belong in? Pause, and decide. Approved changes. It's a formally authorized change to scope, with its approver and its effect. It also explains a gap in the deliverables count, but the change itself is recorded under approved changes. And it's a fact, not a lesson: it says what changed, not why something happened.
Core Rule
Every Statement Traces to a Record
Everything in the report follows one rule: write from evidence. Every factual statement must trace to a record, like the baseline, the change log or the issue log, not to memory or opinion. Memory is selective, especially about an uncomfortable outcome, and an opinion can't be checked by a later reader. Where no record exists, the report says so. Schedule overrun is actual duration minus planned. Riverside's baseline planned forty weeks, and the record shows forty-six. That's six weeks over, and six over forty is fifteen percent. So we ran a little late becomes: the project finished six weeks, fifteen percent, after its planned forty-week duration, according to the schedule baseline and the project record.
Strong and Weak
Statements With Figures, Records and Owners
Here's how that reads in practice. Strong: objective two, cut check-in time, was partly met: the average fell from nine minutes to five, against a target of three, per the two timing samples. Weak: the team worked hard, and the project went well overall. It's an opinion with no record, and it tells a future reader nothing. Weak: communication could have been better. No situation, no cause, no recommendation. Nobody can act on it. Strong: open item, the clinic-finder link on Willowbrook's website is unresolved; owner, the web editor; due, the end of next quarter. Strong statements carry a figure, a record, and an owner or date.
Quick Check
Choosing the Evidence-Based Statement
Quick check. Three draft statements. Stakeholders were very happy with the result. Grace's staff were trained on April twenty-eighth, according to the training log. The budget was a real challenge for the team. Which one belongs in the report as written? Pause, and decide. The training statement. It names what happened, gives a date, and points to a record anyone can check. The other two are opinions. A stronger version would cite a record, like the final cost against the approved budget, from the cost record.
Lessons Session
Preparing and Facilitating a Lessons Review
The lessons come from a lessons-learned session: a structured meeting where the team and stakeholders examine what happened, and agree what should change. First, preparation: gather the records, invite people who saw different parts of the project, circulate an agenda, and set ground rules, like discussing causes, not persons. Then neutral facilitation. Elena, from patient services and outside the build, leads. She doesn't defend decisions, doesn't let one voice dominate, and treats every contribution alike. The session covers what went well, as well as what didn't, because successes can be repeated only if they're understood. And it captures causes, by asking why, until the answer is something that could be changed.
Root Cause
Asking Why Until Something Can Change
Sam recalls a symptom from an earlier job: the fit-out schedule slipped three weeks. Why? Orders were placed late. Why? Approving the order list took too long. Why? The only approver was on leave, and no delegate had been named. That's a cause that can be changed: naming a delegate costs little. Stopping at orders were late would only produce the advice, order sooner. The group stops when it reaches something it can act on, and never stops at a person's name.
Lessons Entries
Situation, Cause and Assignable Recommendation
The session's product is a set of lessons-learned entries. A weak one: communication was poor; communicate better next time. A strong one has a situation, a cause, and a recommendation. Situation: three change requests approved in week twelve reached the supplier in week fifteen. Cause: the change log template had no step for notifying the supplier, and no one was assigned. Recommendation: add a supplier-notification field to the template. The project office template owner does it before the next kickoff. That recommendation is assignable: a named role owns it, and its completion can be checked. Then filing turns a session into learning. Entries are tagged by topic, project type, phase and cause, and stored where other managers can search. A named person reviews them before the next project starts.
Review and Release
Correcting Facts Without Removing Findings
The report is written for readers who weren't there, so it uses plain language, defines its terms, and avoids in-jokes and team shorthand. Before release, the people who hold the records review the draft, and may correct facts. Then the sponsor reviews it, and may ask for clarification. But a reviewer may not remove a finding just because it's unwelcome. A disagreement is settled by pointing to the record, or both views are noted with their evidence. Then the approved report is filed in the archive.
Case Resolved
Tracing Six Weeks to Logged Causes
Back to Helen's request. Priya's reasoning: this report is the record the next clinic build will be planned from, so an inaccurate account would mislead it. So she goes back to the issue log and the baseline. The log shows two weeks lost to a permit delay the project couldn't control, one week to weather, and three weeks to a crew-scheduling gap the project could have prevented. Two plus one plus three is six: the whole overrun. She reports the budget result honestly, as a success. She reports the delay as six weeks, fifteen percent, with each part tied to its logged cause, and a recommendation on crew scheduling. Shown the log entries, Helen agrees. The cost was an uncomfortable conversation and a less flattering report. The gain is a record the next team can trust.
Key Takeaways
An Honest, Searchable Closure Record
To recap: a closure report is written for readers who weren't there. Mark each objective met, partly met, or not met, with evidence and figures. Write from evidence: every statement traces to a record. Each lesson gets a situation, a cause, and an assignable recommendation, filed where others will find it. And a finding stays in the report, even when it's unwelcome.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Developing a Thorough Project Closure Report
How do you decide whether a project objective was met, partly met or not met?
What is the difference between a lesson learned and a recommendation?
How do you find the root cause of a problem in a lessons-learned session?
Why should a closure report be written from evidence rather than memory?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →