Daily weekly and monthly operator checklists

Prerequisites and authority

Assign an operator and an authorized technical owner. Data-replacing recovery and updates require a maintenance window, preserved recovery point and known target.

Daily, weekly and monthly routines

Use the editable maintenance checklist included in templates. Record operator, local date/time, outcome, exception and follow-up for each check.

Daily

Confirm application access and API/service health.
Review worker progress, failures and unusually long operations.
Inspect router reachability and provisioning exceptions.
Reconcile payment/activation complaints and pending records.
Check last backup, local/off-site availability and warnings.
Check disk headroom, license warnings and open incidents.

Weekly

Review failed jobs, repeated incidents and accounting discrepancies.
Verify a retained backup and confirm off-site retrieval.
Review staff sessions and changed permissions.
Inspect management routes/firewall exceptions and diagnostic access.
Check report/financial totals and export context where required.
Review upcoming updates and maintenance requirements.

Monthly

Perform or review an isolated restore drill.
Audit recovery prerequisites, key custody and replacement-host plan.
Review capacity trends, storage growth and retention suitability.
Review access/integration credential lifecycle and license renewal timing.
Confirm documentation remains compatible with the installed release.
Assign permanent fixes for recurring operational workarounds.

After update or recovery

Repeat API/admin/customer acceptance, worker runs, router access, payment/subscription checks and backup verification. Record the actual version and any residual issues.

These are recommended schedules. Worker execution cadence and product defaults are separate reference facts requiring release verification.