The Six Sigma Final Report: What to Include and How to Close the Project
The four sections a Six Sigma final report needs, how to write a one-page executive summary a manager can read alone, what a useful lessons-learned entry looks like, and the three closure steps after sign-off.
Most Six Sigma final reports are written in the last week of the project, by a team leader already assigned to the next one, for a sponsor who will read the first page. Those facts decide what the report has to be: short, assembled from records that already exist, and front-loaded so the first page stands alone.
This post covers the four sections a final report needs, the one-page executive summary, what a lessons-learned entry looks like when it is useful, and the closure steps after the report is signed. It assumes a DMAIC project that has reached Control with a validated result.
What the final report is for
The report has two readers. The sponsor and finance need enough to sign off: what the charter promised, what the primary metric did, and what the benefit is worth. The process owner and the next project team need the rest: how the solution works, what keeps it working, and what went wrong.
Six Sigma Study Guide's closure guidance frames the first job as a comparison of outcomes against the project charter, followed by sponsor sign-off and validation of results from finance. If the report cannot be read side by side with the charter, it is not finished. Four sections cover both readers; adding more mostly buries the sign-off material.
The four sections
Executive summary
The executive summary states the problem, the result, and the money on one page. It uses the same primary metric as the charter, in the same unit, with the baseline and the final value both dated. A reader who has never seen the project should finish it knowing whether the goal was met and by how much.
Write it last, after the other three sections exist. The section below covers how to keep it to one page.
Solution and improvements
This section explains what changed in the process and why that change addressed the root cause. It should carry three things: the verified root cause from Analyze, the solution selected in Improve and the alternatives it beat, and the pilot evidence that the solution moved the primary metric before full rollout.
Describe the solution at the level of the process. "Added a second approval queue for invoices over $10,000, worked by AP on a two-hour cycle" tells the process owner what to maintain. "Implemented process improvements to reduce cycle time" tells them nothing. Include the before-and-after process map or say where it lives.
Controls and sustainability
This is the section the process owner will reread six months from now. It records the control plan: the metric that continues to be measured, who measures it and how often, the threshold that triggers action, and the named person who responds when it is crossed. Standardized procedures belong here too, either in full or by reference to the SOP and its revision number.
The test for this section is whether the process owner could run the controls with the project team gone. If a step depends on the Black Belt checking the chart, the plan is not finished.
Lessons learned
Lessons learned record what the next team should do differently. The ISSSP project closure guidance makes two points that matter here: lessons should be captured throughout the project rather than reconstructed at the end, and the section should identify where the solution can be replicated elsewhere in the organization. A project that fixed invoice routing in one region has probably diagnosed the other regions as well.
The one-page executive summary
The summary is a standalone document. It gets forwarded without the report and pasted into program review decks. Five elements, in this order, fit on one page:
- The problem, in one or two sentences, with the baseline figure and its date. Reuse the problem statement from the charter, shortened.
- The goal, as the charter stated it, and the result against it. "Goal: reduce invoice processing from 11.4 days to 5. Result: 4.6 days, measured over eight weeks ending August 15."
- What changed, in two or three sentences. Name the solution, not the methodology.
- The financial result, separated into hard and soft savings, with the annualized figure and the costs netted against it. Note whether finance has validated the number.
- What happens next: who owns the process, what is being monitored, and any replication opportunity.
Numbers appear in the summary exactly as they appear in the charter and the financials. A manager who sees 4.6 days here and 4.8 days on page seven will stop trusting the report. For the distinction between hard and soft figures, see hard savings vs soft savings; the summary should never present the two as one total.
Leave out the tools. Fishbone diagrams and hypothesis test results belong in the body. The summary reports the outcome.
What a useful lessons-learned entry looks like
An entry needs four parts: what the team expected, what happened instead, what the team did about it, and what a future team should do from the start. A single sentence for each is enough.
Weak: "Stakeholder engagement was a challenge and communication should be improved."
Useful: "We expected AP supervisors to attend the weekly review. Two of three stopped attending after week three because the meeting conflicted with month-end close. We moved the review to Tuesdays and attendance recovered. Schedule around finance calendars at Define, not after attendance drops."
The second version can be acted on by someone who was not there. The first cannot. Aim for three to six entries; if the team has twenty, most are observations, and the ones that would change a future project's plan are the ones worth keeping.
Record entries as they occur. A note added at the end of Measure, when the data collection plan had to be rewritten, is more accurate than the same event recalled at close-out. In SixGrid, the Notes area on the Charter tab serves as the running project journal, and the Lessons Learned field on the Report tab is where the entries are consolidated when the report is written.
Writing the report from the project record
Everything except the four narrative sections already exists in the project: the charter, the team list, the metric baseline and final value, and the benefits and costs. Retyping them into a document is where the mismatches described above come from.
SixGrid's Report tab holds exactly the four sections in this post as narrative fields: Executive Summary, Solution and Improvements, Controls and Sustainability, and Lessons Learned. One-click PDF generation combines those four fields with the charter, the project team, the primary and secondary metrics, and the financials as they stand in the project. The team writes four blocks of prose. The rest is pulled from records the sponsor has already been watching, which is what makes the numbers on page one match the numbers on page seven.
Closing the project after the report
Three steps remain after the report is signed. Skipping any of them is how a completed project turns back into an open one.
Hand the control plan to the process owner
The process owner accepts the control plan at the final tollgate, by name, with a date. Acceptance means they have the monitoring schedule, the response thresholds, the SOPs, and the authority to act. Confirm that the first monitoring cycle has actually run under their ownership before the team disbands, because a plan that has only ever been executed by the project team is untested. How to run a DMAIC project covers the Control-phase milestones that lead up to this handoff.
Set the status to Completed
A project that has delivered but still reads Active inflates the active count on every dashboard and will eventually be asked about. Change the status when the sponsor signs the report, not when the team stops meeting.
In SixGrid, the status change is made on the project's Settings tab. Completed projects stay visible on the All Projects page under their own filter, count toward the Completed pipeline on Program View, and keep contributing their financials to the organization's Reports. Their benefit is still on the books.
Archive when the record is no longer needed day to day
Archiving is separate from completing. A completed project remains part of the reporting picture; an archived one is set aside. Archive after the post-project financial review has closed, when nobody needs the project in the list.
In SixGrid, archiving is reversible: an archived project can be returned to Completed at any time and nothing in it is lost. Archived projects are excluded from Program View and its stat cards. Deletion is a different action. Deleting a project moves it to Trash for 30 days, during which it can be restored, and after which it is removed. Archive the project you may need to cite again. Delete only the one that should never have been created.
Frequently asked questions
What should a Six Sigma final report include?
Four sections: an executive summary with the problem, result, and financial benefit; a solution and improvements section with the root cause and what changed; a controls and sustainability section holding the control plan and SOPs; and lessons learned. The charter, team, metrics, and financials are attached or pulled in from the project record rather than retyped.
How long should a Six Sigma project executive summary be?
One page. It should cover the problem with its baseline, the goal and the result against it, what changed, the hard and soft savings with costs netted, and who now owns the process. Keep the analysis tools in the body of the report.
Who signs off on a Six Sigma project closure?
The sponsor or champion signs the report, finance validates the benefit figures, and the process owner accepts the control plan. All three should be named and dated in the report before the project status moves to Completed.