Offboarding
Nothing should be forgotten when someone leaves.
Tell Orglume that Laura is leaving on the thirty-first and it can tell you exactly what that means: the responsibilities she owns, the systems she can reach, the objectives in flight, the customers who know her, the equipment she has and the approvals that route through her.
The list is generated, not remembered
Offboarding fails because it depends on somebody recalling everything a colleague did. The whole point of recording responsibilities, access and knowledge is that this list can be produced.
Transfer before revoke
Cutting access on the last day without moving the work first is how a company locks itself out of its own processes. The order matters and the plan enforces it.
It ends with a clean record
Every item transferred, revoked, returned or explicitly accepted — and an employment record archived under the retention period you actually chose.
In this area
6 pages under Offboarding.
Each one is its own surface in the product, and each one is here because it does something the others do not.
The leaver plan
One date in, one complete plan out.
ReadResponsibility transfer
Every owned responsibility gets a new name against it.
ReadAccess revocation
Every system, closed — including the ones nobody remembers.
ReadEquipment return
Laptop, phone, card, vehicle — what is out and what came back.
ReadKnowledge transfer
The part that actually walks out of the door.
ReadRecords & retention
Archiving an employment record properly, for the period you actually chose.
ReadThe rest of Orglume
This is one part of one loop.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]