A useful website-maintenance agreement states what is covered, who is responsible and how work is requested. “Maintenance included” is too broad to explain the practical support a business can rely on.
List the systems included
Identify the website, hosting environment, domain, business email and external services covered by the arrangement. Some may be supplied by different companies. Record who controls each account and who approves changes, renewals and additional costs.
Explain the current website’s condition before agreeing ongoing support. An existing fault, unsupported component or unfinished integration may need a separate assessment rather than being treated as routine maintenance.
Define updates and change work
Agree which software updates and routine checks are included, how changes are reviewed and where they will be applied. Where appropriate, use a staging copy and an agreed rollback route before changing important production functions.
Content edits, new pages, redesign work and new integrations should have clear boundaries. Specify how requests are submitted, who can authorize them and how work outside the agreed scope is estimated.
Distinguish backups from restores
Record what is backed up, how often backups are taken, where they are stored and how long copies are retained. Confirm who can access them and whether a copy remains available if the hosting account itself becomes inaccessible.
A backup file and a demonstrated restore are different things. Agree whether restore checks and actual incident recovery are included, what access is needed and how restoration work is approved. Do not assume a guaranteed recovery time or zero data loss unless those commitments are explicitly agreed and supported.
Describe monitoring accurately
Monitoring should identify what is being checked and how a finding is communicated. A sampled HTTP response can provide a useful availability signal, but it does not establish that checkout, email, logins or every page works correctly. It also does not measure a complete visitor experience or establish an uptime guarantee.
DeshTech’s Website Status resource explains its recorded website checks and their limits. Read the methodology when interpreting any monitoring output.
Agree access and communication
Identify the people authorized to request work and grant the access needed for their responsibilities. Keep domain, hosting, website and email ownership clear. Access should be reviewed when staff, suppliers or maintenance responsibilities change.
Confirm normal support coverage, escalation contacts and any response targets in the proposal. A response target, the start of investigation and a resolved incident are separate expectations. The agreed arrangement should make that distinction clear.
Keep a simple maintenance record
Website and services covered, with responsible account owners.
Included updates, checks and content tasks.
Backup scope, retention and restore arrangements.
Monitoring method, reporting and known limits.
Support contacts, coverage and agreed targets.
License, hosting, domain and email renewals.
Changes completed, remaining issues and handover information.
Review the arrangement whenever the website adds important functions or the business changes providers. An online store and a small information website may need different operational checks and support responsibilities.
Comments are closed