An employee departure can leave approval requests addressed to someone who can no longer decide. Revoke authority, review pending proposals, and reassign responsibility without treating old links as permanent permission.
Approval continuity needs current authority
Departure handling removes or changes access under the organisation’s established process and identifies work the employee owned. Approval proposals, delegated roles, notification destinations, and already authorised but unexecuted actions need explicit treatment.
For a proposed review, inventory pending decisions, temporary delegation, approval channels, open sessions, and execution jobs linked to the person. Use trusted personnel and access records as the trigger, not an AI inference about employment status.
The actual legal and organisational obligations depend on the deployment. This article describes technical continuity and permission checks, not a universal employment or records-retention rule.
Test a fictional manager handover
A manager leaves with five pending proposals. The access process removes decision authority and assigns the queue to an authorised replacement. A late click from the former manager’s open browser must follow current policy and not approve a new action.
One proposal was approved before departure but remains queued. The business must define whether that prior decision remains valid, needs reassessment, or is withdrawn. Preserve the historical decision while applying the current execution policy.
| Departure case | Required handling |
|---|---|
| Pending request | Reassign to current authorised owner |
| Late approval attempt | Current authority checked |
| Temporary delegation | Expiry or revocation reviewed |
| Earlier valid approval | Apply explicit post-departure execution policy |
| Reminder destination | Stop sending to inactive responsibility |
Test the decision API, notification channel, and worker path. Removing a name from the main dashboard does not establish that every old approval link and queued job respects revocation.
Preserve history without preserving privileges
Keep the approved audit evidence under the actual retention policy. A departed actor can remain identifiable in historical decisions without retaining present access. Reassign operational ownership of unresolved effects and escalation duties.
Central identity management can simplify the process, but service-specific accounts and external channels may remain. Maintain the inventory and verify supported session and link behaviour. Any authorised exception needs a clear scope and expiry.
This continuity design is proposed. The HVAC case study documents staff access without claiming this departure workflow. Pair it with employee access review.
Departure approval FAQ
Should pending requests be deleted?
Usually preserve their business context and reassign or close them under the defined policy.
Does a past approval automatically become invalid?
The business must define that rule; historical truth and current execution authority are separate concerns.
What proves the handover is complete?
Current access is verified, pending work has owners, notification routing is corrected, and unresolved exceptions are explicit.