You鈥檝e finished the design, built the pages, checked the mobile layout, and launched the website. The client is happy, and you鈥檙e ready to move on. Then the messages start: a heading needs changing, an image needs replacing, or a phone number has changed. Each request seems small, but they can pull you back into a project you thought was finished.
Prepare the website from the client鈥檚 point of view
Before handover, check the main pages, links, forms, images, and mobile layout. Confirm the website works as expected and document any known limitations. Think about the information the client will need to find and update regularly.
Agree on what the client can edit
Most clients don鈥檛 need access to every technical part of a website. They may need to update headings, paragraphs, images, contact details, or selected colours. More complex changes, such as adding a feature or restructuring a page, may still need a developer. Discuss these boundaries before launch.
Make editing straightforward
A login alone doesn鈥檛 make a website easy to manage. Depending on how the site was built, the client may need a CMS, a visual editor, or another controlled editing interface. Test it with someone who didn鈥檛 build the site. Ask them to change a heading or replace an image. If they need constant help, improve the workflow before calling the handover complete.
Document the essentials
Give the client a clear record of where the website lives, which accounts they own, how to edit approved content, how publishing works, and who to contact for support. Share credentials securely rather than putting passwords in an ordinary document.
Set expectations for future support
Explain which fixes are covered after launch, which updates the client can handle, and how new development work will be scoped and priced. Clear expectations help protect both the relationship and your time.
Test the handover together
Ask the client to make a real change, save or publish it, and check the live site. Review the result on relevant screen sizes and explain how to get help if something goes wrong. A handover is successful when the client knows what to do next, not simply when login details have been sent.
Where Baton fits
Baton is designed to help developers hand over websites and give clients a way to edit supported content, including text, images, and selected visual properties, without working directly with code. Baton supports sites built with different frameworks, while its current CMS works best with lighter websites. Check compatibility against the specific project before relying on it.
A smoother handover benefits everyone
Build the handover into your process from the start. When clients understand what they own, what they can edit, and where to get help, they can manage routine changes with more confidence and you can focus on your next project.