# Django client website maintenance review

Website: [internal name]
Review window: [start and end, with timezone]
Reviewed by: [owner]
Evidence last received: [time; mark missing or stale sources]

## Check each maintained website

- [ ] Confirm external reachability and the last successful check.
- [ ] Review new and recurring errors; record affected routes and counts.
- [ ] Check failed jobs and work without a confirmed completion. Check whether
      an attempt is still running and whether replay is safe before retrying.
- [ ] Compare slow routes, query counts and database time with a comparable
      previous window. Investigate repeated queries; do not assume N+1.
- [ ] Review releases in the window. A nearby release is a lead, not proof
      that the release caused a problem.
- [ ] Record supported customer impact and what remains unknown. Do not
      infer lost revenue from an error count or a traffic change.
- [ ] Assign the next action, owner and review date. Rank urgent failures
      before planned work; treat missing telemetry as unknown, not healthy.

## Separate maintenance responsibilities

Monitoring does not complete these checks for you. Record the result or owner:

- [ ] Supported Django/Python versions and dependency/security updates.
- [ ] Backup status and a documented restore test.
- [ ] Domain/TLS renewal and hosting capacity.
- [ ] An agreed critical-journey test and incident contact/escalation route.
- [ ] At handover: repository/deployment access, monitoring ownership,
      agreed support scope, next review date and outstanding risks.

## Client-ready brief template

Review window: [start/end/timezone]
Observed: [one verifiable result and its source]
Customer impact: [supported evidence, or unknown]
Action taken: [actual change, or none yet]
Verification: [check, result and time; include unresolved limitations]
Next action: [owner and date]
Outside this review: [unavailable sources and checks not performed]

This is a blank template, not evidence that maintenance has been completed.
Before sharing, remove secrets, logs, request data and private customer details.
Include website identity only when necessary for the intended recipient.

Created by FetchNode: https://fetch-node.com/django-monitoring-for-agencies/