Skip to main content

Handoff Acceptance Checklist

Owner: Anchor MSP Operations Lead Last reviewed: 2026-04-04

Purpose​

Use this checklist when a development team (EGI or Mast) hands a system off to Anchor for managed production. Every item must be verified and signed off before Anchor accepts ownership.

Checklist​

  • Acceptance criteria met. All items from the Managed Production Acceptance Criteria are satisfied.
  • Monitoring configured and producing data. Uptime Kuma checks are live. Prometheus is scraping metrics. Grafana dashboards are set up.
  • Alerts routing to correct Slack channels. Alertmanager rules are configured. Test alerts have been fired and confirmed in #alerts-critical, #alerts-high, #alerts-medium, #alerts-low.
  • Critical alert SMS escalation verified. A test critical alert has triggered SMS delivery via Twilio to the on-call operator.
  • Backups configured and first backup completed. Restic jobs are running. First backup has completed successfully. Backup metrics are reporting to Prometheus.
  • Secrets migrated to Vault. All secrets listed during acceptance criteria are stored in Vault. Application is configured to read secrets from Vault at runtime.
  • Access provisioned for Anchor operators. Anchor team has the access needed to operate, monitor, and troubleshoot the system.
  • Runbook created and reviewed. A system runbook exists using the Runbook Template. It has been reviewed by an Anchor operator.
  • Escalation contacts confirmed. Development team has provided contacts for application-level escalation (name, role, Slack handle, phone).
  • Development team acknowledges handoff complete. The development team confirms they understand Anchor now owns production operations for this system.

After Completion​

Once all items are checked, the system is officially under Anchor management. The handoff date is recorded and the system's runbook becomes the operational reference.