The handover is part of the work, not the end of it

The most neglected part of any engagement

Attention concentrates on winning the work and delivering it. The end tends to be an afterthought: the thing is finished, an invoice goes out, and the relationship trails off without any particular moment.

That is a waste of the point at which the client is most satisfied and most willing to help. It also creates a long tail of small requests, because nothing ever established that the engagement had concluded.

What a proper handover contains

Everything they need to use, maintain or continue what you built, in a form they can find without asking you. Files, access, credentials, whatever documentation the work requires. Written notes on anything that would not be obvious to whoever inherits it.

This costs a morning and it’s the difference between a client who is capable on their own and one who has to contact you every time something ordinary happens. It also protects you, because a client dependent on your memory is a client whose problems keep arriving without invoices attached.

Anything they own should be handed over in a usable form rather than left inside an account of yours. Who owns what is a question the agreement should have settled at the start, and it varies by trade and by country, so if the work involves rights of any significance it is worth being explicit rather than assuming a convention.

Say that it is finished

A closing message that states the work is complete, lists what was delivered, and confirms what happens next is a small thing that resolves a surprising amount of ambiguity. It marks the boundary.

That boundary is what makes later requests easy to handle. A question arriving three months after a defined close is plainly new work, and both sides can see that without anybody having to be awkward about it. Without the boundary, the same question is an unresolved part of the old job, and declining it looks like poor service.

Ask for the two things now

The moment after successful delivery is when a client is most willing to write something for you or introduce you to somebody. Waiting a month reduces both, and waiting six means it will not happen at all.

Ask for the specific thing rather than a general endorsement. A few sentences about what the problem was and what changed is more useful than praise, and it’s easier for them to write because it does not require them to compose anything.

The introduction is the same principle. Naming a particular kind of person you would like to meet is answerable; asking them to keep you in mind isn’t. Both requests are made easier by having just done good work, which is exactly why the timing matters more than the wording.

Decide what ongoing support looks like

Almost every completed project generates some continuing need — questions, small changes, maintenance. Leaving it undefined means either giving that away indefinitely or refusing it awkwardly later.

Naming the arrangement at handover solves it: a period of included support of a stated length, then hourly, or a retainer, or nothing at all. Whichever it is, the client knows and can plan for it, and you aren’t making individual decisions about goodwill every time a message arrives.

This is also where a good deal of repeat revenue lives. Clients who have a defined way to come back tend to come back, and clients who are uncertain whether they would be imposing tend to go elsewhere next time.

Keep the file, and diarise a return

Keep your own record of what was done, in enough detail that you could describe it in two years without the client system in front of you. Portfolios built entirely inside somebody else’s accounts disappear when the relationship does.

And put a date in the calendar to make contact some months later. Not a sales message — a brief note asking how the thing is working. It costs nothing, it frequently produces the next project, and it is the single cheapest source of work available to a business that has been running for a few years.

None of this needs to take long. A handover checklist that you reuse on every job — what to send, what to write down, what to ask for, what to record — turns the whole thing into an hour of routine rather than a piece of thinking to be done afresh each time. Which matters, because the end of a project is precisely when energy for it is lowest and the next job is already waiting.