Offboarding and access revocation

Offboarding is the workflow that gets dropped, and the cost shows up months later. Email, code repositories, and shared drives stay open because nobody owns a revocation list, credentials in personal accounts are never collected, and the exit conversation happens weeks after the person has left. This workflow starts when a resignation is recorded. It builds the list of every account still assigned to that person, gives each one an owner and a due date, and lines the revocation up with the last working day rather than a convenient week later. In parallel, the exit conversation is scheduled while the person can still answer properly, and the notes are grouped into themes alongside the work those themes point at. A human still decides what happens to shared files and personal credentials, and chooses which themes are safe to share more widely. The workflow closes the record on time and keeps the learning; it does not replace the conversation.