TL;DR
An employee termination checklist is normally strong on the things with a deadline attached. Final pay, access revocation, documentation. Equipment appears near the bottom as a line saying return company property, with no owner, no mechanism and no date. That line has the lowest completion rate on the whole document, and it is the only one with an asset attached.
- Revoke access on the day. Recover hardware on a schedule. They are different jobs.
- A line saying return company property is not a process.
- Say who arranges and pays for collection, or compliance collapses.
- Wipe on receipt, documented, not on trust.
- Record a disposal or reissue date so finance can close the asset.
- Treat involuntary exits differently. Goodwill is not available.
An employee termination checklist runs on two clocks
Access and hardware are treated as one task and they are not.
Access revocation is instant and has to be. The moment employment ends, the accounts close. That is a same-day job with no flexibility.
Best tools for HR Operations
Hardware recovery is a logistics exercise. It involves packaging, a courier, somebody being at home, and a destination. It cannot be same-day and pretending otherwise is why the line fails.
What happens when they are conflated
The checklist gets one tick box covering both. Access is revoked, the box is ticked, and the laptop is still in somebody’s spare room eight months later.
Separating them into two lines with two owners and two dates fixes most of it. Access owned by IT, same day. Recovery owned by whoever runs equipment, with a date two to three weeks out.
Say who arranges and who pays
The most common wording asks the departing employee to return equipment promptly. That asks somebody who is leaving, possibly unhappily, to find a box, source packaging, print a label and reach a drop-off point.
Compliance is predictably poor, and it is not really a compliance problem. It is a design problem.
| Approach | What the person must do | Typical outcome |
|---|---|---|
| Return it promptly | Everything | Poor, and slow when it happens |
| We will send a label | Find packaging, get to a drop-off | Better, still friction |
| We send packaging and book collection | Be at home once | Good |
| Courier attends with packaging | Hand it over | Best, and the most expensive |
Rows three and four are the only ones that work reliably across a distributed team. The cost difference per device is small next to the replacement cost of a laptop plus the unresolved data exposure.
Put it in the policy before you need it
A return arrangement stated in advance is a commitment. One improvised at exit is a negotiation. Our note on unreturned equipment covers recovery once it has already gone wrong.
The data side, which is the actual risk
A laptop that has not come back is not primarily a 900 pound problem. It is a machine holding company data in a location you do not control.
Remote wipe helps and is not a complete answer, because it needs the device to connect. A machine that is switched off in a drawer is beyond it.
the NCSC device security guidance treats device recovery and sanitisation as part of basic device security rather than an afterthought. the General Data Protection Regulation text on EUR-Lex is the relevant frame in Europe for what happens when personal data sits on a device outside your control, though whether a given situation requires anything in particular is a question for your own counsel.
Wipe on receipt, and record it
Returned devices should be sanitised to a documented standard rather than reformatted by whoever opens the box. NIST Special Publication 800-88 on media sanitization sets out what clearing, purging and destroying actually mean, and which is appropriate depends on what the device held and where it goes next.
Record the date. That record is what lets you say, truthfully and specifically, that a device was recovered and cleaned, which is the question that gets asked after an incident or during a security review.
Involuntary exits are a different problem
Most checklists are written for resignations, where there is notice, goodwill and a cooperative person.
An involuntary exit has none of those. Access often has to be revoked before the conversation, the person may be upset, and asking them to help with logistics is both awkward and unlikely to work.
Three adjustments worth building in.
- Arrange collection before the conversation. Not executed, arranged, so the offer is immediate and concrete.
- Do not make recovery a condition of anything. Linking final pay to equipment return is a legal question that differs by jurisdiction and a relationship question regardless.
- Accept a longer tail. Some devices take months. A process that assumes two weeks reports failure constantly and learns nothing.
the Acas guidance on dismissals covers the UK framework around dismissals, and the equivalent elsewhere differs, which is exactly why the equipment process should not be improvising legal positions at the moment of exit.
The decision table
Match the row to the exit type and the geography.
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Resignation, same country | Any | Notice period served | Nothing, usually | Prepaid collection in the last week |
| Resignation, another country | Series A+ | No local presence | No courier relationship | Partner-managed collection |
| Involuntary, immediate | Any | Access cut first | No goodwill available | Arrange collection before the meeting |
| Redundancy, several at once | Any | Known date | Volume on one day | Schedule collections across two weeks |
| Contractor ending | Any | Different contract | Terms may not cover it | Check the contract before assuming |
Row five catches people. An employee equipment clause does not automatically apply to a contractor, and the recovery position should be read from the contract that actually governs the relationship.
Closing the asset record
Recovery is not the end. The device has a next state, and finance needs to know which.
Reissued to somebody else, in which case the asset continues with a new holder. Held in stock, in which case it is idle but alive. Disposed of, in which case the asset should be retired with a date.
Leaving the row open is the default and it is how asset registers drift. Our piece on equipment depreciation covers why that missing date distorts both the balance sheet and the refresh budget.
Making it automatic
The reliable version triggers from the HR system rather than a human remembering. When a leaver date is set, the equipment task is created with the device list already attached.
For teams without local presence in the markets they hire in, RemoAsset runs collection from departing employees and can hold returned devices until they are reissued, which turns the longest step into a booking rather than a project.
Use the notice period, not the last day
Most checklists schedule everything for the final day, which is the worst possible moment. The person is finishing handovers, saying goodbye and has no interest in packaging a laptop.
Book the collection during the notice period instead, for a date a few days after the last working day. The person is still contactable, still has the device, and the task is no longer competing with their final afternoon.
Where notice is short or non-existent, that window does not exist and the collection has to be arranged alongside the conversation itself. Those are different situations and the checklist should say which applies, rather than leaving whoever runs the exit to improvise a sequence under time pressure on the day.
RemoAsset collects, wipes and stores equipment from leavers wherever they are. More on offboarding at HROpsLab.
Frequently asked questions
What is usually missing from an employee termination checklist?
A working equipment process. Most checklists handle the items with hard deadlines well, since final pay and access revocation have obvious dates, then cover hardware with a single line saying return company property. That line has no owner, no mechanism and no date, which is why it has the lowest completion rate on the document despite being the only item with a physical asset attached to it.
Should access revocation and device recovery be on the same timeline?
No, and conflating them is the common design error. Access revocation is same-day and non-negotiable. Device recovery is a logistics exercise involving packaging, a courier and somebody being at home, so it realistically runs two to three weeks. One tick box covering both means the box gets ticked when access is cut and the laptop stays in a spare room. Two lines, two owners, two dates.
Who should pay to return equipment when someone leaves?
The company, and the arrangement should be stated in policy before it is needed. Asking a departing employee to source packaging, print a label and reach a drop-off point produces predictably poor results, and it is a design problem rather than a compliance one. Sending packaging and booking a collection, so the only thing required is being present, costs very little next to a replacement laptop and an unresolved data exposure.
How should involuntary exits be handled differently?
Arrange the collection before the conversation happens, so the offer is immediate and concrete rather than improvised afterwards. Do not make equipment return a condition of anything, since linking it to final pay is a legal question that varies by jurisdiction and a relationship question regardless. And accept a longer tail, because a process assuming two weeks will report failure constantly without learning anything.
Is a remote wipe enough if a device is not returned?
It helps and it is not a complete answer, because a remote wipe requires the device to connect. A machine switched off in a drawer is beyond it indefinitely. That is why physical recovery matters even when the hardware itself has little residual value: the exposure is the data on a machine in a location you do not control, not the replacement cost of the laptop.
What should happen to a device once it is returned?
Sanitise it to a documented standard rather than reformatting it, and record the date. Clearing, purging and destroying are different things and which is appropriate depends on what the device held and where it goes next. The record is what lets you state specifically that a device was recovered and cleaned, which is the question that arrives during a security review or after an incident.
How do we stop the equipment step being forgotten?
Trigger it from the HR system rather than relying on somebody remembering. When a leaver date is set, the equipment task should be created automatically with the device list already attached, so nobody has to look anything up. If your asset records and HR system do not connect, that lookup is manual and will sometimes be skipped, which is reliably the case where it mattered most.