How to build a project closure presentation: the 10-slide template, the variance arithmetic and a lessons ledger with owners

Disclosure: NOXI publishes this guide and is one of the tools it mentions; the method works in any presentation software.

Closure decks usually fail in one of two ways. Some turn into a thank-you slideshow: a photo of the team, a list of features and a cake. Others turn into a blame session, where a cost overrun is discussed for forty minutes and nobody leaves owning anything. Neither gets the project closed, because neither asks the sponsor to sign a specific decision.

This guide builds the deck around those four questions. It gives you a 10-slide template, a 60-minute closure meeting agenda, a planned-vs-actual scorecard with every formula shown, a variance bridge that separates approved changes from unplanned spend, a benefits handover slide, a lessons-learned ledger with owners and due dates, a version for cancelled projects and a pass/fail closure checklist. The worked example is fictional: Northgate Supply, a distributor rolling out a warehouse management system (WMS) to three sites. Every number is invented for teaching and every result is calculated in the open, so you can check it or rerun it with your own figures.

What a project closure presentation is: the four questions

A project closure presentation is the slide deck shown at the final governance meeting of a project, where the sponsor confirms what was delivered, accepts the final cost and schedule, hands the benefits to an operations owner and approves the lessons and actions. Its output is a signed decision to close, not applause.

The four closure questions, asked in this order, give the deck its spine:

1. Did we deliver? Scope delivered against the approved scope, and quality against the acceptance criteria.
2. What did it cost and take, and why? Cost and schedule against plan, with every variance explained as either an approved change or an unplanned overrun.
3. Who owns the benefits now? The operations owner, the metric, the current reading and the next measurement date.
4. What changes next time? A short list of lessons, each turned into an action with an owner and a due date.

The order matters. If cost comes before scope, the room argues about money without knowing what the money bought. If lessons come before the benefits handover, the meeting often ends before anyone agrees who measures the results. Close-out has long been the phase teams skip: a February 2000 PM Network column hosted by PMI calls it the phase most project teams forget and splits it into evaluation, lessons learned and sponsor review (PMI, The forgotten phase). The four questions are those three activities, arranged for one meeting.

The closure presentation is the mirror image of the project kickoff presentation. The kickoff turned the goal, scope, success measures and decision rights into agreements; the closure deck reports against each of those agreements. If you still have the kickoff deck, open it first: its success measures become your scorecard rows.

The 10-slide project closure presentation template

A project closure presentation needs ten slides: the outcome in one line, scope, schedule, cost, the variance bridge, quality and acceptance, benefits and handover, lessons learned, what changes next time, and sign-off. Each slide title should state the finding as a full sentence, so the deck reads as a closure report even without a presenter.

Three rules keep ten slides to ten:

• Slide 1 carries the ask. Write the decisions you need on the first slide ("close the project, accept the handover, approve five actions"). The sponsor then reads every later slide as evidence for or against those decisions.
• One number per claim, with its formula nearby. "Two weeks late" means little without the baseline. Put baseline, actual and the formula on the same slide, as in the scorecard below; our guide on how to present data covers labels, units and comparisons in more depth.
• Everything else goes in the appendix or the closure report. The full defect list, the RAID log, the change log and the training records belong in the record, not on the screen.

How many slides for a small project? A two-month internal project can close with four: outcome and scope, cost and schedule on one slide, benefits owner, and lessons with owners. A large programme may need one scope and one cost slide per workstream, but the order of the four questions stays the same.

Project closure vs retrospective vs post-implementation review

A retrospective improves how a team works and happens at the end of every sprint or iteration; a lessons-learned session collects what the project teaches the organisation; a project closure meeting formally ends the project; and a post-implementation review checks months later whether the benefits arrived. They are four different meetings with different audiences, and agile teams often need all four.

The sprint retrospective is defined in the 2020 Scrum Guide as a way to plan improvements in quality and effectiveness; it looks at the team's own process and does not close anything. A project run in sprints still needs a closure meeting, because no retrospective asks the sponsor to accept the cost or name a benefits owner.

In UK central government, this later check is formalised as Gate 5 of the Gate Review process. The current workbook, published by the National Infrastructure and Service Transformation Authority (NISTA) on GOV.UK and last updated on 20 August 2026, describes a first review as the project is about to hand over to business as usual, a follow-up 6–12 months after handover, and a check that a mechanism exists for logging and sharing lessons learned (GOV.UK, Gate Review 5). Even outside government, it is a useful model: the closure meeting starts the benefits clock; the PIR reads it.

