Imagine finishing a project on a Friday afternoon. The last file is uploaded. The invoice is sent. You close the tab with the quiet satisfaction of someone who might, at last, locate the surface of their desk.
On Monday, your client writes: “Thank you! What do we do with this now?”
It is an entirely reasonable question. It can also be a slightly deflating one when you thought the work was finished.
From your side, the project may have a clear ending. You know which decisions were made, where the final version lives, and what the client will need to maintain. They may be looking at a folder full of unfamiliar files while trying to remember something you explained three weeks ago.
The last part of the work is helping someone know what happens next.
I have a soft spot for a proper closing note. There is something considerate about gathering the useful details before everyone moves on. It gives the client a place to return when the meeting is over, and the information has stopped being fresh.
That note can be brief. Start with what is complete, using the same language you agreed on at the beginning. Link directly to the final materials and identify which ones to use. A folder containing six versions and a reassuring “Everything is in here” still leaves someone with a small research assignment.
Then explain the next practical step. Perhaps the client needs to review a document, share a resource with their team, or begin using a new process. Name that action clearly, including who is responsible and any agreed date.
Suppose you have helped a business organize its client onboarding. The final delivery might include a workflow, email templates, and a tracking board. Your client will need to know which message starts the process, who sends it, and where to record a reply. A short walkthrough with a simple example can help them put the materials to work.
Leave room for an honest distinction between delivered and ready to use. An approval may be outstanding, or the client may still need to confirm a setting. Bringing that into the closing conversation helps everyone understand the work's actual status.
It is also useful to explain the support that follows. If a review meeting or a period for questions is part of your agreement, remind the client how to use it. If ongoing maintenance belongs with their team, make that responsibility clear. A gracious ending can have sensible limits.
Thanking the client belongs here, too. I would keep it personal and specific to the work you actually shared. No need to give a small project the farewell treatment of an ocean liner. A thoughtful sentence can acknowledge the client’s time and contributions without requiring a commemorative program.
When appropriate, a later check-in can give someone room to raise a question that only became apparent in use. Agree on that follow-up and put it somewhere dependable. An intention to “circle back sometime” is easy to carry into the following year.
The ending also needs a little behind-the-scenes attention. Close out the project record. Capture an improvement for the next engagement. Review any temporary access according to the arrangement you made. These details help prevent a completed project from lingering indefinitely in the business.
For ongoing relationships, you can apply the same care to a phase of work. A monthly summary or the close of an initiative can give the client a clear view of progress without suggesting that the whole relationship is ending. It is a useful pause in which to recognize what’s been completed and confirm what comes next.
I would begin with one project nearing its final week. Read your planned delivery message as though you had not spent the last month immersed in the work. Could you find the right file? Would you know your next step? Would you understand where to take a question?
People should leave a closing conversation feeling equipped to continue. That is worth a little care before you put the file away.