A maintenance agreement should say which tasks are covered and how requests are handled. Content changes, software updates, backups, incident response and feature development are different kinds of work. Name the included activities instead of relying on a broad promise to keep the site running.

A practical approach

Agree the response process and responsibilities on both sides. A response target is not necessarily a resolution promise, especially when a third-party provider is involved. Keep billing, access and escalation contacts current so urgent work does not stall for administrative reasons.

Your checklist

  • List included tasks and explicit exclusions.
  • Specify reporting and support request channels.
  • Confirm who monitors and renews external services.

For example

A plan might include routine software updates and backup checks but exclude new page design. That can be reasonable if the distinction is clear before the client sends a redesign request through the support channel.

Planning a project? Explore our ecommerce & cms or tell us what you need.