01 / Confirm the agreed deliverables.
Compare the final package with the latest agreed scope. Review approved changes as well as the original brief. This prevents an outdated checklist from becoming the definition of completion.
02 / Check the receiving experience.
Open the handover links, confirm the correct versions, and check that the intended recipient has the access they need. Label files by their purpose. Treat the handover document as an interface someone else must navigate.
03 / Separate open items from completed work.
State any remaining inputs, decisions, or follow-ups clearly. Assign an owner and an agreed next step. A polished closeout should make uncertainty visible, not hide it under a final-delivery heading.
04 / Preserve the useful history.
Keep approved files, key decisions, and relevant context in an organized location. A future team member should be able to understand why the work looks the way it does without reading every message from the project.
05 / Capture one improvement.
Ask what made the work easier and what repeatedly slowed it down. Turn the most useful lesson into a concrete change to a brief, checklist, or review rhythm. Reflection becomes valuable when it changes the next project’s working conditions.
Choose one idea from this note and apply it to the next brief, update, or handover you prepare.
Talk through a project with me ↗