What to agree in a website maintenance plan.

Define what support covers

Maintenance is not one universal service. A plan might cover hosting administration, dependency updates, defect fixes, monitoring, backups, or a small amount of new development. Ask for an explicit list of included work and the process for anything outside it.

Clarify the backup plan

A backup plan should name the data being protected, the schedule, retention period, storage location, and who can restore it. A successful backup job alone does not establish that restoration will work. Agree how restoration is checked and what recovery objectives are relevant to your product.

Distinguish response from resolution

A response target describes how quickly a support request is acknowledged and assessed within an agreed support window. A resolution time depends on the cause and complexity of the issue. Avoid assuming that a short response target guarantees an immediate fix.

Use severity levels and a support window

A complete outage and a minor visual issue should have different priorities. Define the severity levels, the hours during which support is available, the escalation contact, and what happens outside those hours. If you need a formal SLA, include its measurement and reporting process in the agreement.

Make provider dependencies visible

Cloud providers, payment services, email platforms, and other integrations each have their own availability and terms. Your agreement should explain how these dependencies are monitored and what assistance is available during an upstream incident.

Revisit the plan as the product grows

A new product and a business-critical system may need different coverage. Review support after major changes, growth in usage, or new integrations. The goal is a plan that matches the product’s actual needs and makes responsibilities clear.