Where do the main frameworks stand? PMI's PMBOK Guide, Eighth Edition (November 2025) is built on six principles and seven performance domains, with process guidance reintroduced in what PMI calls a non-prescriptive way. PeopleCert's PRINCE2 7 pages say the method kept its seven processes in the seventh edition and describe them as running from initiation to closure (PeopleCert, PRINCE2 7 Foundation). The deck in this guide works with either: it presents the closure facts both frameworks expect a sponsor to see.

Who attends the closure meeting and what each person signs

The closure meeting needs the people who can accept something: the sponsor, who closes the project; the operations owner, who accepts the handover and the benefits; a user or customer representative, who confirms acceptance; finance, who confirms the final cost; and the PMO, who owns the lessons register. The project manager presents, and team leads join for the lessons section.

If the sponsor cannot attend, do not hold the meeting with a delegate who cannot sign; reschedule it. If a supplier delivered a large part of the work, close their contract in a separate commercial meeting and bring the result to the closure meeting as one line on the cost slide.

The 60-minute project closure meeting agenda

A project closure meeting runs well in 60 minutes when the lessons workshop has already happened with the team: 5 minutes for the outcome and the decisions asked, 25 for scope, schedule, cost and quality, 10 for the benefits handover, 12 for lessons and actions, and 8 for sign-off and thanks. Send the deck as a pre-read two working days before.

Hold the lessons-learned workshop with the team a week before, for about 90 minutes and without the sponsor, so people speak freely. The closure meeting then presents the curated result. Within 24 hours, send a one-page summary: the decisions signed, the final numbers, the benefits dates and the five actions with owners. That summary, plus the closure report, is what the PMO archives.

The closure scorecard: planned vs actual with the arithmetic

The closure scorecard is one table that shows scope, schedule, cost and quality, each with its original baseline, approved baseline, actual result and the formula used. Showing the formula next to the result is what makes a closure deck trustworthy: anyone in the room can recheck the number, and nobody can quietly choose the baseline that flatters the project.

Read the cost row carefully, because it carries the most important rule in this guide. Earned value (EV) at closure equals the budget of the work actually delivered. Northgate delivered all 44 approved requirements, so EV equals the approved budget of $1,270,000, not the original $1,200,000. Measured against the approved baseline, the project overspent by $40,000 and its CPI is 0.97. Measured against the original budget, it is $110,000 over, but $70,000 of that was approved by the sponsor in four change requests and two deferrals. Both views belong on the slide; only the first is the project's performance.

These are the standard earned value formulas. PMI's own explainer, published on 31 August 2026, lists them in one table, CV = EV − AC, SPI = EV ÷ PV and CPI = EV ÷ AC among them, and notes that the method is codified in the ANSI/EIA-748 standard (PMI, Earned Value Management: A Guide to Reading the Numbers). The project status report presentation uses the same numbers month by month; at closure you report the final reading once.

Here are two slides from this article's worked example, as NOXI built them, unedited.

Scope: delivered, deferred and added, shown honestly

The scope slide should show four numbers in one line: original scope, approved additions, approved deferrals or removals, and what was delivered against the resulting approved scope. Deferred items need an owner and a destination, such as a phase-2 backlog, or they disappear after the meeting.

Northgate's scope moved twice, and both moves went through change control:

• Added (+4 requirements, +$95,000). Three requested by the site managers during design (cross-dock workflow, cycle-count scheduling, a returns screen) and one required by a carrier (a new label format). Approved by the sponsor in change requests CR-01 to CR-04; CR-03 also moved the plan by one week.
• Deferred (−2 requirements, −$25,000). Voice picking and a supplier portal moved to a phase-2 backlog owned by the operations director, because neither was needed for go-live. Their unspent budget came off the project.
• Delivered. 44 of 44 approved requirements: 40 original plus 4 added.

A useful format is a single horizontal bar from 42 to 44 with the additions and deferrals labelled, or a short table with the change-request numbers. Avoid the phrase "100% delivered" on its own: the honest headline is "All 44 approved requirements delivered; 2 original requirements deferred to phase 2 by sponsor decision." When scope was cut because money or time ran out, say so in those words; a sponsor remembers a hidden descoping longer than an honest one.

Schedule and cost variance: the formulas and which baseline to use

Report schedule and cost variance against the approved baseline, meaning the original plan plus every change the sponsor approved, and show the original baseline beside it as context. Variance against the approved baseline measures the project team's performance; the gap between original and approved baselines measures decisions the sponsor made.

