An update needs verification
WordPress, its theme and plugins work together. Before a change, consider compatibility and a rollback route; test significant updates on an isolated copy. Afterwards, checking the homepage is not enough: test navigation, forms and other essential functions. The scope and frequency of this work should be agreed as part of maintenance.
A backup needs a recovery route
Agree who backs up files and the database, where copies are stored and how recovery works. “Backups enabled” does not prove that a restore will succeed. For a site receiving data, consider changes since the latest backup. Domain and hosting access should remain under the owner’s control.
Check contact and content
A form can look correct while email delivery fails. Periodically follow a real enquiry journey and confirm receipt. Update outdated offers, contact details, links and information documents. Every language needs the same review; editing one version does not automatically update the others.
Separate maintenance from development
Fixing an update-related error, adding an integration and restructuring an offer are different tasks. Record what maintenance includes, how to report problems and how priorities are set. Plan improvements around customer questions, search data and user behaviour. Do not assume response times or a quantity of changes unless agreed in the proposal.
A maintenance routine with evidence
Before updating, record versions, check available backups and agree restoration steps. On a test installation, check key views, forms, languages and functions dependent on the changed component. After release, clear cache and repeat checks while logged out. Record the date, versions and result; a successful installer message is not enough.
How to report a problem
Include the page URL, device, steps and expected outcome. For example: “on mobile, the send button remains disabled after choosing a service and completing required fields”. Keep passwords and other people’s data out of screenshots. Agree who receives reports and which changes need a separate quotation.
A backup listed in a dashboard does not prove restoration works. Test restoration away from production and avoid replacing recent enquiries or orders with an older database.