Confirm ownership and access
Keep a record of the domain registrar, hosting account and any editing tools. Use accounts and access arrangements you can maintain. Do not place private passwords inside a public website ZIP or source repository. A handover document should explain the systems involved without exposing credentials.
Keep an organised source copy
Retain the complete source and asset files, not only screenshots of the finished design. Record which version is currently live and which files were changed in an update. Keep a backup before replacing production files. Clear names and version notes reduce confusion when several ZIPs or preview links exist.
Know how content changes
Identify where headings, service descriptions, images, forms and contact details are edited. If the site has translated pages, list every version that needs updating. For a static site, explain the relevant HTML and asset paths. For an editing system, document the correct page or field rather than relying on memory.
Review the practical journeys
Check contact links, forms, navigation and important external embeds periodically. Revisit the site on a phone after major content updates. An image with different dimensions or a longer heading can affect the layout even when the code has not changed. Keep a short checklist so the review is repeatable.
Define support clearly
Agree whether ongoing support includes content changes, technical fixes, hosting, security updates or only a limited handover period. Keep those responsibilities in writing. Avoid assuming that every future feature is part of the original build. A clear arrangement makes it easier to plan improvements without uncertainty about scope.
A quick checklist
- Keep ownership and access records.
- Retain source files and versioned backups.
- Document update and support responsibilities.