Markdown Editor

End Stage Report Template

Stage close: performance vs original and exception plan, products and concessions, business case review, benefits, lessons, carried-forward risks, next stage request

项目管理标准Structure aligned with PRINCE2 7 (PeopleCert, 2023)endstagereport

使用方法: Use it at each stage boundary, submitted with the next stage plan and the updated business case. Fill the plan-versus-actual table and the business case review first. The main pitfall is asking for the next stage without restating whether the project is still worth doing.

预览

End Stage Report: [Project name], Stage [N] [stage name]

An end stage report closes one management stage. The project manager tells the project board what the stage delivered against its plan, how the project stands as a whole, whether the business case is still viable, and asks for authority to start the next stage on the basis of a new stage plan. It is the main input to the board's stage-gate decision. The structure is aligned with the end stage report management product and the stage boundary process described in PRINCE2 7 (PeopleCert, 2023), and it fits any stage-gated or phase-gated project. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document ID[ESR-PROJ-NN]
Project[Project name] ([project code])
Stage closing[Stage number and name]
Plan reported against[Stage plan v1.0 / Exception plan v1.0]
Next stage requested[Stage number and name]
Version[1.0]
Status[Draft / Submitted / Approved]
Author[@project-manager]
Board review dateYYYY-MM-DD
Classification[Internal]

Approvals

RoleNameDecisionDate
Executive (sponsor)[@executive][Authorise next stage / Do not authorise / Close project]YYYY-MM-DD
Senior user[@senior-user][Agree / Disagree]YYYY-MM-DD
Senior supplier[@senior-supplier][Agree / Disagree]YYYY-MM-DD

Revision history

VersionDateAuthorChange
0.1YYYY-MM-DD[@author]Draft
1.0YYYY-MM-DD[@author]Submitted with stage 4 plan

The worked example continues the fictional Brackwell Vale Housing Trust Tenant Services Portal. Stage 3, Build and migrate, was re-planned after exception report ER-TSP-001 (option B approved): budget 534,000 EUR, end 2027-05-28. The project budget is 1,090,000 EUR for four stages plus a 90,000 EUR risk budget, 1,180,000 EUR in total.

1. Stage summary

[Summary]

Example: Stage 3 built the new portal and migrated current tenancy data. All 9 planned products are complete, with historic repairs before 2022 left read-only in the legacy system as approved in the exception. The stage ended on 2027-05-28 as re-planned, at 531,500 EUR, 2,500 EUR (0.5%) below the exception plan budget of 534,000 EUR. The business case remains viable. The board is asked to authorise stage 4, Rollout, at 210,000 EUR over 10 weeks.

2. Performance against the stage plan

AreaOriginal stage planPlan in forceActualVariance vs plan in force
Time[Date][Date][Date][Weeks]
Cost[Amount][Amount][Amount][Amount, %]
Scope[Products][Products][Products][Difference]
Quality[Criteria][Criteria][Result][Difference]
Example: Time2027-05-212027-05-282027-05-280
Example: Cost520,000 EUR534,000 EUR531,500 EUR-2,500 EUR (-0.5%)
Example: Scope9 products, full history9 products, current tenancies only9 productsNone
Example: Quality0 open severity 1 defectsSame0 open severity 1, 4 severity 3Accepted by senior user

Against the original budget, the stage cost 11,500 EUR (2.2%) more, funded by 14,000 EUR drawn from the risk budget.

3. Products delivered

Product IDProductStatusQuality evidenceAccepted by
[PRD-NN][Product][Approved / Approved with concession / Not delivered][Evidence][@approver]
PRD-31 (Example)Tenant login with multi-factor optionApprovedSystem and security test reports[@product-owner]
PRD-36 (Example)Cleansed tenancy recordsApprovedReconciliation: 18,500 of 18,500 current tenancies matched[@data-owner]
PRD-39 (Example)Portal accessibility statementApproved with concession4 minor issues to fix in stage 4[@senior-user]

Off-specifications and concessions: [List, with IDs and who accepted them.]

4. Business case review

ItemAt initiationNow forecastComment
Total project cost[Amount][Amount][Comment]
Go-live[Date][Date][Comment]
Annual net benefit[Amount][Amount][Comment]
Payback[Years][Years][Comment]
Example: Project cost excluding risk budget1,090,000 EUR1,096,000 EURActuals 886,000 EUR for stages 1 to 3 plus stage 4 plan 210,000 EUR
Example: Annual net benefit255,500 EUR249,500 EURRead-only legacy licence kept 2 years at 6,000 EUR a year

Conclusion: [Still justified / Justified with changes / No longer justified]

Example: Still justified. Actuals to date are 58,000 EUR (stage 1), 296,500 EUR (stage 2) and 531,500 EUR (stage 3), 886,000 EUR in total. The risk budget has 76,000 EUR left.

5. Benefits achieved so far

BenefitMeasureBaselineAchievedNext review
[Benefit][Measure][Value][Value]YYYY-MM-DD
Example: Calls moved to self-serviceShare of repairs reported online9%Not yet live3 months after go-live

6. Team performance and lessons

IDLessonTypeAction for the next stage
[LL-NN][Lesson][Keep / Change][Action]
LL-07 (Example)Sampling under-estimated data quality problemsChangeProfile full data before any future migration estimate
LL-08 (Example)Daily burn-down of cleansing gave early warningKeepUse the same burn-down for rollout support tickets

7. Issues and risks carried forward

IDDescriptionScore or priorityOwnerPlan in next stage
[ID][Description][Score][@owner][Plan]
RSK-019 (Example)Tenants without email cannot self-register3 x 4 = 12[@senior-user]Assisted registration at local offices

8. Next stage request

ItemValue
Next stage[Number and name]
Products[Main products]
Start and endYYYY-MM-DD to YYYY-MM-DD
Budget[Amount]
Proposed tolerances[Time, cost, scope, quality, risk, sustainability]
Plan document[Link]
Example: Next stage4, Rollout
Example: Start and end2027-05-31 to 2027-08-06 (10 weeks)
Example: Budget210,000 EUR
Example: Proposed tolerancesCost +/-5% (10,500 EUR), time +/-1 week

9. Related templates

Glossary

  • Stage boundary: the point between two stages where the board decides whether to continue.
  • Exception plan: a plan that replaces a stage plan after the board accepts an option in an exception report.
  • Concession: acceptance of a product that does not fully meet its specification.
  • Off-specification: something that should be provided but is not, or that does not meet its specification.
  • Risk budget: money set aside for risk responses, controlled by the board.

Standard and licence note

Structure aligned with the end stage report management product and the "manage by stages" principle of PRINCE2 7 (Managing Successful Projects with PRINCE2, 7th edition, PeopleCert, 2023), including the stage boundary process. PRINCE2 is cited by name only: no text, tables or figures from the publication are reproduced, and the headings, wording and the fictional Brackwell Vale example are original. Official text: PeopleCert, purchase or licensed access: https://www.peoplecert.org/prince2. PRINCE2 is a registered trademark of PeopleCert. Check the current edition and your organisation's stage-gate rules before use. Template licence: MIT.

相关模板