Milena RadovićIndependent web developer
← Back to notes

What belongs in a website handover?

A useful handover follows everyday tasks: updating a page, adding an image, checking the result, and knowing what to do when something goes wrong.

· Milena Radović · Process / Content design

A tour of every control-panel menu is easy to give and difficult to remember. I prefer to organise a handover around the changes someone will actually make.

For an events website, that might mean adding next month’s session, correcting a start time, and explaining that a venue has changed. These tasks connect the editing fields to a visible result.

Work through a complete update

Start with a new entry. Add its title and description, choose an image, complete the practical details, and check the page before publishing. Include the parts that are easy to overlook: a useful summary, an image credit, and the destination of a link.

The editor should make the change during the session. Watching a familiar person move quickly through an interface can make a confusing task look deceptively simple.

Leave something useful behind

I want the written guide to answer a short set of questions:

  • Where do I change this information?

  • Which other pages will use it?

  • What should I check before publishing?

  • How do I remove something from public view?

  • Who handles changes outside my access?

Screenshots help when they explain a particular step. Long recordings are less useful when someone needs one answer in the middle of an update.

Explain the limits

A handover should distinguish content changes from changes to the design or functionality. It should also explain the actual backup and recovery arrangements, rather than implying that every mistake has an undo button.

The aim is ordinary confidence. Someone should be able to return a month later, make a familiar change, and know how to ask for help when the task is different.

A good place to start

Have a site that your team has outgrown?

Tell me what you need to change, what you want to keep, and who will be looking after the content. We can start there.

Tell me about your project