Employee offboarding checklist

Checklist

Equipment back, keys back, access off, handovers done — and somebody named against each one.

Property and access, and nothing else

This is the list that stops a building access card staying live for a year and a laptop never coming back. Every row has somebody named against it, because a task owned by “HR” is a task nobody does.

What it will not hold: the reason for leaving, disciplinary history, a legal dispute, medical information, or a final-pay calculation. There is no field for any of them, and the form says so where somebody might otherwise start typing.

Work from what was issued

The PPE & equipment issue register already holds what each person was given and what is owed back — that is the list to work from. Keys signed in and out of the building have their own custody history in the key control log.

The same seam, run forwards

This is the onboarding checklist in reverse, on the same person record with the same stable id — which is why somebody who leaves and comes back is one person with two checklists rather than two people.

An operational separation checklist. It records no reason for leaving, no disciplinary or medical information, no legal matter and no final-pay calculation — there is no field for any of them. CompliMaint gives no employment-law advice and makes no compliance determination. Everything runs on your device.

Questions people ask

What belongs on an offboarding checklist?
The operational things that go wrong when nobody tracks them: equipment returned, keys and badges back, building and system access removed, company property accounted for, and the handovers that stop work disappearing with the person. Each with somebody named against it, because 'access removal' with no owner is how an account stays live for a year.
Can I record why somebody left?
No, and there is no field for it. A reason for leaving, disciplinary history, a legal dispute, medical information and a final-pay calculation are not operational, and a local browser tool is not where any of them should live. This checklist is about property and access.
Is access removal actually tracked?
As a task with an owner, a due date and a confirmation — which is all a checklist can honestly do. It connects to no system and disables no account: somebody has to do it and record that they did. What the tool provides is the list that makes the omission visible.
Does it link to what the person was issued?
The PPE and equipment issue register holds what was given to whom and what is owed back, per person, so it is the list to work from when somebody leaves. Keys signed in and out of a building are in the key control log, which keeps its own custody history.