The last row surprises people. At the end of a completed project, all planned work has been earned, so earned value equals planned value and the schedule performance index returns to 1.0 even for a project that finished late. SPI is a useful signal while a project runs; in a closure deck, report schedule in weeks and dates instead. Northgate's schedule slide shows three dates (planned go-live 12 October, approved 19 October, actual 2 November 2026) and the cause of the two-week slip: the site 3 cutover had to be rerun after a failed data load.

When should a closure deck include CPI at all? Include it when your organisation already reports earned value, or when the audience is a board or finance committee used to it; the board meeting presentation guide covers that audience. For a business audience that has never seen it, the cost variance in dollars and percent is enough, with CPI in a footnote.

The variance bridge: approved changes vs unplanned overrun

A variance bridge is a waterfall chart that walks from the original budget to the actual cost, one bar per cause, with approved changes and unplanned overrun in different colours. It answers the question every sponsor asks at closure, "why did this cost more?", in one picture, and it keeps the decisions the sponsor made separate from the spend nobody approved.

Northgate's bridge, step by step:

Four rules make a bridge credible:

• It must reconcile. The bars add up exactly to the actual cost in the finance ledger. If they do not, finance will find the gap in the meeting.
• One bar per cause, not per cost centre. "Overtime at site 3 cutover" tells the room what happened; "labour, cost centre 4410" does not.
• Approved and unplanned in different colours. Approved changes are the sponsor's decisions; unplanned overrun is the project's variance. Colour is not enough on its own, so label each bar as well.
• Five to seven bars. Group small items into "other, under $5,000 each" with the total. A bridge with fifteen bars is a ledger, not an explanation.

The same structure works for schedule: start at 26 planned weeks, add 1 approved week, add 2 unplanned weeks from the rerun cutover, end at 29. Spreadsheet tools build this as a waterfall chart; if your data sits in Excel, our guide to turning Excel data into PowerPoint slides compares the routes.

Quality and acceptance: criteria met, defects open, who accepted what

The quality slide states how many acceptance criteria were met, which were accepted with conditions, how many defects remain open by severity, and who owns each open item with its due date. Acceptance is a signature from the business, not a test pass rate, so name the people who accepted.

For Northgate, the slide reads as three blocks:

• Acceptance criteria: 11 of 12 met. The twelfth, label printing in under 2 seconds per carton at site 2, measured 2.6 seconds. The site 2 manager accepted it with a condition: a printer driver update due 15 January 2027, owned by the IT service owner.
• Testing: 309 of 312 user acceptance tests passed (99.0%). The three failures were cosmetic and are among the open defects.
• Open defects: 0 critical, 0 major, 6 minor. All six sit in the support backlog, owned by Helen Ortiz, with a fix date of 29 January 2027.

The rule to apply: every open item on this slide has an owner outside the project team, because the project team is about to be released. If the only owner for a defect is the project manager, it is not yet handed over, and the project is not ready to close.

Benefits and handover: the slide that names the owner

The benefits handover slide names the operations owner who will measure each benefit after closure, the metric, its baseline, its target, the latest reading and the next measurement date. Projects deliver outputs; benefits arrive later, in operations, so the closure meeting must hand them to someone who will still be there in 90 days.

Benefits realisation is the work of measuring and securing the improvements a project was funded to produce, such as higher productivity or lower costs, after its outputs are in use. Each benefit needs a metric, a baseline, a target, an owner in operations and measurement dates; the business case is the usual source of the targets.

Northgate's business case promised two operational benefits. The share of each target already reached is (latest − baseline) ÷ (target − baseline):

Three details make this slide work. First, show the share of the uplift, not the raw percentage of target: 112 is 93% of 120, which sounds nearly done, but only 68% of the promised improvement has arrived. Second, put the day-90 date on the slide and in the operations owner's calendar during the meeting. Third, say what happens if the benefit stalls: Northgate's operations director will bring the day-90 reading to the sponsor's monthly review and, if the pick rate is under 116, ask for a short optimisation sprint. If you need the benefit targets in the first place, they come from the business case presentation that funded the project.

Lessons learned without blame: the ledger and the five-lesson rule

A lessons-learned presentation should show five lessons or fewer, each as one row: what happened, why, keep or change, the action, the owner and the due date. A lesson without an owner and a date is an observation, and observations do not change the next project.

Northgate's ledger came from a 90-minute team workshop. Following the affinity method described in the PMI-hosted column cited above, each person wrote what went well and what they would do differently on sticky notes, the team grouped the notes silently and then wrote one statement per group. The result was 23 notes in 6 themes, merged into 5 lessons:

