Offboarding
Laura is leaving on 31 October.
That sentence should produce a plan. Fourteen responsibilities, six systems, four active objectives, three customer relationships, two equipment items and one recurring approval — each with an owner and a date.
Everything, counted
The plan opens with the scale of the problem, because "fourteen responsibilities" is the number that makes a manager start early rather than on the final Friday.
Sequenced sensibly
Knowledge transfer and responsibility handover first, access revocation on the last day, equipment and payroll after. A plan that revokes access in week one is worse than no plan.
Works for contractors too
An engagement ending is the same problem in a smaller package, and it is the one companies almost always handle worst.
Offboarding
The rest of this area.
The full list of what has to move, produced from the record rather than from memory.
Responsibility transfer
Every owned responsibility gets a new name against it.
Access revocation
Every system, closed — including the ones nobody remembers.
Equipment return
Laptop, phone, card, vehicle — what is out and what came back.
Knowledge transfer
The part that actually walks out of the door.
Records & retention
Archiving an employment record properly, for the period you actually chose.
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]