Client Offboarding (W4)

The procedures for ending a SnowOps engagement — the inverse of onboarding (the GitHub Onboarder App (B1) + Azure Client Bootstrap Module (B2)). Ownership-aware: what is handed back vs torn down depends on each asset's [SO]/[CO]/[CA]/[SH] tag (gap G10).

Code → name lookup: docs/context/00-asset-glossary.md.

Contents

File	Use it for
client-offboarding.md	The full phased offboarding playbook — freeze & snapshot, knowledge transfer, identity teardown, repo/CI hand-back, state & secrets transfer, cost & monitoring, decommission (tear-down only), and final attestation. Covers both hand-back and tear-down engagement types, with a sign-off + client counter-sign block.

When to use

Trigger this playbook on contract end, a client bringing the platform in-house, or a vendor change. Read the ownership recap first, then work the phased checklist top to bottom — phases are gated and each leaves the platform in a consistent state, so it is safe to pause between them.