The five-lesson rule is a discipline, not a limit on learning. Keep the full register in the record; put the five that will change something on the slide. Notice that the ledger includes two "keep" lessons. A closure that lists only failures teaches people to hide problems; a closure that names what worked, with the person who made it work, teaches them to repeat it.

To keep the session blameless without making it vague, write causes as conditions, not people: "the rehearsal was skipped to save time" rather than "the site 3 lead skipped the rehearsal." The incident postmortem presentation guide covers blameless wording in depth; the same rules apply here. The ledger columns also match how public repositories record lessons: the NASA Public Lessons Learned System describes each lesson by its original driving event and the recommendations that feed into training, practices and policies.

Turning lessons into changes on the next project

A lesson is learned only when it changes a template, a checklist, a threshold or a kickoff agenda that the next project will actually use. Slide 9 of the closure deck therefore lists each action, the artefact it changes, the owner and the date, and names the meeting where the change will be checked.

The loop closes at the next kickoff. When Northgate starts its next site rollout, the PMO lead opens the kickoff with one slide: "What we changed after the WMS project," listing the five actions and their status. That single slide is the clearest evidence that lessons learned is more than a ritual.

Closing a cancelled or failed project: same deck, different first slide

A cancelled project closes with the same ten-slide structure, but slide 1 records the decision to stop, who made it and why, and the cost slide shows money spent, money not spent and what is kept. Stopping a project that no longer makes sense is a good decision, and the closure deck should present it as one.

The slides change like this:

• Slide 1, the decision. "We stopped the portal on 18 September 2026 because its main customer moved to a new ordering system; $620,000 of the budget is returned." Name who decided and the date.
• Slide 2, what was finished and what is kept. List reusable outputs and who now owns each one.
• Slides 4–5, money. Spent, committed but cancellable, not spent. Treat spent money as sunk: the question for the room is only what the remaining budget does next.
• Slide 7, benefits. Usually "none to hand over", or the partial benefit of the kept assets, with an owner.
• Slide 8, lessons. Focus on how early the signal could have been seen, and on the decision process, not on the people who proposed the project.

Hold the lessons session soon after the decision, while people still remember why they believed in the project, and thank the team by name. People who see a stopped project closed respectfully are more willing to raise the next stop signal early.

Project closure report vs project closure presentation

The project closure report is the full written record that the PMO archives; the closure presentation is the ten-slide version used in the meeting to get the decisions signed. Write the report first or in parallel, then build the deck from it, so both carry the same numbers.

The PMI-hosted column cited earlier recommends a closeout report with an executive summary, the final status report, lessons learned and recommendations, reviewed with the sponsor before it is issued. That is the same sequence the deck follows, which is why the two documents rarely disagree when one is built from the other. A closure deck can also feed an annual review: our year in review presentation guide shows how a portfolio's closed projects become a single results slide.

Project closure checklist: pass or fail

A project is ready to close when ten conditions pass: acceptance signed, benefits owner named, cost reconciled, contracts closed, open defects owned, lessons owned, records archived, access removed, team released and the benefits review booked. If any item fails, close it first or record it as a condition with an owner.

Keep the security-related items concrete: list which accounts, keys and environments were closed and by whom, rather than claiming compliance with a named standard on the slide.

3 AI prompts for a project closure presentation

The fastest way to draft a closure deck with AI is to attach the documents that already hold the facts, such as the last status reports, the change log, the budget spreadsheet and the lessons workshop notes, and ask for the ten-slide structure with every formula shown. Check every number against the source before the pre-read goes out.

How to build the project closure presentation in NOXI

NOXI can turn your status reports, change log and budget spreadsheet into the ten-slide closure deck, in the style of your kickoff deck or company template. It is free, with no card and no watermark; uploading files needs a free account, and a full deck uses about 25 of the 1,000 monthly credits.

Frequently asked questions

What should be included in a project closure presentation?

Ten slides: the outcome and decisions asked, scope delivered against approved scope, schedule, cost with cost variance, a variance bridge, quality and acceptance, the benefits handover with a named owner, five lessons learned, the actions with owners and due dates, and sign-off. Together they answer four questions: did we deliver, what did it cost and why, who owns the benefits, and what changes next time.

How do you present lessons learned?

Show five lessons or fewer in one table with the columns what happened, why, keep or change, action, owner and due date. Write causes as conditions rather than people, include what worked as well as what failed, and add a second slide that maps each action to the template or procedure it changes. Keep the full register in the closure report.

