How to hand a website over to a client.
A handover goes well when the client knows what they can do alone, and the design is still the design a year later.
In shortA good website handover gives the client three things: the address and who owns what, a way to change everyday content without help, and a clear line for when to call the designer.
What a client needs at handover
Where the site lives
The address, who the domain is registered to, and who pays for hosting. Put it in writing.
A way to change content
Opening hours, prices, team, news. If changing these needs the designer, the site will be out of date within months.
A way back
People edit more freely when they know a mistake can be undone.
A line for design work
New sections, a new look, a new page: say clearly that these go through you, and what they cost.
Three ways to hand over, and what follows
The choice at handover decides who does the small changes for the next years.
| What the client gets | What tends to happen | |
|---|---|---|
| Hand over the files | A folder or a repository | Every change comes back to you, or the site goes stale |
| Hand over a full editor | A login to a CMS or site builder | Content is kept up to date; layouts drift as people experiment |
| Hand over content only | A way to change words and pictures | Content is kept up to date; the design stays as built |
heyweb is built for the third row. See what clients can and cannot change.
A handover with heyweb
What you do on the day.
Step 1: Decide what is content
Choose whether the client may change texts and pictures only, or lists such as a team or a menu as well.
Step 2: Lock what must not move
Navigation, footer, legal text. One sentence to your agent per part.
Step 3: Show the chat once
Change one sentence together and undo it again. That is the whole training.