Offboarding
Exit without data loss, without licence gaps, and with traceable history.
Problem
Offboarding risks three mistakes: removing productive rights too early, keeping billable licences too long, and undocumented exceptions (leave, executives, project accounts). Helpdesk and HR use different lists; the admin centre shows no rationale trail. Later, audit asks who changed assignments and on what basis.
Approach with CHAOS
CHAOS maps offboarding rules to identity and group state: which SKUs at which HR status, which leave phase, which exceptions via approvals. Writes can be policy-bound; each change produces audit trail with rule reference. Exceptions become tickets/rules instead of chat history.
Outcome from CHAOS
Reduced over-licensing after exit, fewer escalations from premature removals, and defensible exports for internal control. Security benefits because access and licences move together.
Insight
Offboarding is high frequency: modelling pays back quickly. Tie HR master data to technical signals early to minimise manual reconciliation.