What is the difference between project closure and a retrospective?

A retrospective is a team meeting at the end of each sprint or iteration to improve how the team works; the 2020 Scrum Guide makes it the event that concludes the sprint. Project closure is a governance decision at the end of the whole project: the sponsor accepts the deliverables, the final cost and schedule, the benefits handover and the lessons actions.

What is a project closure meeting agenda?

A 60-minute agenda works for most projects: 5 minutes for the outcome and decisions asked, 10 for scope and schedule, 10 for cost and the variance bridge, 5 for quality, 10 for the benefits handover, 12 for lessons and actions, and 8 for sign-off and thanks. Run the lessons workshop with the team a week before, and send the deck as a pre-read two working days ahead.

How many slides should a project closure presentation have?

Ten slides for a typical project, presented in about 60 minutes with discussion. A small internal project can close with four: outcome and scope, cost and schedule, benefits owner, and lessons with owners. Large programmes add one scope and cost slide per workstream but keep the same order. Detail such as the defect list and change log goes in the appendix.

Who signs off on project closure?

The project sponsor signs the formal closure and accepts the final cost and schedule. The operations owner accepts the handover and the benefits, user or customer representatives accept the deliverables against the acceptance criteria, finance confirms the reconciled cost, and the PMO accepts the lessons register and the archive. The project manager prepares the deck but does not close the project.

How do you close a project that failed or was cancelled?

Use the same ten slides with a different first slide: the decision to stop, who made it, when and why. Show money spent, money not spent and returned, and the outputs worth keeping with their new owners. Treat spent money as sunk, focus the lessons on how early the stop signal could have been seen, and thank the team by name.

What is a lessons learned register?

A lessons learned register is the running record of a project's lessons: what happened, the cause, the recommendation, the action, its owner and its status. It is kept during the project, reviewed at closure, and handed to the PMO, which carries the approved actions into templates, checklists and the next project's kickoff. The closure deck shows only the top five.

What goes in a project handover presentation?

A handover presentation shows what operations receives: the system or product, the support model and runbooks, open defects with owners and due dates, the benefit metrics with baselines, targets and measurement dates, and the named operations owner. In a closure deck it is slide 6 and slide 7; for complex services, run it as a separate session with the support team.

Sources & methodology

How this guide was made: the earned value formulas come from PMI's own explainer; the close-out activities and the closeout report contents from a PM Network column hosted by PMI; the timing of post-handover reviews and the lessons-logging check from the UK Gate 5 workbook; the retrospective definition from the 2020 Scrum Guide; and the framework descriptions from PMI's and PeopleCert's own pages. The four questions, the ten-slide template, the agenda, the two-baseline rule, the bridge rules, the five-lesson rule and the checklist are editorial recommendations, not a standard. Northgate Supply, its people and all figures are fictional; every calculation was checked by hand. All sources were checked on 15 October 2026.

• [1] Close-out as the phase most teams forget; evaluation, lessons learned and sponsor review; the affinity method; closeout report contents and the sponsor review before issue — PMI Learning Library, Martin and Tate, The forgotten phase, PM Network 14(2), February 2000.
• [2] Earned value terms and formulas (CV = EV − AC, SPI = EV ÷ PV, CPI = EV ÷ AC, EAC = BAC ÷ CPI) and the ANSI/EIA-748 standard — PMI, Earned Value Management: A Guide to Reading the Numbers (31 August 2026).
• [3] PMBOK Guide, Eighth Edition: publication date November 2025, six principles, seven performance domains, reintroduced process guidance — PMI, PMBOK Guide product page.
• [4] PRINCE2 7 keeps seven processes, described as running from initiation to closure — PeopleCert, PRINCE2 Project Management Foundation (Version 7); PeopleCert, PRINCE2 7: A Process of Evolution.
• [5] Gate 5: review at handover to business as usual, follow-up 6–12 months after handover, a mechanism for logging and sharing lessons, post-implementation review feeding the assessment; last updated 20 August 2026 — GOV.UK (NISTA), Gate Review 5: operational review and benefits realisation.
• [6] Sprint Retrospective purpose, position at the end of the sprint and 3-hour timebox for a one-month sprint — Schwaber and Sutherland, The 2020 Scrum Guide (November 2020).
• [7] Public lessons repository; each lesson records its driving event and recommendations — NASA Public Lessons Learned System.

Build your project closure presentation in NOXI, free: attach your status reports and budget file, match your kickoff deck's style, and export an editable PowerPoint or PDF.