
1. Forecast
1.1. [Provide the Project Manager’s forecast for the project and next stage against planned targets and tolerances for time, cost, quality, scope, benefits and risk]
2. Issues and Risks
2.1. [Summarise the current set of issues and risks affecting the project]
3. Review Stage Objectives
3.1. [Review how the specific stage performed against its planned targets and tolerances for time, cost, quality, scope, benefits and risk]
4. Review of Products
4.1. Summary of Follow-on Action Recommendations (if applicable)
4.2. Phased Handover (if applicable)
4.2.1. [Provide confirmation by the customer that operations and maintenance functions are ready to receive the release]
4.3. Products
4.3.1. [Product Name]
4.3.1.1. Quality Records
4.3.1.1.1. [Planned]
4.3.1.1.2. [Completed]
4.3.1.2. Approval Records
4.3.1.2.1. [....]
4.3.1.3. Off-specifications
4.3.1.3.1. [....]
4.3.2. [Product Name]
4.3.2.1. Quality Records
4.3.2.1.1. [Planned]
4.3.2.1.2. [Completed]
4.3.2.2. Approval Records
4.3.2.2.1. [....]
4.3.2.3. Off-specifications
4.3.2.3.1. [....]
4.3.3. [Product Name]
4.3.3.1. Quality Records
4.3.3.1.1. [Planned]
4.3.3.1.2. [Completed]
4.3.3.2. Approval Records
4.3.3.2.1. [....]
4.3.3.3. Off-specifications
4.3.3.3.1. [....]
4.3.4. [Product Name]
4.3.4.1. Quality Records
4.3.4.1.1. [Planned]
4.3.4.1.2. [Completed]
4.3.4.2. Approval Records
4.3.4.2.1. [....]
4.3.4.3. Off-specifications
4.3.4.3.1. [....]
4.3.5. [Product Name]
4.3.5.1. Quality Records
4.3.5.1.1. [Planned]
4.3.5.1.2. [Completed]
4.3.5.2. Approval Records
4.3.5.2.1. [....]
4.3.5.3. Off-specifications
4.3.5.3.1. [....]
4.3.6. [Product Name]
4.3.6.1. Quality Records
4.3.6.1.1. [Planned]
4.3.6.1.2. [Completed]
4.3.6.2. Approval Records
4.3.6.2.1. [....]
4.3.6.3. Off-specifications
4.3.6.3.1. [....]
5. Lessons Report
5.1. [A review of what went well, what went badly, and any recommendations for corporate or programme management consideration]
6. Review of Team Performance
6.1. [Provide recognition for good performance]
7. Review of Project Objectives
7.1. [Review how the project has performed to date against its planned targets and tolerances for time, cost, quality, scope, benefits and risk. Review the effectiveness of the project’s strategies and controls]
8. Review the Business Case
8.1. [Summarise the validity of the project's Business Case]
8.2. Benefits achieved to date
8.3. Expected net benefits
8.4. Deviations from the approved Business Case
8.5. Residual benefits expected
8.5.1. [Remaining stages and post-project benefits expected]
8.6. Aggregated risk exposure
9. Document information
9.1. Project Name
9.1.1. [name]
9.2. Date
9.2.1. [date]
9.3. Release
9.3.1. Draft/Final
9.4. Author
9.4.1. [author]
9.5. Owner
9.5.1. [owner]
9.6. Client
9.6.1. [client]
9.7. Document Number
9.7.1. [number]
9.8. Revision, Approvals & Distribution
9.8.1. Revision History
9.8.1.1. Revision # [....]
9.8.1.1.1. Revision Date
9.8.1.1.2. Previous Revision Date
9.8.1.1.3. Summary of Changes
9.8.1.1.4. Changes Marked
9.8.1.2. Revision # [....]
9.8.1.2.1. Revision Date
9.8.1.2.2. Previous Revision Date
9.8.1.2.3. Summary of Changes
9.8.1.2.4. Changes Marked
9.8.1.3. Revision # [....]
9.8.1.3.1. Revision Date
9.8.1.3.2. Previous Revision Date
9.8.1.3.3. Summary of Changes
9.8.1.3.4. Changes Marked
9.8.1.4. Date of next revision:
9.8.1.4.1. [....]
9.8.2. Approvals
9.8.2.1. Approval # [....]
9.8.2.1.1. Name
9.8.2.1.2. Signature
9.8.2.1.3. Title
9.8.2.1.4. Date of Issue
9.8.2.1.5. Version
9.8.2.2. Approval # [....]
9.8.2.2.1. Name
9.8.2.2.2. Signature
9.8.2.2.3. Title
9.8.2.2.4. Date of Issue
9.8.2.2.5. Version
9.8.2.3. Approval # [....]
9.8.2.3.1. Name
9.8.2.3.2. Signature
9.8.2.3.3. Title
9.8.2.3.4. Date of Issue
9.8.2.3.5. Version
9.8.3. Distribution
9.8.3.1. Distribution # [....]
9.8.3.1.1. Name
9.8.3.1.2. Title
9.8.3.1.3. Date of issue
9.8.3.1.4. Version
9.8.3.2. Distribution # [....]
9.8.3.2.1. Name
9.8.3.2.2. Title
9.8.3.2.3. Date of issue
9.8.3.2.4. Version
10. How to use this template
10.1. How to share this template with your team
10.1.1. Send an email
10.1.1.1. 1. Click Share this map
10.1.1.2. 2. Select Invite People
10.1.1.3. 3. Write a message
10.1.1.4. 4. Click Invite
10.1.2. Send a link
10.1.2.1. 1. Click Share this map
10.1.2.2. 2. Tick Link to share
10.1.2.3. 3. Copy the link to share it
10.1.3. Export
10.1.3.1. 1. Click down arrow, bottom right
10.1.3.2. 2. Select the export option you want
10.2. How to complete this template
10.2.1. Complete the sections in square brackets
10.2.1.1. [....]
10.2.2. Read these sections for help on this template
10.2.2.1. Purpose
10.2.2.2. Advice
10.2.3. Navigate using the links in Contents
10.2.3.1. Contents
10.3. Attribution
10.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS
10.4. Get this template here
11. Overview
11.1. Purpose
11.1.1. An End Stage Report is used to give a summary of progress to date, the overall project situation, and sufficient information to ask for a Project Board decision on what to do next with the project.
11.1.2. The Project Board uses the information in the End Stage Report in tandem with the next Stage Plan to decide what action to take with the project: for example, authorize the next stage, amend the project scope, or stop the project.
11.2. Contents
11.2.1. The End Stage Report should cover the following topics.
11.2.2. Project Manager's report
11.2.3. Review of the Business Case
11.2.4. Review of Project Objectives
11.2.5. Review of Team Performance
11.2.6. Lessons Report
11.2.7. Issues and Risks
11.2.8. Forecast
11.2.9. Review of Products
11.2.10. Note: Where the End Stage Report is being produced at the end of the initiation stage, not all of the above content may be appropriate or necessary
11.3. Advice
11.3.1. The End Stage Report is derived from the: Current Stage Plan and actuals; Project Plan; Benefits Review Plan; Issue Register, Quality Register and Risk Register; Exception Report (if applicable); Lessons Report; Completed/slipped Work Packages and updated Business Case.
11.3.2. An End Stage Report can take a number of formats, including presentation to the Project Board (physical meeting or conference call), as a document or email issued to the Project Board; or as an entry in a project management tool.
11.3.3. The following quality criteria should be observed:
11.3.3.1. The report clearly shows stage performance against the plan
11.3.3.2. Any abnormal situations are described, together with their impact
11.3.3.3. Any appointed Project Assurance roles agree with the report.