Close a project with a usable final handover

A final email with several attachments is not necessarily a usable handover. The recipient needs to know which files are approved, what each one is for and whether anything remains to be done. Organise the close around future use rather than the order in which files were produced.

Provide a clear inventory

List the deliverables in plain language and point to their maintained location. Separate published outputs, editable source files and background material. A client may need all three, but they should not have to guess which PDF is ready to distribute or which document is still an internal draft.

Confirm the status of each important item. If something is excluded, deferred or awaiting a separate decision, say so. Do not describe the project as entirely complete while leaving a required deliverable hidden in a list of follow-ups. Conversely, optional future ideas should not make a completed scope appear unfinished.

For a hypothetical brand-writing project, the inventory could distinguish the approved message brief, editable page copy, final style sheet and a separate list of future content ideas. That separation keeps suggestions from being mistaken for promised work.

Explain how to use and maintain the result

Include only the operational guidance the recipient needs: where the editable files live, which fonts or assets are required, what may need updating and who now owns the record. If there are third-party usage conditions, preserve the information the operator needs to comply with them. Do not imply that delivery of a file automatically transfers every possible right.

Check access before closing the project. Shared links can depend on a departing person's account or a temporary workspace. Use the agreed transfer process and confirm that the recipient can retrieve the material. A folder visible only to the supplier is not a completed handover.

State any agreed support period or follow-up precisely. Avoid open-ended wording such as ‘anything else you need’ if that is not the arrangement. Equally, do not invent a support limitation that conflicts with the agreement. The closing note should reflect the actual scope and relationship.

Leave a useful record of the work

Summarise the key decisions and unresolved matters without retelling the entire project. If a review is planned later, identify its purpose and owner. Archive superseded drafts where appropriate, while keeping the final working files easy to find.

Ask the recipient to confirm receipt and access, and resolve any missing items. The last useful act of a project is often a small verification: can the person who now owns the work open it, understand its status and take the next step without calling the former project team?

Separate delivery, acceptance and future maintenance

Delivery means the agreed material has been supplied. Acceptance means the relevant person has confirmed it meets the agreed requirements, using whatever review process applies. Maintenance is the later work of keeping it current. These stages may happen close together, but they are not the same. A closing note should not imply acceptance simply because the files were sent, or imply ongoing maintenance merely because editable files were included.

For the brand-writing example, the recipient might confirm that the approved pages and style sheet are present, while a separately agreed final factual review remains scheduled. The handover can identify that review without pretending the project has failed to deliver. What matters is that both parties understand the remaining obligation and its owner, rather than using the word ‘complete’ to cover several different states.

If a later operator will update names, prices or service details, point out where those facts appear and how to avoid inconsistent edits. Do not leave them with a general instruction to ‘keep everything current’. A short note about repeated information can prevent an outdated claim from surviving in a secondary page even after the main description has been corrected.