Maintenance

Maintenance agreement: what should a website maintenance agreement include?

A good maintenance agreement defines the tasks, response times, responsibilities and price. This guide covers what the agreement should contain, pricing models and the most common pitfalls.

Updated

When a business outsources the maintenance of its website, the agreement decides what the money buys. Without a written agreement, "maintenance" can mean a monthly round of updates to the supplier and everything to do with the website to the customer. The disagreement usually only surfaces during an incident.

This article goes through what a maintenance agreement should include.

Core contents of the agreement

A good maintenance agreement answers at least these questions:

Area What to record
Scope Which websites, domains, environments and integrations the agreement covers
Tasks What is done and how often: updates, backups, monitoring, reporting
Response times How quickly the supplier reacts to an incident and how quickly it is fixed
Service hours Weekdays during office hours, or evenings and weekends too
Boundary with development What the monthly fee covers and what is invoiced separately
Reporting What the customer is told and how often
Responsibilities Who is responsible for the domain, server, content and third-party services
Ownership Ownership of credentials, backups and code, and their handover when the agreement ends
Data protection A data processing agreement if the supplier has access to personal data
Price and term Pricing model, price reviews, notice period

Tasks in detail

A mention of "website updates" is not enough. Record the tasks concretely:

  • Updates: the CMS core, plugins and theme, how often, and whether they are tested in a staging environment first.
  • PHP and server versions: does the supplier follow support periods and handle version changes?
  • Backups: frequency, retention period, location and the rhythm of restore tests.
  • Monitoring: uptime monitoring, tracking SSL certificate and domain expiry, malware scanning.
  • Checks after updates: are forms, the online shop checkout and login tested?
  • Reporting: a monthly report on the updates made, problems found and recommendations.

Response times and service level

Classify incidents by severity and agree on a response time for each class:

Class Example Response time (example)
Critical Site down, online shop checkout not working, data breach 1–4 hours within service hours
Major A form does not work, some pages have errors Next working day
Minor A layout bug, a single broken link 3–5 working days

Response time usually means the time within which the supplier starts investigating, not the time by which the fault is fixed. Separate the two in the agreement. If the business needs monitoring in the evenings and at weekends too, that must be agreed and priced separately.

The boundary between maintenance and development

Most billing disputes arise at this boundary. Record, for example:

  • Maintenance: updates, backups, monitoring, fixing functionality broken by an update, fixing security findings.
  • Development: new page templates, new features and integrations, design changes, adding content, large performance projects.

A clear approach is a bank of hours from which small change requests are charged, with a separate quote for larger pieces of work.

Pricing models

  • A fixed monthly fee covers the agreed tasks. It is predictable, but extra work is invoiced separately.
  • A bank of hours: the customer buys a set number of hours that are used as needed. It suits situations where change requests come in irregularly. Check whether unused hours carry over to the next month.
  • A combination: fixed basic maintenance plus a bank of hours for small changes. This is the most common model for business websites.

Always compare offers on their content. A low monthly price that only covers pressing the plugin update button is a different service from an agreement in which backups are tested and updates checked.

Ownership and ending the agreement

Make sure the agreement lets the business change supplier without the website being held hostage:

  • The domain is registered in the company's name.
  • The company has its own main administrator credentials for the CMS, the hosting and the domain service.
  • When the agreement ends, the supplier hands over a fresh backup, the documentation and all credentials.
  • The rights to use and modify any custom code have been agreed.

Data protection

If the maintainer has access to personal data, such as form submissions or online shop customer data, it acts as a processor of personal data within the meaning of the GDPR. The agreement then needs data processing terms that define the purpose of processing, security measures, subcontractors and the procedure in the event of a data breach.

Checklist before signing

  • Are the tasks recorded concretely, including their rhythm?
  • Are response times classified and separated from fix times?
  • Is the boundary between maintenance and development clear?
  • In whose name is the domain, and does the company have its own main administrator credentials?
  • Are the data processing terms attached?
  • What happens when the agreement ends?

For the big picture of maintenance, see Website maintenance.

Frequently asked questions

How much does a website maintenance agreement cost?

The price depends on the type of website and the scope of the agreement. Basic technical maintenance for a brochure site is often a few tens of euros a month, whereas maintenance, monitoring and fast response times for an online shop can cost hundreds of euros a month. Compare agreements on their content, not just the monthly price.

What does SLA mean in a maintenance agreement?

An SLA (service level agreement) defines measurable promises such as the response time to an incident report, the time to fix and the availability of the service. A good SLA also states what happens if a promise is not met.

Who owns the domain and the credentials?

The business. Register the domain in the company's name and keep the main administrator credentials in the company's own password manager. Write into the agreement that the supplier hands over credentials, backups and documentation when the agreement ends.

Can the maintenance agreement be with a different supplier from the one that built the site?

Yes. A new supplier usually starts with an audit of the CMS, plugins, server and credentials. Ask for the price of the audit in advance.

Sources

  1. Office of the Data Protection Ombudsman (Finland)