Assemble a closure pack that separates accepted outputs, residual work, operational ownership and evidence-based lessons for the next project.
Willow Club has delivered a workshop-booking page. The form and export passed acceptance, but a help article is unfinished and an automated reminder was explicitly deferred. Operations starts Monday. A closure meeting must avoid presenting deferred scope as a defect or leaving unfinished agreed work without an owner.
| Item | State | Owner after handover |
|---|---|---|
| Booking form | accepted | Operations |
| Attendance export | accepted | Operations |
| Help article | agreed; incomplete | Editor |
| Automatic reminder | deferred change | Sponsor review |
Closure criteria should distinguish delivery acceptance from administrative completion and transition readiness. A project can have accepted outputs alongside explicitly transferred actions, depending on its agreed rules. The decision must be transparent. Do not silently relabel an incomplete baseline item as optional just to create a green status.
Define five closure checks and classify the four supplied items against the approved scope.
Closure conditions and scope disposition
Record your result and evidence here or in a separate file.
The help article remains an open agreed item and the reminder remains a deferred change.
Return to the baseline before labeling an item a defect or a future enhancement.
A handover transfers usable knowledge and responsibility. Include access arrangements, support contacts, operating instructions and unresolved issues. A folder of files is not sufficient if the receiving owner cannot perform the routine task. Use a walkthrough to test the handover and record which parts still need clarification.
Create a handover index and a walkthrough for exporting attendance and handling a failed booking.
Operational handover checklist
Record your result and evidence here or in a separate file.
Every routine task points to instructions and a receiving owner; no credentials appear in the pack.
Ask the receiving role to locate the next action without the project team explaining it.
A learning review separates what happened, the evidence, contributing conditions and a change to future practice. Avoid attributing every problem to a person. A lesson becomes reusable when it says when the recommendation applies and what evidence would show it helped. Record disagreement when the available evidence cannot settle a cause.
Write three lesson cards from the supplied handover situation, each with an observation, condition and next-project action.
Three reusable lesson cards
Record your result and evidence here or in a separate file.
Each card proposes an observable process change and avoids an unsupported blame claim.
Replace communicate better with a specific checkpoint, owner or shared artifact.
A closure report is a compact decision record. Compare promised and accepted outputs, summarize remaining actions and identify where evidence lives. Distinguish measured outcomes from hoped-for benefits after transition. Include the final approved version so future readers can understand the scope without reconstructing every meeting.
Draft a two-page closure report with a residual-action table and evidence links.
Versioned closure report
Record your result and evidence here or in a separate file.
The report includes the unfinished help article and does not claim later operating benefits have already occurred.
Separate delivery facts from benefit forecasts and assign dates to residual actions.
A closure review should test whether the transition is workable. The receiving owner may accept with explicit conditions or identify a blocking gap. Record the decision and any follow-up, then preserve the learning in a findable location. Archiving should not destroy information required to support the service or explain a prior decision.
Simulate the Monday walkthrough and record acceptance with conditions or a hold, using the evidence in your pack.
Receiving-owner review record
Record your result and evidence here or in a separate file.
The decision names the receiving role and the disposition of every open item.
Do not write handover complete before checking whether the receiving owner can use the material.
Deliver the closure conditions, handover index, three lesson cards, report and receiving-owner review. Reopen the pack as a new team member and locate the help-article owner and the reason the reminder was deferred.
No unresolved baseline item disappears from the closure record and no future benefit is claimed as already realized.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The two accepted functions can be evidenced separately from the help article. The article needs an assigned completion date and an agreed transition decision. The reminder belongs in the deferred-change record. Treating all four as completed would misstate the scope and remove useful follow-up information.
This is a small project-transition and learning exercise; retention and contractual requirements depend on the real organization.