Agree the scope explicitly
Maintenance may include software updates, backups and checks; content changes, hosting and emergency work may be separate. Ask for the included tasks, exclusions and responsibilities in plain language.
Test updates and recovery
Decide how important updates are checked and what happens if an integration breaks. A backup needs defined contents, retention and a tested restoration route. Do not assume a successful update means every customer task still works.
Manage renewals and access
Track domain, hosting, certificates and subscriptions with the people responsible for them. Keep ownership and appropriate supplier access documented. A maintenance arrangement should not make recovery depend on an unknown shared password.
Review useful outcomes
Check key forms, payments, navigation and outdated business details on a suitable schedule. No generic monthly package guarantees uninterrupted service, a fixed search ranking or coverage of every possible fault.
Ask about a broken form
If a software update stops enquiry delivery, find out who notices, who investigates and whether restoration is included. A plan listing updates and backups alone may leave those responsibilities undefined.
Questions about this guide
What should a maintenance agreement specify?
List the sites, updates, backup checks and support included, plus exclusions and agreed response arrangements. Avoid assuming redesigns or content changes are included without written scope.
How should completed maintenance be reported?
Request a concise record of what changed, checks performed and anything still needing attention. This helps distinguish a completed update from an unresolved fault.