TL;DR
- An offboarding checklist is the list of things that must happen when somebody leaves, and the equipment line is the only one that depends on a person who no longer works for you.
- If everybody hands their laptop to IT on their last afternoon, you do not need this. You need one owner and a drawer.
- Every other task on the list can be completed by somebody inside the company. That asymmetry is why the equipment step is the one that fails.
- The return rate is decided before the resignation, by whether the device has a known serial, a known recipient and a known address in a system somebody trusts.
- Ask on the last day, not after it. Access is the only thing you hold that the departing person still wants, and it expires the moment you revoke it.
- Measure recovery rate and days to return. If you cannot state both numbers, you do not yet know whether you have a problem worth paying to fix.
The Checklist That Was Fully Ticked
A 340-person company had a good offboarding checklist. Fourteen items, owned across HR, IT, payroll and the leaver's manager, tracked in the HRIS, and reviewed quarterly. Compliance liked it. It had been audited twice.
Thirteen of the fourteen items were completed on time, every time, for two years. The fourteenth was "equipment returned", and it sat at about 61 per cent. Nobody had noticed the gap because the checklist reported completion as an average, and thirteen out of fourteen is 93 per cent, which reads as excellent on any dashboard.
The thirteen items had something in common that nobody had articulated. Accounts closure, final pay, exit interview, reference letter, access revocation, pension notification, benefits termination: every one of them is completed by somebody who works there, using systems they log into, as part of a job they are paid to do. The equipment line is the only item on the list whose completion depends on a person who has already left, has no obligation they feel, and gains nothing from acting. Designing it like the other thirteen is why it behaves differently from the other thirteen.
Best tools for Device Management
So the useful question is not what goes on the checklist. It is which item needs a different mechanism.
When You Don't Actually Need This
When the manual way is genuinely fine
One office, under about forty people, low turnover, and a leaver who walks past the IT desk on their final afternoon. At that size the equipment step is a conversation and a cupboard, and the honest advice is to write it into the checklist, give it a named owner, and spend your attention elsewhere. The trigger is not headcount. It is the first leaver who is not physically going to be in the building again.
When friction starts appearing
The first signal is rarely a missing laptop. It is a returned laptop that then sits unopened for four months because nobody decided what to do with it. That is a redeployment failure rather than a recovery failure, and it is the cheaper of the two to fix. Recovery becomes the real problem the second time somebody leaves from a city where you have no office.
When it becomes a liability
The point where somebody outside the team asks for evidence. An auditor wants a device list with current locations. A security review asks when access was revoked on hardware you no longer hold. An acquirer asks what you own. The problem stops being that a laptop is missing and becomes that you cannot say how many are, which is a materially worse position to be in.
The edge case that forces it
A redundancy round or a market exit. Both produce a cluster of departures in a short window, often remote, often from people who are not feeling warm towards the company. A process that works for one amicable leaver a month does not survive eleven in a fortnight, and that is exactly when the return rate matters most and attention is scarcest.
Five Questions People Ask Before Rewriting the List
"Why does the equipment line fail when the others do not?" Because of who completes it. Twelve of your items are internal actions; this one is a request to somebody who has left. Treating it as a task with an owner inside the company produces a situation where the owner is accountable for an outcome they cannot deliver, which over time trains them to mark it complete and move on.
"When should we ask?" Before the last day, and the thing to understand is why. You hold exactly one piece of usable goodwill at that point: the person still wants their final payslip to be right, their reference to exist, and their access to work until Friday. The moment access is revoked, you have nothing they want and nothing to coordinate around. Most companies revoke access on day one of the notice period and then ask for the laptop on day thirty.
"Can we withhold final pay until the laptop comes back?" This is the most commonly asked question here and the answer is that it depends entirely on where the person is employed and on the terms that apply to them, and it is not something a checklist should assert. What any employer may or may not do with somebody's pay differs by jurisdiction and by individual circumstance, and the sensible route is local advice rather than a policy template. What you can do without any of that complexity is ask earlier and make returning easy.
"Should we post a prepaid box?" Yes, and the detail that matters is who books the collection. A label emailed to somebody who then has to arrange a drop-off puts the effort on the person with the least incentive. A scheduled collection from their address on a named day, arranged by you, converts the task from something they must organise into something they must be present for. The return rate difference between those two designs is large.
"What if they simply refuse?" A small number will, and the practical answer is to decide in advance what the device is worth to you and act accordingly. A three-year-old machine with a wiped drive and no remaining warranty is frequently worth less than the effort of pursuing it, and the right outcome is to record the loss, revoke everything, and close the asset record. What you must not do is leave it open indefinitely, because an open record that nobody is pursuing is the thing that corrupts the register.
Rebuilding the Equipment Line as Seven Steps
The fix is not a longer checklist. It is replacing one item with a short sequence that has its own timings.
One: confirm what they actually have, from the register, on the day notice is given. Serial, model, and anything else issued. If the register cannot tell you this in under a minute, that is the finding, and everything downstream depends on it.
Two: send the return arrangement in the first week of notice, not the last. While access still matters to them and while they are still in a working rhythm. The message should contain the device, the date, the method and what happens next, and nothing else.
Three: book the collection yourself, to a named date. Put the effort on your side. Their only obligation should be to be at an address at a stated time and to hand over a box.
Four: send packaging if the device needs it. A machine returned loose in a jiffy bag arrives damaged, which turns a recovery into a write-off and makes the whole exercise pointless.
Five: confirm receipt to them, by name, the day it arrives. This matters more than it sounds. People worry about having handed over company property with no acknowledgement, and the confirmation is also your audit record of the handover.
Six: wipe on arrival, not on reissue. Ending the data obligation at the moment the device enters your custody means anything that later goes missing from storage carries no exposure. Record the wipe with a date against the asset.
Seven: decide the device's next state within a fortnight. Reissue, store, sell or dispose. A device with no decision is a device in a cupboard, and the cupboard is where residual value goes to die.
The Message Itself
Step two above says to send the return arrangement in the first week of notice and lists what it should contain. That is still not a message, so here is the shape that works, and the reasoning behind each part.
Open with the specific device, not a category. "Your MacBook Pro, serial C02XK1…" rather than "company equipment". A specific object is a clear request. A category invites the recipient to decide what counts, and some of them will decide the monitor and the dock do not.
State the date and that you have booked it. "A courier will collect from you on Thursday 23rd between 9am and 1pm." Not "please arrange a return at your convenience", which transfers the work. The single biggest design error in these messages is asking somebody to organise something.
Confirm the address and ask them to correct it. One line, with the address you hold. For a remote employee this is often the delivery address from eighteen months ago, and a failed collection costs a week.
Say what happens to the data. "The device will be wiped on arrival and the wipe recorded." People worry about personal files and about being held responsible for company data later, and addressing it unprompted removes a reason to delay.
Say what you will send them. "We will confirm by email the day it arrives." This is a small promise that costs nothing and gives the handover an end point.
Leave out everything else. No policy extract, no reference to terms, no mention of consequences. A message that reads as a warning gets forwarded to someone for advice rather than acted on, and you have converted a logistics request into a dispute.
Two practical notes. Send it from a person rather than a no-reply address, because a return that needs one clarification will otherwise not happen. And send it in the language the person works in if that is not your working language, since this is a short, consequential message that will be read once.
When Departures Arrive All at Once
The edge case flagged above is the one that actually breaks processes, and it deserves its own handling because the one-at-a-time sequence does not scale by repetition.
The volume is not the problem. The simultaneity is. Eleven collections in a fortnight across six countries means eleven address confirmations, eleven courier bookings and eleven arrival checks landing on whoever owns the step, at exactly the time that person is also handling eleven access revocations and a great deal of difficult conversation. The step that gets dropped is the one with no internal deadline.
Decide the batch's disposition before the first collection. In a redundancy round or a market exit you already know these devices are not going to the next joiner in that country, because there is no next joiner. That makes the decision simpler than usual: the whole batch is store-centrally, sell or dispose, and settling it up front removes eleven individual judgements.
Appoint one owner for the window, not one owner per leaver. A single person tracking eleven returns on one list will do better than eleven managers each tracking one, because the eleven managers have other things happening that week.
Expect a lower return rate and plan for it. People leaving involuntarily return equipment less often, which is neither surprising nor a moral failing. Build the write-off into the plan rather than discovering it in the next audit, and set the threshold for pursuit before anybody is upset.
And run the collections on consecutive days where you can. One courier booking covering a block is less work than eleven, and it concentrates the arrival checks into a period somebody can actually staff.
One more thing that only shows up at volume: the arrival end needs as much planning as the collection end. Eleven devices turning up at one address over four days, with nobody expecting them and no space allocated, produces a pile that gets logged a fortnight later from memory. Tell whoever receives them how many are coming and when, give them the serial list, and have them confirm each one against it on arrival. That single list is the difference between a batch you can account for and eleven devices you believe came back.
Deciding What the Device Becomes
Step seven says decide within a fortnight and does not say how. Four outcomes, and the criteria are mostly arithmetic.
| Outcome | Choose it when | Watch out for |
|---|---|---|
| Reissue in region | Device has over a year of useful life and you have a likely recipient in that country | Needs regional storage, or you pay for two international shipments |
| Store centrally | Device is current but there is no near-term recipient | Set a review date, or it becomes cupboard stock nobody issues |
| Sell or buy-back | Device is serviceable but below your issue standard | Activation locks and missing serials sink batch quotes |
| Certified disposal | Genuinely end of life, or the data risk outweighs residual value | A recovery platform wipes; it does not certify disposal |
The field that decides most of these is the issue date, which is why it belongs on the register. A device nobody can age is a device nobody will make a decision about, so it defaults to storage, which is the outcome with the worst economics of the four.
What the Register Has to Hold
The return rate is largely determined before anybody resigns, by whether four facts exist and are trusted.
The serial number, tied to a person. Not a model, not a count. You cannot ask somebody to return a specific thing if you do not know which thing they have.
The shipping address it was delivered to. Frequently the only address you hold for a remote employee, and frequently stale by the time they leave. Confirming it at the start of the notice period is a thirty-second step that prevents a failed collection.
The issue date, so you can price the decision. Whether to chase a device is a commercial judgement, and it needs an age and a rough residual value.
Whether the data obligation is open. A device issued, never enrolled and never wiped is a different risk from one that was managed throughout. This field is the one most often absent entirely.
Everything else on a typical asset record is useful for other purposes and does not affect whether a laptop comes back.
How to Choose: Five Questions Before You Talk to Any Vendor
What is your actual recovery rate? Devices returned divided by devices issued to people who have since left, for the last twelve months. Most teams have never calculated it and are surprised by the answer. Without it you cannot tell whether you have a problem or an anecdote.
How many days does a return take? From last working day to device in hand. The gap between your best and worst case tells you more than the average, because the worst case is where write-offs live.
Did you procure the device yourself? This decides how much any tool can help you. A platform that handled procurement and delivery already knows the serial, the recipient and the address. A platform asked to recover a device somebody bought on a corporate card three years ago inherits exactly the incomplete register you already have.
How concentrated are your departures? Steady attrition is a process problem. Clustered departures are a capacity problem, and they need a route that can absorb eleven at once rather than one that works well for one.
What happens to devices after they come back? If the answer is "they go in a cupboard", fix that before buying recovery, because improving the return rate on devices you do not reissue just fills the cupboard faster.
Sequencing Revocation Against the Return
This is the interaction the whole article turns on, and most checklists get it backwards because the two items are owned by different teams who optimise for different things.
Security wants access gone early, which is correct and not in dispute. Equipment recovery wants a reason for the person to stay engaged, which is also correct. Treated as a conflict, security wins every time and should, so the resolution is not to delay revocation but to separate the things being revoked and to move the equipment ask ahead of the parts that matter to the leaver.
Revoke on day one of notice: anything that is a standing risk rather than a working tool. Administrative consoles, production access, customer data exports, payment systems, anything with a blast radius. None of this affects their ability to hand back a laptop and none of it is goodwill you are spending.
Keep to the last working day: email, calendar, chat, the HR self-service portal and the payslip system. These are the things the person actually wants during notice, and they are low risk on a device you are about to recover. This window is the only period in which you have anything to coordinate around.
Send the equipment arrangement inside that window, early. Day three to day five of notice is the sweet spot: the resignation has settled, the person is still in a working rhythm, and the systems they care about still function.
Revoke the device's own access at collection, not before. If the machine is enrolled, leave management in place until it is physically back, because a device you have locked remotely is a device with no reason to be returned and no diagnostic value when it arrives. Lock it the moment the courier confirms collection, not the moment notice is given.
Close the asset record only after the wipe is recorded. The sequence ends at the register rather than at the courier, and a record closed on collection rather than on verified wipe is the gap that shows up in an audit.
Two failure modes to watch. The first is the security-driven blanket revocation on day one, which is defensible on its own terms and reliably costs you return rate, so if that is your policy, accept the hardware loss and stop treating the recovery number as a performance problem. The second is the opposite: leaving production access live for a fortnight because somebody thought it would help get a laptop back. That trade is never worth it, and nobody should be asked to make it.
The practical test of whether you have sequenced this correctly is to ask who sends the equipment message and when. If the answer is IT, after the last day, you have the common arrangement and the common return rate. If it is a named person during the first week of notice, while the leaver still has email, you have the arrangement that works.
The Options, and the Pricing Problem
A note before the list, because it is the most striking thing about this category. Not one vendor whose primary product is device recovery publishes a price. Each was checked against its own pricing page, most recently on 7 and 9 October 2026. Some describe a model, and none attaches a figure to it, so budget for a sales conversation because there is no alternative route to a number.
RemoAsset
Disclosure: RemoAsset is owned by the same people who publish HROpsLab. It appears here because it competes in this category and is assessed against the same criteria as everything else on this page, with its limitations stated in the same detail.
Best for: teams that want the return to close a lifecycle they already run on one platform, rather than bolting a retrieval service onto a device bought somewhere else.
Why companies choose it: offboarding in the HRIS triggers the return automatically, so the step does not depend on anybody remembering. Because the same platform handled procurement and delivery, the device has a known serial, a known recipient and a known address before anybody needs to chase it, which removes the most common failure in recovery, which is not knowing what you are looking for. Recovered devices can be stored in region and reissued rather than shipped back to a head office.
Where it struggles: it publishes no price and requires a demo, so there is no way to size it without a sales process. It is meaningfully weaker if you did not also procure through it, because then it inherits the same incomplete register everybody else is working from. And it is not a certified IT asset disposition vendor: it wipes devices, but bulk end-of-life processing with disposal certification is a different purchase.
Workwize
Best for: teams wanting procurement, delivery and retrieval in one place across a wide set of countries.
Where it struggles: publishes no price, so the same sales-conversation caveat applies. Depth varies by country, so check your specific markets rather than the headline coverage number.
Deel IT
Best for: companies already running Deel for employment or contractor management, where equipment becomes an extension of an existing relationship.
Where it struggles: publishes no price. It is most compelling as an add-on and less so as a standalone equipment platform, so the decision is usually about the wider contract.
Firstbase
Best for: remote-first companies wanting the full issue-and-recover loop with a strong employee-facing experience.
Where it struggles: publishes no price. Like every platform here it is far more effective when it also handled the original delivery.
GroWrk
Best for: teams with staff spread across many countries, including ones the larger platforms cover thinly.
Where it struggles: names an a la carte option and a subscription model without attaching figures to either, so the comparison has to happen in a call.
allwhere
Best for: companies that want a managed service and are comfortable with a consultative buying process.
Where it struggles: consultation only, with no published pricing of any kind.
Doing it yourself with a courier account
Best for: under about thirty returns a year in countries you already ship to.
Why it works: the mechanics are not hard. A prepaid label, a booked collection and a tracked parcel solve most of the problem, and the reason platforms exist is coordination at volume rather than any courier magic.
Where it struggles: it consumes somebody's attention every time, it has no audit trail unless you build one, and it degrades badly under clustered departures. It also leaves the wipe and the reissue decision entirely to you.
What Each One Published
| Option | Publishes a price | Also handles procurement | Can store in region | Wipe included |
|---|---|---|---|---|
| RemoAsset | No, demo required | Yes | Yes | Yes, not certified ITAD |
| Workwize | No | Yes | Yes | Varies by market |
| Deel IT | No | Yes | Yes | Varies |
| Firstbase | No | Yes | Yes | Varies |
| GroWrk | No, model described | Yes | Yes | Varies |
| allwhere | No, consultation only | Yes | Yes | Varies |
| Courier account, in house | Yes, your own rates | No | Only where you have space | You do it |
Read the first column as the finding. In a category where buyers are comparing on cost, nobody publishes one, which means every comparison you make will be against numbers somebody gave you in a meeting.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| One office, leavers hand devices to IT | Under 40 | Checklist with a named owner | Nothing structural | Write the step down. Revisit when the first remote leaver goes |
| First few remote leavers, devices bought centrally | Under 200 | Courier account plus a booked collection | Effort sits with the person who has left | Book collections yourself. Measure the return rate for two quarters |
| Steady remote attrition, register is unreliable | 200 to 1,000 | Platform that also procures | Chasing a device nobody can identify | Fix procurement first, then recovery. Order matters |
| Devices procured centrally years ago, no serials | Any | Audit before anything else | Any platform inherits a broken register | Run the asset audit. A tool cannot infer what was never recorded |
| Clustered departures, redundancy or market exit | Any | Managed service with capacity | A one-at-a-time process collapses | Engage a platform for the window specifically |
| Returns arriving and sitting in a cupboard | Any | Reissue decision with a deadline | Residual value lost to indecision | Fix the fortnight rule before improving recovery |
| Bulk end-of-life processing with certification | Any | Certified disposal vendor | Recovery platforms wipe but do not certify | A certified ITAD vendor, not a recovery platform |
Measuring It Honestly
Four numbers, and the first two settle most arguments.
Recovery rate. Devices returned over devices issued to leavers, rolling twelve months. Report it on its own rather than inside a checklist completion average, because an average across fourteen items will always hide it.
Days to return. Last working day to device in hand. Watch the distribution rather than the mean; the tail is where write-offs are.
Value written off. The residual value of unreturned devices, which is the number that gets this work funded. A recovery rate of 61 per cent means nothing to a finance partner until it is expressed in money.
Time to reissue. Days from arrival to being back in service. This is the one that tells you whether recovery was worth doing, and it is routinely ignored because it sits with a different team.
What Getting This Wrong Costs
The direct cost is the hardware, and it is the smallest of the four. A written-off laptop two years into its life is a modest number, and companies absorb it without noticing precisely because it is modest.
The second cost is the record. A device you never recovered is a permanent gap in your data destruction evidence, because you cannot demonstrate the destruction of data on hardware you do not hold. That matters only when somebody asks, and when they ask it is not a small conversation.
The third is the compounding one. Every unrecovered device makes the register slightly less trustworthy, and a register nobody trusts stops being consulted, which means the next recovery starts from scratch. This is how a 61 per cent recovery rate becomes a 40 per cent one over three years without any single decision causing it.
The fourth cost is the one that lands on individuals and is worth naming because it is invisible from the centre. Somebody still holds a company laptop eight months after leaving, and most of those people are not keeping it deliberately. They were never asked clearly, or they were asked once by an address that no longer accepts replies, and the machine is now an object they are vaguely uneasy about and cannot get rid of. A few will have moved house with it. That is a bad experience you created, it happens to people who did nothing wrong, and it is the kind of thing that gets mentioned when somebody is asked what the company was like to leave.
So the question worth asking at the next review is not whether the checklist is complete. It is what your recovery rate was last year, and whether anybody could have told you without going and counting.
When You're Ready to Move Beyond a Spreadsheet
Most companies run this on a spreadsheet and a reminder, and for a long time that is the right answer. The spreadsheet is not the problem. The problem arrives when the number of people who update it exceeds the number of people who understand it, which is usually somewhere between the second and third country.
What makes it stop working is not volume but trust. A spreadsheet that is 80 per cent accurate is still useful. One that is 80 per cent accurate and that nobody is confident about gets double-checked every time it is used, and the double-checking is the real cost.
The sequence that works: calculate your recovery rate so the conversation has a number in it, confirm the four register fields exist for devices you issue from now on, move the ask to the first week of notice, and book collections yourself. Those four changes cost nothing and address most of the gap. Only then is it worth talking to a platform, and at that point you will be comparing vendors with a figure of your own rather than taking theirs.
Frequently Asked Questions
What should be on an employee offboarding checklist?
The standard items are access revocation, final pay, benefits and pension notification, the exit interview, return of equipment, handover of work and files, removal from systems and distribution lists, and closing the asset record. The useful insight is not the list itself but that one item behaves differently from the rest: every task except equipment return is completed by somebody who still works there, using systems they log into, as part of a paid job. The equipment line depends on a person who has left and gains nothing from acting, so it needs a different mechanism rather than just an owner.
When should we ask for the laptop back?
In the first week of the notice period rather than on or after the last day, and the reasoning is about timing rather than politeness. During notice the departing person still wants their final pay to be correct, their reference to exist and their access to work, which gives you something to coordinate around. Once access is revoked you hold nothing they want, and a request sent at that point competes with everything else in a new job.
Can we withhold final pay until equipment is returned?
What an employer may do with somebody's final pay depends on the jurisdiction they are employed in and on the specific terms that apply to them, so this is a question for local advice rather than one to settle from a policy template. It is also usually the wrong thing to focus on, because the companies with good return rates get them by asking earlier and making the return effortless rather than by applying pressure. Book the collection yourself, send packaging, and confirm receipt.
What is a normal device recovery rate?
There is no published benchmark worth quoting, which is itself worth knowing, and the figures companies report privately vary enormously with how they issue devices rather than how hard they chase them. The more useful comparison is against your own trend: calculate returns over issues to leavers for the last twelve months, then watch whether it moves. Teams that procure and deliver centrally, with a serial tied to a person and a confirmed address, consistently do better than teams that do not, regardless of what they spend on recovery.
How much do device recovery services cost?
Not one vendor whose primary product is device recovery publishes a price, checked against each vendor's own pricing page most recently on 7 and 9 October 2026. Some describe a model, such as an a la carte charge per order or a subscription tier, without attaching figures, and the rest offer a consultation. The practical consequence is that budgeting is a negotiation rather than a comparison, so go into those conversations with your own recovery rate and written-off value so you can judge whether a quote is worth it.
Should recovered laptops be reissued or disposed of?
Decide within a fortnight of arrival, because the decision costs more the longer it waits and a device with no decision ends up in a cupboard losing value. Reissue anything with meaningful life left and a clean wipe, especially if you can store it in the region it came from, since a domestic reissue avoids a second international shipment. Send genuinely end-of-life hardware to a certified disposal vendor rather than a recovery platform, since wiping a device and disposing of it with certification are different services.
Does recovery work if we did not buy the devices through the platform?
It works considerably less well, and this is the single most useful thing to understand before buying. A platform that handled procurement and delivery already holds the serial, the recipient and the address, which removes the most common recovery failure, which is not knowing precisely what you are looking for or where it went. A platform asked to recover devices bought on a corporate card three years ago inherits the same incomplete register you already have, so the honest first step is an asset audit rather than a recovery contract.
HROpsLab takes no vendor money and publishes no paid placements, which is why this page says "no published price" seven times rather than estimating.