What should a website maintenance agreement include?
A maintenance agreement decides who is responsible for your website after launch. We list the clauses that should be written down clearly, from scope and response times to backups and handover.
Summarise this article with an AI tool
The tool opens in a new tab with a summary prompt that includes this article’s address.
A website maintenance agreement should state which tasks are done regularly (updates, backups, monitoring), how quickly requests are answered, where and how often backups are kept, how work is reported, how out-of-scope work is charged, who handles licence and domain renewals, how access details are managed and how the site is handed over when the agreement ends.
Why do you need a maintenance agreement?
You need one because a website is software that keeps changing after launch. WordPress core, themes and plugins are updated; server and PHP versions change; domains and SSL certificates renew. If responsibility for this work is not written down, the first question when something breaks is "who was supposed to do that?"
An agreement sets expectations on both sides and decides in advance who acts when something goes wrong. For sites that take orders, bookings or quote requests, even a few hours of downtime can mean lost business. Karınca Bilişim prepares maintenance proposals around the headings below, and you can use the same list to review any agreement.
How should the scope be defined?
Scope should be defined item by item, with a frequency for each task. Vague wording such as "the site will be maintained" is the most common source of disputes.
| Scope item | What the agreement should say |
|---|---|
| Updates | How often core, themes and plugins are updated; how major versions are handled |
| Backups | Frequency, retention period, storage location and how often restores are tested |
| Monitoring | Whether uptime, security and file change monitoring are included |
| Content changes | What counts as a small change and how many are included per period |
| Performance | Whether speed is measured, and with which tools |
| Security incidents | Whether clean-up after an attack is included |
| Reporting | How often completed work is reported, and in what form |
What counts as a small change?
Define small changes with examples. Updating text, swapping an image or adding a menu item usually qualify. Designing a new page template, building a new form flow or adding an integration is development work. Stating the hours or number of requests included per period removes ambiguity.
What is the difference between maintenance and support?
Maintenance is preventive work done regularly before problems appear; support is fixing a problem once it occurs. Updates, backup checks and monitoring are maintenance. A plugin error, a form that stops sending email or a sudden slowdown is a support request.
Define the two separately. Some agreements cover maintenance only and charge support separately; others include a set amount of support time. The right model depends on how often your site changes and how often issues arise. Stores and membership sites usually need more support than a static company site.
How should reports look?
Reporting tells the site owner, regularly and clearly, what was done and how the site is doing. It makes maintenance visible even in months when nothing broke.
A good maintenance report includes:
- Core, theme and plugin updates with versions
- Backups taken and any restore test
- Uptime results and periods of downtime
- Security findings and actions taken
- Completed change requests and time used
- Upcoming licence, domain and certificate renewals
- Suggested improvements for the next period
The agreement should state how often reports are sent and through which channel. A short monthly summary is enough for most company sites.
How should response times be set?
Response times are agreed by both parties according to how serious an issue is, and written into the agreement. The key is defining what "urgent" and "routine" mean.
- Urgent: the site is completely down, checkout or ordering has stopped, a security breach is suspected
- High priority: an important form fails, a specific page returns an error
- Routine: content changes, small visual fixes, questions
For each level, state the first-response time and the channel to use (phone, email, ticket system), plus how weekends and public holidays are handled. First response and resolution are different things; resolution time depends on the problem and often cannot be promised.
Who holds the backups, and where?
Backups should be stored off the server, somewhere the site owner can also reach. If backups exist only in the supplier's account, the owner is stuck when the agreement ends or the supplier cannot be contacted.
The agreement should answer:
- How often are backups taken, and how many days are kept?
- Which service or server stores them?
- How can the site owner access them?
- How often is a restore tested, and is the result reported?
- Is restoring a backup included in the maintenance fee?
Who is responsible for licences, domains and renewals?
Name the owner of every renewal. Paid theme and plugin licences, the domain, SSL, hosting, email and third-party services each renew on different dates.
We recommend one list showing, for each item: whose name the account is in, the renewal date, who renews it and who pays. Having the domain registered in the site owner's name is the most important long-term safeguard.
How should access details be managed?
Give the supplier only the access needed for the job, through personal accounts rather than one shared login. Separate accounts for the hosting panel, WordPress admin, domain management and third-party services make it easy to remove access when the agreement ends.
An appendix can specify that passwords are never sent as plain text by email or chat, but through a password manager or another secure method. Where the site processes personal data, the supplier's access to that data and how it is protected should be reviewed under the data protection rules that apply to you.
How should out-of-scope work be handled?
Agree the pricing method and approval process for out-of-scope work in advance. New needs often appear during maintenance; the problem is work done without approval and invoiced afterwards.
Include:
- Examples of out-of-scope work
- An hourly rate or a separate-quote method
- A rule that written approval is needed before work starts
- Whether unused maintenance time carries over to the next period
How is the site handed over when the agreement ends?
Handover is a described set of steps for moving the site smoothly to another supplier or to the owner. It is the clause least considered at signing and most needed later.
- Delivery of a current full backup
- A list of all accounts and access details
- Delivery of custom code and its documentation
- Transfer of licences, or a statement of their status
- Removal of the supplier's access
- The expected handover period and whether it is charged
It also helps if the new supplier checks the site before taking over, so its condition is recorded and later issues are not disputed. Clear handover terms give the owner freedom to change supplier and make the relationship healthier for both sides. See our website migration page for related work.
What should you look for in a maintenance proposal?
The most important criterion is how clearly the scope is written, not the price. Fill in the table above for each proposal and ask the supplier about any empty rows.
Karınca Bilişim offers website maintenance and security and hosting and domain management with a written scope based on these headings. Our WordPress security checklist shows what we check regularly. You can share your site's maintenance needs through the quote form.
Frequently asked questions
How long should a maintenance agreement run?
It depends on the site and its needs; monthly, quarterly and yearly terms are common. What matters is that renewal and the notice period for ending the agreement are written down.
Is a site safe without a maintenance agreement?
If your own team does updates, backups and monitoring regularly, an agreement is not essential. If nobody does this work regularly, the risk grows over time.
Is clean-up after an attack part of maintenance?
It depends on the agreement, and it must be written down. Some agreements exclude clean-up, others include it up to a limit. Leaving it open leads to cost disputes during an incident.
What determines the maintenance fee?
Site complexity, plugin count, backup and monitoring frequency, included change time and response times. Stores and membership sites need more checks than static company sites.