Website maintenance: scope and responsibility after launch
Define availability, updates, enquiries, backups, content work and product changes as a clear operating service with accountable owners.
ecomvision editorial team
2 min
Published
Key takeaways
- 01Define maintenance boundaries and ownership.
- 02Backups need a recovery procedure.
- 03Separate incident response from product development.
Inventory the system
List domains, hosting, repositories, CMS, analytics and integrations with owners and renewal responsibilities. Avoid relying on a single person’s private account.
Describe essential outcomes such as accessible pages, delivered enquiries and working publishing.
Agree on incident response
Separate outages, broken core journeys and minor defects. Define reporting channels, response expectations and communication. Response time is not the same as resolution time.
Assign authority for rollback or a temporary manual process.
Schedule preventive work
Test dependency updates separately and check forms, certificates, backups and public files. Repeat affected journeys after integration changes.
Verify recovery rather than treating the existence of an archive as proof.
Separate improvements from maintenance
New locales, catalogues or account areas need their own estimate and acceptance. Keep them visible instead of hiding a large project inside routine support.
Reviews should show incidents, updates, unresolved risks and next improvements, not only hours consumed.