Website maintenance: updates are not enough

Define the responsibilities

List who manages the domain, hosting, content, software and support requests. Agree what the maintenance package includes, its response arrangements and which work is billed separately. Avoid confusing routine maintenance with a guaranteed emergency service.

Test recovery, not just backup creation

Record where backups are stored, which data they contain and who can access them. A successful export alone does not prove that the website can be restored. Test recovery in an isolated environment without overwriting production.

Review real journeys

After an update, check login, forms, bookings, uploads and key mobile screens. Review permissions and errors, and remove access that is no longer needed. Keep a short change log and a way to roll back. Maintenance is an ongoing operational task, not a one-time badge of complete security.