The Bit After the Big Reveal: Making Your Handover Page Public

Every portfolio has a favourite photograph. The one where the thing is finished, lit properly, and nobody is crying near a printer. It is a good photograph. It is also only half the story. The other half happens on the last day, when the work stops being a project and becomes a set of files someone else has to use.

That last day is where a lot of good creative work gets quietly undone. Not because the work is bad, but because the handover is a shrug: a link to a folder called final_final_v7, a licence buried in an email thread, and a vague promise to be around if anything comes up. First-time clients feel that uncertainty more than established ones. They do not know what normal looks like. They just know they are about to send the final payment and they are not entirely sure what they will own afterwards.

A public handover page fixes a surprising amount of that. Not a contract. Not a fourteen-page terms document. A short, plain-English page on your site that says: here is what happens at the end, here is what you get, here is what you can do with it, and here is how I stay useful after the invoice is paid. It reassures people who have never commissioned creative work before, and it quietly tells everyone else that you finish properly.

The page is not the paperwork

Let us get this out of the way. A handover page does not replace your contract, your licence agreement or your project-specific schedule. It sits in front of them, like a helpful sign at the entrance to a building. The contract is still the thing that does the legal heavy lifting. The handover page is the thing that stops a client emailing at 4pm on a Friday to ask whether the logo files are meant to be used in a newspaper ad.

That distinction matters. You are not trying to be a lawyer on your own website. You are trying to be a clear, organised person who has done this before. The page can be friendly. It can use normal words. It can say what happens without sounding like it was written by a committee in a basement.

What actually lands on the last day

Most clients do not need a dramatic reveal. They need a list. They need to know which files are coming, which formats they will be in, and what they are allowed to do with them. If you have ever watched someone open a zip file with the expression of a person defusing a bomb, you know why this matters.

A good handover page answers the practical questions before they are asked:

• What is included in the final delivery? Final artwork, exports, documents, images, code, or whatever the project produces.
• What formats will be provided? PDF, PNG, JPG, SVG, MP4, WAV, Figma, InDesign, WordPress, and so on. Name the ones that actually apply.
• Are source or editable files included? If yes, say so. If no, say that too, without apology.
• What does the licence cover? Print, web, social, broadcast, internal use, unlimited use, a specific campaign, a specific territory. Keep it short and point to the full terms if needed.
• Who owns what? Client owns the final work; you retain the right to show it; third-party assets such as fonts or stock images have their own rules. A sentence or two is enough.
• What happens with access and accounts? If you are handing over a website, say whether hosting, domain and admin logins are included.

The point is not to cover every edge case. The point is to remove the small, avoidable mysteries that make a finished project feel unfinished.

The aftercare note is part of the work

There is a particular kind of email that arrives two weeks after a project ends. It is polite, slightly apologetic, and asks a question that could have been answered on day one. Can I use this image on a billboard? Where is the version with the transparent background? Did you include the fonts?

A short aftercare note stops most of that. It can be a paragraph on the handover page, not a new service. Something like: for thirty days after delivery I will answer reasonable questions about the files and how to use them. After that, I am happy to help with new work or a paid support session. That is it. Warm, clear, and bounded.

You are not promising to be on call forever. You are promising not to vanish the moment the invoice clears. For a first-time client, that is reassuring. For you, it is a boundary that sounds like care rather than admin.

Say what is not included

This is the bit people skip, and it is usually the bit that causes trouble. If source files are not part of the fee, say so. If the licence is for one campaign only, say so. If you are not providing ongoing maintenance, say so. None of this makes you difficult. It makes you legible.

The trick is tone. You are not writing a warning label. You are writing a signpost. There is a difference between no source files, and source files are available as an optional extra if you need them. Both are honest. One sounds like a door closing. The other sounds like a person who knows what they are doing.

Why put it on the public site at all

You could send this information privately at the end of every project. Many people do. But a public page does three useful things at once.

First, it reassures the nervous first-timer who is still deciding whether to hire you. They can see that you have a process for the ending, not just a nice portfolio for the beginning. Second, it reduces the post-project ping-pong. You can point to the page instead of retyping the same explanation. Third, it signals that you are the sort of creative who finishes properly. In a market full of beautiful launch posts and vague delivery promises, that is quietly persuasive.

It also helps your referrals. When a past client recommends you, the new person can read your handover page and arrive at the first call already knowing what the final week looks like. That is a good place to start.

A structure you can write in an afternoon

You do not need a designer or a content strategist for this. Open a blank page and use five headings:

1. What you will receive
2. What you can do with it
3. What is not included
4. After handover
5. Who to ask

Under each heading, write like you would in an email to a sensible adult. Keep the sentences short. Use bullet points where they help. If a phrase sounds like it belongs in a contract, either cut it or link to the contract. If a sentence sounds like you are apologising for having standards, rewrite it.

The page can live near your contact page or your FAQs. It does not need to be in the main navigation. It just needs to be findable, readable, and true. Update it when your process changes, not every time you get a new laptop.

The last day is still the work

A launch is lovely. The final photograph is lovely. But the last day is where trust either settles or wobbles. A public handover page will not make a bad project good, and it will not replace a decent contract. What it will do is make the ending feel as considered as the beginning. In 2026, that is not a small thing. It is the difference between a client who remembers the work and a client who remembers that you made the last week easy.