Client Offboarding¶

Owner: Bryan · Goal: end an engagement cleanly. Revoke access, hand over what the client is owed, and archive the rest.

The mirror of Client Onboarding. Work top to bottom; do not skip the access revocation.

Phase 1: Revoke access¶

Owner: Bryan

Zero Trust → Access → Applications → delete or disable the client's Access app, or remove their emails from the policy.
Confirm the client can no longer reach <slug>.dalayon.work or client-<slug>.pages.dev (incognito test).
Revoke our store access (remove staff account / disconnect any connector). Manual-export clients: confirm no standing access remains.

Done when: neither the client nor Dalayon retains access that the engagement no longer justifies.

Owner: Bryan

Produce the final report for the closing period.
If the client should keep their data or reports, export the content first (before archiving the repo).
Hand over anything contractually owed.

Done when: the client has their final report and anything they are owed.

Owner: Bryan

Cloudflare Pages → delete the project (or remove the custom domain).
Remove the DNS record for <slug>.dalayon.work if it is not auto-removed.
GitHub → archive or delete client-<slug> (only after any needed export in Phase 2).
Release the Access seat and clean up ClickUp / Slack / Drive as appropriate.

Done when: the hosting, domain, and repo are decommissioned and no orphaned resources remain.

Run a short retro. Fold anything learned back into the onboarding and delivery SOPs, and add any new trap to Gotchas.