Check it out
Managing your website after launch: who does what?
Your new website is live. But who will update a page, check the contact form or raise the alarm when an integration fails? Website management becomes much clearer when you agree on those responsibilities before handover.

A website can work well technically and still be difficult to manage. Perhaps nobody knows which account pays for a tool. Or three people can edit the copy, but nobody checks whether a new page works properly on mobile.
For me, good website management starts with clear ownership. Who can change something, who checks it and where do you report a problem? This does not need to become a complicated document. A few specific agreements already help.
Separate content, technical upkeep and further development
Adding a case study is different from connecting a form to your CRM. Developing a complete new service page involves different work again from correcting a typo. Yet all of it often gets grouped together as ‘keeping the website up to date’.
Divide the work into three areas. Content covers copy, images and existing pages. Technical upkeep covers your setup, accounts and integrations. Further development covers new features or changes to the structure. You can then decide what knowledge and checks each task requires.
Give every task an owner
A practical division of responsibilities might look like this. It is an example to complete together, not a standard BORING maintenance package:
- A marketer adds a case study. A designated colleague checks the content, links and mobile layout before the page goes live.
- One contact manages access. They give new colleagues suitable permissions and revoke access when someone leaves.
- The person responsible for enquiries checks that a test submission arrives correctly. If it fails, everyone knows who handles the technical follow-up.
- A technical owner reviews changes to code, apps and integrations. They also document how to reverse a change.
- The website owner decides which improvements take priority and agrees the time and budget for them.
In a small team, one person may hold several roles. What matters is that every task has an owner and someone to cover their absence. ‘Someone in marketing handles that’ is usually too vague.
Enable your team to make everyday changes
Which tasks come up regularly? You might publish vacancies, update team members or add case studies. During handover, ask someone from your team to complete one of these tasks. That reveals missing instructions more quickly than simply watching a demonstration together.
Work through the whole task: where the image comes from, which fields are required, how to preview the result and who publishes it. Our article on Webflow and CMS management for marketing teams explains how the setup supports that work.
Document recurring tasks briefly. A screen recording or a short set of steps using a real example may be enough. Update those instructions when the setup changes.
Keep accounts and responsibilities visible
Maintain an overview of the domain, hosting platform, form tool and other connected services. Record who administers each one, who receives the invoice and where access is managed securely. Do not put passwords in a general handover document.
For platform updates, establish which parts the supplier handles and which parts you need to check yourselves. A managed platform does not automatically take responsibility for every external app or custom integration. Check the arrangements for your specific setup.
Do the same for recovery: which data can you restore, from which source, and who is authorised to do so? A recovery option is only useful in practice when you know what it will restore.
Check a function from beginning to end
A form that looks perfectly fine can still send an enquiry to the wrong address. Test the whole journey: enter information, submit it, see the confirmation and check receipt. Use clearly identifiable test data and prevent anyone from treating the test submission as a real lead.
Plan checks around the importance of the function and what changes. A form deserves a check after its fields or recipients are updated, for example. Also agree on a regular checking schedule that fits your use. Reviewing everything every week is not useful for every website.
Agree what happens when something breaks
Where should someone report a problem? What information is needed, and who decides its urgency? An unavailable website needs a different response from a badly cropped image.
A useful report includes the page, what should have happened, what actually happens and when it started. Add a screenshot if helpful, without exposing customer data. Record response times and availability separately if you agree on them; do not assume they are automatically included in handover.
Plan management as part of the website project
Decisions during design and development influence how much work the website needs later. A flexible CMS only helps when your team knows how to use it and someone is responsible for quality.
Want a website that remains practical to manage after launch? Tell us who will work with it and what you want to handle yourselves. We can build that into the setup and handover.




