Leader offboarding

Last updated May 11, 2026File: content/operations/offboarding.mdx

When a leader rolls off the team — graduated, moved on, or stepped back — this is the checklist. The goal is a clean handoff with no orphaned access.

Knowledge transfer

  • Identify a successor or interim owner for each of their responsibilities
  • Schedule a 60-minute handoff meeting with each successor
  • Update any SOPs they wrote/owned with the new owner
  • Hand off their Slack DMs/threads — share relevant context

Access removal

  • Remove from leadership Slack channels (keep them in the main community)
  • Remove from the leadership Google Group
  • Remove from the GitHub org (or downgrade to read-only)
  • Remove from Vercel team
  • Remove from any shared password managers (1Password, etc.)
  • If they had access to credentials in admin/credentials, rotate those credentials

Documentation

  • Remove from Leadership roster
  • Post a thank-you in #announcements
  • Update org chart if maintained externally
Always rotate shared credentials

Even if the departure is amicable, any password or API token they had access to should be rotated. This is good hygiene, not a statement of trust.