PRINCE2 7 End Stage Report – reporting the PRINCE2 stage end
A new management stage commences once the project board have read the project manager’s end-stage report, given their approval for the next stage plan, set stage Tolerances, and advised the project manager how often they wish to receive their regular Highlight Report. It does not have to be a meeting – but it is usually the best way to communicate the project status.
Evaluate the stage
The results of a stage should be reported back to the project board so that progress is clearly visible
to the project management team.
The project manager gives a view on the continuing ability of the project to meet the project plan
and business case and assesses the overall risk situation. This activity should happen as close as
possible to the actual end of a stage.
Recommended actions for the project manager:
- based on the performance of the stage using the updated business case, updated project plan, project logs, and any updated management approaches, prepare an end stage report for the current stage.
- review the lessons logged to date and include them in the end stage report. This is particularly important for longer projects where interim reviews of lessons (or the project itself) may benefit the business.
- review the communication management approach to see whether there is a requirement to send copies of the end stage report (and, if appropriate, a lessons report) to the interested external parties.
Request the next stage
The project manager contacts the project board to request to finish the current stage and to
proceed to the next stage. The formal justification can be found in the end stage report and the
next stage plan or the exception plan.
Recommended actions for the project manager:
- brief the project board about the performance of the current stage, an overview of the next stage, and the people and resources required, and confirm readiness to proceed.
- The project manager should also confirm where there have been concessions for any off specifications during the stage.
- seek approval from the project board for the exception plan or stage plan and, if appropriate, the revised project plan, the revised benefits management approach, and the revised business case.
- If the project board does not approve the exception plan, then the current stage continues in accordance with the project board direction until a revised exception plan is approved.
- request authority from the project board to deliver the next stage.
- if appropriate, review the lessons at this time, particularly for longer projects where interim reviews of lessons (or the project itself) may benefit business.
The project board will now manage by exception. Unless the project manager forecasts that tolerance is to be exceeded by giving the project board an Exception Report, then the Highlight Report is usually the only means by which the project will is kept informed.
The end stage report is the project manager’s report given to the project board (any other stakeholders identified in the Communication Management Approach document) just as the stage finishes.
As the current stage comes to a close, it is essential to report to the project board the results of the stage just finished so that the project board can clearly understand the progress achieved – this is done via the end stage report.
As part of this, the project manager will need to present the continuing ability of the project to meet the Project Plan and Business Case, including an assessment of the overall risk situation.
This information in the end-stage report should be presented as close as possible to the end of the current stage to ensure the information is the most recent.
The mechanism for doing this is the End Stage Report which will be created as a result of writing the next Stage Plan, or an Exception Plan, and updating the Project Plan and Business Case.
Typically, the end-stage report summarizes how the stage performed against the plan, what it cost, what its duration was compared to the original plan, and whether the products were of sufficient quality.
No surprises there, then!
Creating the End-Stage Report
Here are the steps that the project manager should take in creating the End Stage Report:
Review the Business Case and capture any benefits already achieved, and in doing so, update the Benefits Management Approach for this information to be included within the end-stage report.
Review the Stage Plan for the stage just finished to ensure that the objectives have been met, and similarly update the Project Plan to ensure that the project-level objectives can still be achieved.
This is also a good opportunity to review the team performance for the stage just finished for the end stage report, and in particular, mention any good performance within the team that deserves recognition.
One of the seven principles that guide PRINCE2 is product focus.
Therefore the project manager will want to review the product status of all products within this stage within the end-stage report and request a Product Status Account from project support.
This will then drive the project manager to review all quality management activities and ensure that all products are complete and approved – also to be included in the end-stage report.
The stage expected a phased handover of some or all of the products created during this stage.
If so, the project manager will want to confirm that the users and operational and maintenance staff have accepted the products and they have been transferred to customer ownership. This, too, is included in the end-stage report.
This may also include identifying any follow-on action recommendations for those products.
The Issue and Risk Registers should be reviewed, and the End Stage Report must include a summary of such issues and risks. The project manager may prepare a Lessons Report to accompany the End Stage Report.
The End Stage Report will be presented to the project board either accompanying the next Stage Plan or an Exception Plan (depending upon whether it is being used to feed an End Stage Assessment or an Exception Assessment) and other revised documentation to seek their approval to proceed by the Project Boards or otherwise.
The project manager will review the Communication Management Strategy to know whether there is a need to send copies of the end-stage report to other stakeholders.
The structure of the End Stage Report
Be careful here. Many end-stage report headings look more complicated than they are. Be prepared to make the end-stage report as simple and light as possible.
Your watchword should be “just enough honest information in the end-stage report to allow the project board to make an informed choice about what to do next.”
The most extensive list of end-stage report sub-set headings is in the ‘Review of Products’ header. Consider what the project board may know from your regular Highlight Reports and keep the details simple.
For example, in most cases, you will find that no products have been handed over to the operational departments, so a simple statement that certain products were approved may be sufficient within the end-stage report because the project board will know that they will have passed their quality criteria before being approved.
Project Manager’s report. How the stage went, a summary of the key statistics here.
Review of the Business Case. The key parts here are the benefits and risks. What are the full benefits/changes? Any benefits that have already been realized. A summary and comment on the full project risk exposure.
Note that the business case and the Benefits Management Approach will have been updated for inclusion here and that business assurance and user assurance will have played a key role here. They may even write this section of the End Stage Report.
Review of the project objectives. There are three components of this section of the end-stage report:
- Review the six project control areas – time, cost, quality, scope, risk and benefits, and a statement of each being met or otherwise.
- Review of the effectiveness of the four management strategies within the Project Initiation Documentation (risk, configuration management, quality, and communication)
- Review of the effectiveness of the project controls in delivering the project successfully.
If any of the above have been changed, this should be included under the above sub-section.
Review of team performance. Any comment on general team performance during the time frame of the end stage report, possibly from time sheets, and a mention of exemplary individual performance if appropriate.
Review of Products. Consider my remarks at the beginning; keep this part of the end-stage report as simple as needed to provide evidence for project board judgement. Don’t duplicate details if the project board already have them!
- Quality Records – planned and completed activities
- Approval records – products completed and approved
- Off-specifications. If any, point the reader to the details; summarize them here.
- Phased handover. If any products have been handed over to operations/user/customer, please confirm that they were ready and accepted.
- Summary of follow-on action recommendations. If any, these are agreed actions to be done by others after the project has closed.
Lessons Report. This will be created at the end of the project, but any lessons may be passed on at this point, in which case they should be included in the end-stage report.
Issues and risks. A summary of them – do not list them, as this information is on the relevant Registers.
Forecast. This is based on the project and will include time and cost metrics. This section could be combined with the first heading!
PRINCE2® 7 Foundation and Practitioner


Learn PRINCE2® 7 Foundation and Practitioner Online
** Enhance your PRINCE2 career now **
PRINCE2® Masterclass gives you the skills necessary to manage projects effectively and achieve your objectives.
Get 7 days a week 12 months one to one coaching with ex PRINCE2 examiner Dave Litten.
PRINCE2® is a globally recognized project management framework. By completing both the Foundation and Practitioner courses through our self-paced e-learning, you will develop an understanding of the methodology and learn how to effectively adapt it to any project.
The PRINCE2® 7 Foundation and Practitioner Masterclass is PeopleCert Accredited and guarantees to take you from PRINCE2 Novice to PRINCE2 Practitioner with our famous video learning, study guides and practice exams.
What Does the Masterclass Cover?
The PRINCE2 Foundation examination assesses your knowledge and comprehension of the PRINCE2 project management methodology as detailed in the syllabus. The PRINCE2 Practitioner examination, on the other hand, gauges your ability to apply and tailor the PRINCE2 method. Candidates who pass the Practitioner exam should be able to start implementing the method on an actual project with some guidance. However, their effectiveness may differ based on their experience in project management, the complexity of the project, and the level of support they receive in their work environment.

