# Website care scope and monthly report

Source: https://lindo.ai/guides/how-to-create-website-maintenance-plans
Updated: 2026-09-03
Published by: Lindo Team

Includes a responsibility matrix, baseline checks, incident updates, request tracking, and the monthly report template.
Illustrative planning aid, not market data or a guarantee. Do not store credentials or private client data here.

## Working brief

### Site / platform / domain owner / critical functions

- Notes:
- Owner / decision:
- Evidence / next action:

### Task / owner / frequency / evidence / exclusion

- Notes:
- Owner / decision:
- Evidence / next action:

### Backup scope / restore process / last verified test

- Notes:
- Owner / decision:
- Evidence / next action:

### Inherited issue / remediation scope / approval

- Notes:
- Owner / decision:
- Evidence / next action:

### Support channel / hours / priorities / response target

- Notes:
- Owner / decision:
- Evidence / next action:

### Request / approval / time / allowance

- Notes:
- Owner / decision:
- Evidence / next action:

### Incident timeline and provider escalation

- Notes:
- Owner / decision:
- Evidence / next action:

### Monthly evidence / open decisions / next review

- Notes:
- Owner / decision:
- Evidence / next action:

### Cancellation and handoff responsibilities

- Notes:
- Owner / decision:
- Evidence / next action:

## Acceptance checklist

- [ ] Site inventory and inherited issues are recorded.
  Owner / evidence / date:

- [ ] Agency, provider, and client responsibilities are separate.
  Owner / evidence / date:

- [ ] Backup coverage and restore capability are verified or explicitly limited.
  Owner / evidence / date:

- [ ] Request allowance, exclusions, and overage approval are clear.
  Owner / evidence / date:

- [ ] Support hours and response targets match actual staffing.
  Owner / evidence / date:

- [ ] Baseline tests and client approval contacts are established.
  Owner / evidence / date:

- [ ] Monthly reports contain evidence and unresolved decisions.
  Owner / evidence / date:

## Examples and templates from the guide

### Incident update template

Reported at / timezone:
Affected page or function:
Known visitor impact:
Checks completed and evidence:
Current owner: agency / provider / client / specialist
Temporary workaround, if tested:
Next update at:
Resolution or next action:
Post-incident prevention task:

### Monthly care report — copyable structure

Period and covered site:
Checks: [date, path, test, result, evidence]
Completed requests: [request, approval, work, time]
Incidents: [impact, owner, resolution, follow-up]
Open issues: [risk, next action, owner, due date]
Allowance used / remaining under the agreed rule:
Client decision needed:
Next scheduled checks:

## Working tables

### Illustrative care-plan responsibility matrix

| Work | Agency responsibility | Boundary / evidence |
| --- | --- | --- |
| Enquiry path | Scheduled authorized submission test | Record result and confirm receipt |
| Content edits | Agreed allowance from supplied material | Log time and approval; new layouts separate |
| Public-site check | Review named pages and links | Not a full security or accessibility audit |
| Platform incident | Triage and coordinate escalation | Provider controls infrastructure repair |
| Recovery | Only the documented supported process | Record backup coverage and restore-test status |

## Sources and next steps

- WordPress: updating and backing up before changes: https://wordpress.org/documentation/article/updating-wordpress/
- Calculate a selling price from the workload: https://lindo.ai/guides/how-to-price-website-design
- Stress-test recurring service costs: https://lindo.ai/guides/how-to-build-recurring-revenue-with-websites