WordPress maintenance is often described in one sentence: "we update the site". In reality you need to know who checks the backups, who responds when a form is not working, how updates are tested and who can restore the site. The contract has to make these responsibilities visible.
Agree on specific checks and their frequency, a backup policy and a restore test, the way WordPress and extensions are updated, monitoring of critical functions and response times. Separate maintenance from new development and clarify who controls the hosting and the access.
What goes into basic operational maintenance
Start with the backups: how often they are created, where they are kept, what the retention period is and when a restore was last tested. A backup that has never been restored is not a proven recovery plan. Then specify the updates of WordPress, the theme and the plugins; critical extensions are tested against the specific functions of the site. The official WordPress documentation on updating is a starting point, but the real process depends on your site's settings and dependencies.
Check functions, not just whether the home page is up
The site can load and still lose inquiries. Agree on checks of the contact form, emails, mobile menu, key pages, analytics events and, if you sell online, the order process. For a site with custom integrations, check whether the data arrives where it should.
Write down who gets an alert on an error and what the working hours for response are. "24/7 monitoring" and "24/7 person who fixes it" are different services.
Separate a defect, an edit and new functionality
| Situation | What should be clear in the contract |
|---|---|
| A form stops working after an update | Who diagnoses it, response time, recovery and a check after the fix. |
| Changing a phone number or text | Is the edit included and who approves it? |
| A new integration with a CRM | How is the separate project priced and who will maintain it afterwards? |
| A hosting problem | Who communicates with the provider and who is responsible for the configuration? |
Ownership and recovery
The domain, hosting, admin accounts and licenses should be documented. Ask for a handover procedure for a change of contractor: a current backup, a list of active extensions, instructions for the integrations and access to the environment. For a custom site, clarify where the code is kept and who can maintain it.
How to assess the monthly report
A useful report describes the updates made, the functions checked, incidents, backups, remaining risks and proposals that need a decision from the owner. A count of "plugins updated" without a check of the site says little. If you are planning a redesign, also read when the change solves a business problem; maintenance and redesign have different jobs.
For a specific scope of monitoring and response, take a look at website maintenance from DigitaL+.
A sample monthly check
A useful record for one month would contain the date and result of the backup, a restore check at the agreed interval, updated versions, a test of the form and the main pages, observed errors and open tasks. If the site has commercial functions, add a test of an order and an integration following a predefined scenario.
Specify the response time for different problems
A complete site outage, a broken inquiry form and a minor visual error do not have the same effect. Agree on incident categories, who reports them and when the response time starts running. Distinguish acknowledging the alert from resolving the problem: some failures also require work from the hosting provider or an external software vendor.
If nobody in the organization knows who pays for the domain and where the backups are, the first maintenance task is an inventory, not installing yet another plugin.

