A website launch is a handover as well as a milestone. Once the site is in everyday use, someone needs to update its content, renew the services it depends on and decide what happens when something stops working. Those responsibilities are easier to discuss before the first urgent problem, while there is still time to make a practical plan.
Who controls the important accounts?
List the domain registration, hosting, email, software licenses and connected services. Record who owns each account and how access is managed. The organization should understand where the services live and which renewal dates matter. Do not put passwords into a public form or an ordinary project document; agree on an appropriate way to share and manage access.
Who keeps the content current?
A website becomes less useful when an old contact detail, outdated service description or expired event stays in place. Decide who can edit the relevant sections and who approves changes. Ask for a handover that covers the tasks those people will actually perform, such as updating a paragraph, adding a project or replacing an image.
What does maintenance include?
Routine updates, content work, fault investigation and new features are not automatically the same service. Ask which tasks are included, how often they are considered and how additional work is approved. Clarify any coverage hours and response expectations. The details should be written down so both sides understand the arrangement.
What is the recovery plan?
Discuss which parts of the website are backed up, how long copies are retained and who can restore them. Ask how a restoration would be requested and checked. The appropriate arrangement depends on how the website is used and how often its information changes. A backup plan should be connected to a practical recovery process rather than treated as a box to tick.
What should be checked after a change?
- Important pages and navigation still open as expected.
- Forms can save a request and the relevant notification route is checked separately.
- Key content remains readable on smaller screens.
- Any agreed connections to outside services still perform their intended task.
- Someone knows how to report a problem and what information to include.
Where do future improvements belong?
Keep a short list of changes that can follow launch: a new article section, a better workflow or an additional service page. Separating those improvements from routine care makes the budget and priorities easier to discuss. It also gives the website a practical path forward instead of letting every request become an urgent exception.
Make the agreement easy to find.
Keep the scope, key contacts and operating notes together in a place the responsible people can access. Review them when the website, staffing or providers change. The aim is not a large manual for its own sake; it is enough shared understanding that the next person does not have to reconstruct how everything works.
If the responsibilities around an existing website are unclear, start with a review of the current setup. A manageable care plan begins with knowing what is there and who is responsible for it.