Day 19: Close a Project Properly

The Concept

Closing a project is a delivery activity. It confirms what was achieved, records what remains, transfers ownership, and gives the organisation a chance to learn. A rushed closeout creates hidden work and weakens trust in future plans.

Finish against the promise

Compare the result with the original outcome and success measures. “The deliverable was shipped” does not prove that the intended change happened. If measurement will happen later, name who owns it and when it will be reviewed.

Close the open loops

Open risks, unpaid work, unresolved defects, missing documentation, and unclear ownership all belong in the closeout. They do not need to be solved by the project team, but they do need a visible next owner and destination.

Example: distinguish closed from transferred

Suppose a project launches a new internal service. The launch is complete, but three low-priority defects remain, usage data will not be reliable for another month, and the support team has not yet taken ownership of the incident queue. Calling the project complete may be reasonable; calling every obligation complete is not.

A good closeout records the launch acceptance, transfers the defects to the support backlog with owners, assigns the measurement review to an operations lead, and confirms when the incident queue becomes the team's responsibility. The project can close without pretending that the product has no future work.

Close with evidence

Collect the evidence that proves delivery: acceptance, final decisions, approved scope changes, key measures, financial or capacity reconciliation, and links to the source records. Do not create a new document simply to say that documents exist. Link to the records people will need later and note any retention or access requirements.

Communicate the ending

Tell stakeholders what was achieved, what changed, what remains, who owns the next work, and when outcomes will be reviewed. A closeout message is also an opportunity to thank contributors and acknowledge limitations without turning the update into a celebration that hides unfinished obligations.

Learn while memory is fresh

Ask what should be repeated, stopped, or changed. Connect the answer to a future brief, plan, risk review, or checklist. Lessons become useful when they are placed where the next team will encounter them.

A final check before sharing

Read the closeout as someone inheriting the result six months later. Can they tell what was promised, what was accepted, what remains open, and who to contact? If not, the project is administratively finished but not properly closed.

Confirm the outcome owner

Some outcomes cannot be measured at the moment of delivery. Adoption, cost reduction, customer behaviour, or operational stability may need weeks or months to appear. Assign the measurement to a named role, define the measure, and set the review date. If the result does not appear, that owner should be able to explain whether the assumption, implementation, or measurement approach needs attention.

Close access and administration

Review temporary access, project spaces, vendor arrangements, recurring meetings, budget codes, and unused tools. Closing this work is part of responsible delivery. Keep the records required for audit, support, or future learning, but remove access and copies that no longer have a purpose.

Make the ending useful for the next start

Capture the smallest set of information that would help another project begin well: the original problem, key decisions, meaningful trade-offs, measures, risks that appeared, and practices worth repeating. A closeout is not a memoir. It is a practical handrail for future work.

A final check before archive

Ask the sponsor, receiving owner, and project team whether anything important is missing. Resolve contradictions before archiving the record. A clean close gives the organisation confidence that projects can end without losing accountability.

Use this today

The closeout can also identify work that should become a standing operational practice. Name the owner, the first action, and the date for review so the benefit remains connected to the organisation.

Closeout is also a moment to check whether the original business case still holds. If assumptions changed, record that plainly. The result may still be valuable, but future work should not inherit a promise that the evidence no longer supports.

Make the changed assumption visible in the final record and tell the relevant owner what to revisit.

An explicit follow-up is better than an implied obligation.

Keep the owner and review date in the closeout record.

That makes future measurement possible.

Close the record only after the responsibility is clear.

This is a small administrative act with lasting value for the organisation.

Future teams should be able to trust the closeout.

Keep the evidence available for future review.

Make ownership explicit.

For everyone involved.

Choose a completed project or phase and create a closeout record. Ask one stakeholder whether the result solved the problem they expected it to solve. That answer may be more valuable than the final status colour.

Remember this

• A project is not closed because the calendar says it is over.
• Move remaining work explicitly to an owner and destination.
• Measure outcomes after delivery when the result needs time to appear.