What to put in a website handover
A website handover should help the next person use the site confidently. A folder of design files is useful, but it does not explain how content is updated, who owns the accounts or what needs attention after launch.
Explain the everyday tasks
Document the actions an editor will perform most often: adding a page, replacing an image, updating navigation and checking a preview. Use the actual labels found in the interface. Include the constraints that matter, such as recommended image shapes and accessible alternative text, without turning the guide into a catalogue of every technical setting.
Make ownership clear
List the services involved and identify the responsible account owner without placing passwords in the document. Explain the approved access process and where operational records belong. Separate public content guidance from confidential infrastructure information. A handover should reduce dependence on one individual while protecting the systems that keep the site running.
Plan the first review
Agree how defects, content changes and new feature requests will be handled. Schedule a review of real usage and accessibility observations once the site has been used. Record known limitations honestly. A launch is a milestone in maintaining a useful site, and a clear handover makes that ongoing work easier to understand and prioritise.
