Offboarding
Leaving is not deleting.
An employment record has to survive the employment, for a period set by law and by your own policy. Equally, it should not survive indefinitely because nobody decided otherwise.
Archived, with an end date
The record moves to an archived state and shows the date its retention period expires, so deletion is a scheduled outcome rather than a decision nobody makes.
Payroll and final pay inputs
Outstanding leave, final expenses and any deductions are collected as inputs for whoever runs payroll, rather than reconstructed afterwards.
What stays visible, and to whom
Work history stays visible where it must — a responsibility's history should not lose the name of who owned it — while personal detail closes behind the archive.
Offboarding
The rest of this area.
The full list of what has to move, produced from the record rather than from memory.
The leaver plan
One date in, one complete plan out.
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.
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]