TL;DR
- IT asset recovery is the work of getting company hardware back from somebody who no longer works for you. Contacting them, shipping them packaging, tracking the return, then wiping and reissuing the machine.
- If everybody works in one office and hands their laptop to IT on the last day, you do not need this. You need a checklist and somebody who owns it.
- Four jobs sit underneath it: making contact, moving the device, proving the data is gone, and deciding whether the machine goes back into service or out of it.
- The market splits into recovery platforms built to get one laptop back from one person at home, and disposition vendors built to process hardware that has already reached a warehouse. Both use the word recovery.
- Not one vendor in this category publishes a price. Every figure comes from a sales call, which makes budgeting a negotiation rather than a comparison.
- Measure recovery rate and days to return. If you cannot state both numbers today, you do not yet know whether you have a problem worth paying to solve.
The Laptop That Was Still in a Flat in Lisbon
A 210-person company ran a clean offboarding process. Accounts closed the same afternoon, final pay calculated correctly, exit interview booked and held. Eight months later an auditor asked for a list of devices issued in the previous two years and their current location. Fourteen laptops could not be accounted for. One of them belonged to a developer who had left in March and had, it turned out, been perfectly willing to return it. Nobody had ever asked him.
That is not a story about a careless employee. It happens because returning a laptop is the only offboarding step that depends on somebody outside the company doing something, and every other step was designed around people inside it. HR closed its tasks. IT closed its tickets. The laptop was nobody's ticket, because the person who had it was no longer in any system that generates tickets.
The real issue is not logistics. Couriers are not the hard part, and they have never been the hard part. Asset recovery fails at the moment somebody has to ask a departing person for something, clearly and promptly, in a way that makes complying easier than ignoring it. Every platform in this category is selling a solution to that moment, and the ones that work are the ones that own the conversation rather than handing you a shipping label.
Best tools for Device Management
This is what IT asset recovery is supposed to solve.
When You Don't Actually Need IT Asset Recovery
When the manual way is genuinely fine
One office, under about 40 people, low turnover, and a leaver who walks past the IT desk on their last afternoon. At that size recovery is a conversation and a drawer. Buying a platform adds a vendor relationship and removes nothing, and the honest advice is to write the step into your offboarding checklist and give it an owner.
When friction starts appearing
The first real signal is not a missing laptop. It is a laptop that came back and then sat in a cupboard for five months because nobody decided what to do with it. That is a redeployment failure rather than a recovery failure, and it is cheaper to fix. Recovery becomes the problem when the second person leaves from a city with no office in it.
When it becomes a liability
The cost of not having a process exceeds the cost of having one at the point somebody outside IT asks for evidence. An auditor wants a device list with locations. A security review asks when access was revoked on hardware you no longer hold. An acquirer asks what you own. At that moment the problem stops being that a laptop is missing and becomes that you cannot say how many are.
The edge case that forces it
A redundancy round, or a country exit. Both produce a cluster of departures in a short window, often remote, often with 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 recovery rate matters most and attention is scarcest.
Five Questions People Ask Before Buying
"How many are we actually missing?" Most teams cannot say. The number usually comes out worse than the guess, because the devices that went missing earliest are the ones least likely to be on any current list.
"Who contacts the person who left?" Whoever owns this has to be comfortable chasing somebody with no obligation to reply. If the answer is an IT generalist doing it between tickets, the recovery rate will reflect that.
"What happens when the device just never arrives?" Every vendor has a story for the happy path. The difference between a service and a shipping label is what happens on day twenty-one, and how that gets reported to you.
"Can we put the machine back into service?" A recovered laptop that is wiped and reissued is worth a great deal more than one that is recovered and recycled. Whether that is possible depends on where the device is stored and what condition anybody checks it in.
"What does this cost per device?" Nobody in this category will tell you without a call. That is the honest answer and it is worth knowing before you start, because it shapes how long the evaluation takes.
The Two Halves of This Market
Recovery platforms
What it is. Software and logistics built to retrieve one device from one individual, usually at home, usually in a country where you have no office.
When it's right. When the devices you cannot account for are in people's houses. The platform contacts the leaver, sends prepaid packaging, chases non-responders, and tells you where each device is in the process.
When it fails. It does not help with hardware that has already reached you. If you have 300 end-of-life laptops on a pallet and need them processed, certified and resold, a recovery platform is the wrong purchase and an expensive one.
IT asset disposition vendors
What it is. Bulk processing of hardware that has arrived somewhere central: data destruction to a documented standard, certification, resale or recycling.
When it's right. When the problem is volume and compliance at the end of life, and the devices are already in your possession.
When it fails. It cannot get a laptop out of a flat in Lisbon. ITAD vendors are built around pallets and collections from business addresses, and a request to chase one individual is outside what they do.
The arrangement most teams end up with
Recovery in front, disposition behind. Devices come back through a recovery process, get triaged, and the ones worth reissuing go back into service while the rest go to an ITAD vendor for certified destruction. It works provided somebody owns the handoff between them, which is the step that gets dropped.
| Half of the market | What it does | Right when | Fails when |
|---|---|---|---|
| Recovery platforms | Retrieves devices from individuals | Hardware is in people's homes | You need bulk certified destruction |
| ITAD vendors | Processes hardware in bulk | Devices already reached you | The device is in somebody's flat |
| Both, in sequence | Recover, triage, then dispose | You have volume and an audit obligation | Nobody owns the handoff |
Working Out Your Real Recovery Rate
This is the number the whole decision turns on, and almost nobody has it. Here is how to produce it in an afternoon.
Pull every leaver from the last twelve months. For each one, answer three questions: were they issued a company device, did it come back, and how many days did that take from their last working day. If you cannot answer the first question for some of them, that gap is itself a finding and it is usually the largest one.
Then compute two numbers. Recovery rate is devices returned divided by devices issued to leavers. Days to return is the median, not the mean, because one laptop that took 240 days will drag an average somewhere useless.
| What you find | What it means | What to do first |
|---|---|---|
| Recovery above 90 per cent, median under 14 days | The process works | Leave it alone, measure quarterly |
| Recovery above 90 per cent, median over 45 days | People comply, nobody chases | Fix the prompt and the packaging, not the tooling |
| Recovery 60 to 90 per cent | Ordinary for a distributed team with no platform | A recovery platform pays back here |
| Recovery below 60 per cent | Nobody owns the step | Assign the owner before buying anything |
| Cannot establish what was issued | An inventory problem wearing a recovery costume | Fix the register first; recovery depends on it |
That last row catches more teams than any of the others. A recovery platform cannot retrieve a device nobody recorded issuing, and buying one before the register is accurate produces an expensive tool pointed at an incomplete list.
What Happens in the First Seventy-Two Hours
Recovery rates are set early, and almost everything that determines them happens in the three days around somebody's last working day.
The ask has to arrive while the relationship is still warm. A request sent on the final Friday lands very differently from one sent five weeks later, when the person has started somewhere else and has no reason to think about you. Most of the gap between a 95 per cent recovery rate and a 65 per cent one is explained by that timing, not by courier coverage.
It has to be trivially easy to comply with. Prepaid packaging that arrives at their address, a label already printed, and a collection they do not have to arrange. Every step you leave to the person is a step where this stops.
Somebody has to be named. Not a department. A person who notices on day ten that the box has not moved, and sends a short, friendly message. Automation handles the first contact well and the third contact badly.
And the person needs to know what happens to their data. A surprising share of non-returns are not refusals. They are people who have personal photographs on a work machine and no idea whether returning it means losing them. One sentence about this in the first message measurably helps.
So treat the first seventy-two hours as the product. The platform you buy is mostly a way of making those three days happen reliably when nobody is watching.
Writing the Message That Gets the Laptop Back
The article so far has twice told you to fix the prompt, which is easy to agree with and useless without the actual content. So here is what a first contact needs to contain, and why each part is there.
Say what you are asking for, specifically. Not "please return company property". The make, the model and, if you have it, the serial. People own several devices and a vague request invites a vague reply, or none.
Say when, with a real date. An open-ended request is a request with no deadline, and it competes with everything else in somebody's first fortnight at a new job. A date ten working days out is generous and still a date.
Say what arrives and when. The packaging is coming to them, prepaid, with the label attached, and all they do is put the laptop in it and hand it over. Every task you leave with the person is a place this stops, and "arrange a collection" is where most of them stop.
Say what happens to their personal files. This is the part teams leave out and it is responsible for a surprising share of silence. Somebody with family photographs on a work machine will delay indefinitely rather than ask. One sentence telling them to copy anything personal off first, and confirming the drive will be erased, removes that.
Say who they can reply to, by name. A no-reply address signals that nobody is reading, which is usually accurate and always counterproductive.
And then send the second message on day ten, from a person, short. Not a reminder template. Something closer to "the box should have reached you last week, has it turned up?" The third contact, if it is needed, should come from somebody senior enough that it reads as mattering, and that is where automation genuinely stops helping.
Teams that rewrite this message typically see the change before they see anything from new tooling, which is worth knowing before a procurement cycle starts.
Rebuilding a Register You No Longer Trust
The decision table above sends several rows here first, so it is worth being concrete, because "fix the register" is the kind of advice that gets agreed with and never actioned.
Do not try to reconstruct history. A full audit of every device ever issued stalls, and it stalls in a way that convinces everybody the work is impossible. Instead, draw a line at today and build forward from three sources you already have.
Start from purchasing, not from IT. Finance has the invoices, and an invoice is evidence a device exists. That list is usually more complete than the asset register, because somebody always had to pay.
Match against identity. Your SSO or directory tells you who is active. Devices that appear in a management console but belong to nobody active are your immediate recovery candidates, and that intersection is normally a short and uncomfortable list.
Then confirm with the people who have them. A single message to current staff asking them to confirm the make and serial of the machine they are using gets a response rate far above what anybody expects, because it costs them nothing and it is not a trick. That closes most of the remaining gap in one pass.
Whatever is still unaccounted for after those three steps is the real number. Write it down, accept it as the starting position, and apply the recovery process from here forward rather than trying to recover devices issued four years ago to people nobody remembers. But do record the write-off explicitly, because an auditor would rather see a documented gap than discover an undocumented one.
How to Choose: Five Questions Before You Talk to Any Vendor
What is your recovery rate today? If you cannot state it, do that first. Vendors will ask, and an evaluation conducted without it turns into a feature comparison rather than a decision about whether you need this at all.
Where are the devices you cannot account for? List the countries. The answer determines everything, because coverage varies enormously and a vendor strong in the United States and Western Europe may have nothing useful in the markets where your gap actually is.
Who will own this in six months? Recovery is a process with a human in it, and the human changes. Ask who sends the day-ten message, and whether that is in anybody's objectives. A platform with no owner reverts to a shipping label.
Can recovered hardware be stored regionally and reissued? Shipping a laptop from Portugal back to London and out again to Poland destroys the economics of reusing it. If a vendor cannot hold devices near where they were recovered, the recovered machine is worth much less than it looks.
What do you need to prove, and to whom? If the answer involves an auditor, you need documented data destruction, not an assurance that the device was wiped. That requirement changes the shortlist, and it is cheaper to establish now than after the first certificate request.
Seven Options Worth Knowing
A note on pricing before the list, because it is the most striking thing about this category. Not one of these vendors publishes a price. Each was checked against its own pricing page on 6 and 7 October 2026. Some describe a model, GroWrk names an a la carte option charged per order and a subscription tier, allwhere describes pay-as-you-go and fixed rates, but none attaches a figure to it. 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 recovery to close a lifecycle they already run on one platform, rather than bolting a retrieval service onto a device they 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 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 if your requirement is bulk end-of-life processing with disposal certification, that is a different purchase.
Workwize
Best for: IT-led teams that want warehousing and recovery in the same platform across several regions.
Why companies choose it: regional storage is the real differentiator, because it makes reissuing a recovered laptop practical rather than theoretical. Strong coverage across Europe.
Where it struggles: quote-based with a demo required. The breadth suits teams running a genuine multi-region fleet and is overhead for a company with people in three countries and forty laptops.
Deel IT
Best for: companies already running Deel for employment or contractor payments who want equipment handled in the same relationship.
Why companies choose it: the offboarding signal already exists in the system, which removes an integration and a handoff. For teams hiring through Deel internationally it is the shortest path.
Where it struggles: pricing is quote-based. It is most compelling as an extension of an existing Deel relationship, and considerably less so as a standalone recovery purchase.
Firstbase
Best for: teams thinking about the whole remote setup rather than the laptop alone.
Why companies choose it: it covers desks, chairs and peripherals as well as computers, which matches what companies actually issued during the shift to remote work and now need to recover.
Where it struggles: no published price. The broader equipment scope is an advantage only if you issued broader equipment; for a laptop-only fleet it is paying for coverage you will not use.
GroWrk
Best for: recovery in markets where the large providers are thin, particularly Latin America and parts of Asia.
Why companies choose it: in-country presence in places where other vendors subcontract, which shows up directly in how long a retrieval takes and whether it happens at all.
Where it struggles: it publishes no figures. Its own pricing page names an a la carte model charged per order and a subscription tier called Flex, then routes to a form, so even the shape of the cost needs a call to establish.
allwhere
Best for: United States-led companies with international staff and real deployment complexity.
Why companies choose it: strength in the depth of the deployment workflow rather than only the shipping, which matters when devices need configuring before they reach somebody.
Where it struggles: pricing is a consultation. Its page offers a tailored snapshot and a custom quote and shows no rates, so comparison against alternatives cannot be done on paper.
A certified ITAD vendor
Best for: the other half of the problem, once hardware has reached you in volume.
Why companies choose it: documented destruction to a recognised standard, with certificates an auditor will accept, plus resale channels that return some value.
Where it struggles: it will not retrieve anything from an individual. Teams that buy an ITAD contract expecting their non-return problem to improve are solving the wrong half, and this is the single most common misdirected purchase in the category.
What Each One Published
| Option | Published price | Unit | Half of the market |
|---|---|---|---|
| RemoAsset | Not published, demo required | n/a | Recovery, lifecycle-wide |
| Workwize | Not published | n/a | Recovery with regional storage |
| Deel IT | Not published | n/a | Recovery inside an employment platform |
| Firstbase | Not published | n/a | Recovery across full home setups |
| GroWrk | Not published, per-order and subscription models named | n/a | Recovery in emerging markets |
| allwhere | Not published, consultation only | n/a | Recovery with deployment depth |
| ITAD vendors | Varies, usually per unit on a quote | n/a | Disposition, not recovery |
Checked against each vendor's own pricing page on 6 and 7 October 2026. A category where every participant withholds pricing is telling you something: cost depends heavily on geography and volume, and no vendor wants to publish a number that looks wrong for most enquiries.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Leavers hand devices to IT in person | Under 40 | Single office | Nothing is actually broken | A checklist with a named owner |
| Devices come back slowly but they come back | Any | Hybrid | Nobody chases, people comply | Fix the prompt and prepaid packaging |
| Cannot say what was issued to whom | Any | Any | An inventory gap, not a recovery gap | An asset register first |
| Laptops sitting in homes in several countries | 50 to 500 | Remote | Non-return across borders | A recovery platform |
| Latin America or Asia is where the gap is | Any | Remote | Coverage, not process | GroWrk or a regional specialist |
| Already running Deel for employment | Any | Remote | One more vendor to manage | Deel IT, inside the existing relationship |
| 300 end-of-life machines on a pallet | Any | Central | Disposal and certification | A certified ITAD vendor, not recovery |
| Auditor has asked for device locations | 100 plus | Any | Evidence, not logistics | Register plus documented destruction |
Most teams occupy two of these rows at once, and the common pairing is an inventory row with a recovery row. Fix the inventory one first, because the recovery purchase depends on it.
Triaging What Comes Back
A device arriving is not the end of the process, and the step after it is where most of the value is either captured or quietly lost. Laptops that come back and sit in a cupboard represent the same write-off as laptops that never came back, with the added cost of having paid to retrieve them.
Triage is a decision with three outcomes, and it should take minutes rather than weeks.
Reissue. The machine is under roughly four years old, the battery holds a working charge, the screen and keyboard are sound, and it meets the specification a new starter would be given. Wipe it, record it against the register as available, and put it somewhere a new starter can be shipped from. This is the outcome worth optimising for, because it avoids a purchase outright.
Hold. The device is serviceable but not currently needed, or it needs a repair that is worth doing. Set a review date when you shelve it. Stock without a review date is how a cupboard becomes an archaeology site.
Retire. Out of support, uneconomic to repair, or below the specification anybody would accept. Route it to a certified disposition vendor, get the destruction certificate, and record the write-off against the register so the number is documented rather than merely absent.
The judgement that matters is the first one, and the mistake is being too strict with it. A three-year-old machine that would be refused by an engineer is often perfectly good for a role that lives in a browser and a spreadsheet, and treating one hardware standard as universal sends usable laptops to recycling. Decide what your floor actually is per role, write it down, and let whoever receives returned devices apply it without escalating each one.
But do the triage near where the device landed. Shipping a recovered laptop to a head office to be assessed, then out again to its next user, routinely costs more than the machine is worth and is the single most common way reissue economics get destroyed.
What Getting This Wrong Costs
The obvious cost is the hardware, and it is the smallest one. A laptop that does not come back is worth a few hundred pounds as a write-off and rather more as a reissue, but a company losing fourteen machines a year is losing an amount that will not change anybody's mind on its own.
The second cost is the one that actually bites: you cannot prove a negative about data. A device you do not hold is a device you cannot demonstrate was wiped, and that distinction matters enormously the first time somebody asks. It does not matter whether the data was ever at risk. What matters is that the honest answer to "can you confirm that device was securely erased" is no, and that answer appears in a report. Companies discover this during due diligence or a security review, which are the two worst moments to discover it.
The third is organisational and it compounds quietly. Once a team has accepted that some laptops do not come back, the standard moves. The register stops being maintained because everybody knows it is wrong. New starters are issued devices against a list nobody trusts. Within two years the question is not how many devices are missing but whether the company has any reliable idea what it owns, and rebuilding that is far more expensive than maintaining it would have been.
So ask the diagnostic question plainly. Is this a knowledge problem, a logistics problem, or an ownership problem? A knowledge problem wants an accurate register and no vendor at all. A logistics problem wants a recovery platform. An ownership problem wants somebody's name against the step, and no amount of software substitutes for that.
When You're Ready to Move Beyond a Spreadsheet
The signals are specific rather than aspirational. You can state your recovery rate and your median days to return. The devices you cannot account for are in homes rather than cupboards. Somebody is named to own the chase, and that person will still be in the role in six months. And the register is accurate enough that a platform would have something real to work from.
When those four are true, a recovery platform pays back quickly, mostly through reissue rather than through the devices it retrieves. When any one of them is false, buying tooling adds a licence to an unsolved problem.
If the piece you are missing is the lifecycle itself, rather than the retrieval step alone, that is the case for a platform that handled the device from the start. RemoAsset sits in that position: it closes a loop it opened, which is why its recovery works best for teams that also procured through it and why it is a weaker choice for teams who did not. If that is where you are, it is worth a look alongside the alternatives here, and expect a demo rather than a price list from any of them.
And if your register is the real gap, fix that first. Every option on this page will perform against the list you give it, and none of them can retrieve a device you never recorded issuing.
Frequently Asked Questions
What is IT asset recovery?
IT asset recovery is the process of getting company-owned hardware back from somebody who has left the organisation, and then deciding what happens to it. In practice it covers four jobs: making contact with the former employee, physically moving the device from wherever it is to wherever you want it, destroying the data on it to a standard you can evidence, and triaging the machine for reissue or disposal. It is distinct from IT asset disposition, which handles hardware already in your possession at end of life, although the two words are used interchangeably by vendors and that conflation causes a lot of misdirected spending.
How is asset recovery different from ITAD?
Recovery gets a device from an individual, usually at a home address, usually after the working relationship has ended. Disposition processes hardware in bulk once it has arrived somewhere central, destroying data to a documented standard and routing machines to resale or recycling. The distinction matters because the two are built around completely different problems: recovery is a communication and logistics challenge involving one person who no longer works for you, while disposition is a throughput and compliance challenge involving pallets. A company with laptops stranded in four countries gains nothing from an ITAD contract, and a company with 300 end-of-life machines in a storeroom gains nothing from a recovery platform.
What is a normal recovery rate?
For a distributed team with no dedicated process, somewhere between 60 and 90 per cent is ordinary, and the figure degrades the longer the gap between the last working day and the first request. Teams with a defined process, prompt contact and prepaid packaging routinely run above 90 per cent. Rather than benchmarking against other companies, calculate your own from the last twelve months of leavers and track the median days to return alongside it, because the two numbers together tell you whether you have a compliance problem or a chasing problem, and those have different solutions.
How much does IT asset recovery cost?
No vendor in this category publishes a price, which was checked against each one's own pricing page on 6 and 7 October 2026. RemoAsset, Workwize, Deel IT, Firstbase, GroWrk and allwhere all route to a demo or a consultation. Two describe their model without attaching figures: GroWrk names a per-order a la carte option and a subscription tier, and allwhere refers to pay-as-you-go and fixed rates. Expect cost to vary substantially by country, because the economics of retrieving a laptop differ enormously between a major European city and a remote region, and build a sales conversation into your timeline because there is no way around it.
Can we just post a prepaid box and skip the platform?
For a handful of leavers a year in countries you understand, yes, and plenty of companies do exactly that successfully. It stops working for three reasons as you grow: customs paperwork for cross-border returns is genuinely difficult and a box that gets stuck at a border is effectively lost, you have no chain-of-custody documentation when somebody asks for it, and nobody owns the chasing so the non-responders simply accumulate. The honest test is whether your recovery rate is holding. If it is above 90 per cent with prepaid boxes, keep doing that.
What happens if the person refuses to return the laptop?
Far more often than outright refusal, what happens is silence, and the two need different responses. Silence is usually logistics or uncertainty, frequently a worry about personal data on the machine, and it responds well to a clear prompt, prepaid packaging and an explicit sentence about what happens to their files. Genuine refusal is a matter for whatever agreement the person signed and for your own legal advice, which will depend on your jurisdiction and the terms in place. What the software can do is document the attempts, which is what you will need if it escalates.
Should recovered laptops be reissued or recycled?
Reissued, wherever the machine has useful life left, because the economics are not close. A recovered laptop that goes to the next starter avoids a purchase, while one that is recycled returns a small fraction of its value. The constraint is usually geographic rather than technical: if the only way to reissue is to ship the device to a head office and out again, the shipping and the delay often exceed the benefit. This is why regional storage matters more than it first appears, and it is worth asking any vendor specifically where a recovered device would physically sit.
How does recovery connect to data destruction compliance?
Recovery is the step that makes destruction possible, and the two are usually assessed together. An auditor asking about a departed employee's device wants to know that it was recovered and that the data on it was destroyed to a documented standard, with a certificate rather than an assurance. The practical consequence is that a device you never recovered is a permanent gap in that record, because you cannot evidence the destruction of data on hardware you do not hold. If evidence is the driver for this work, make documented destruction a shortlisting requirement rather than something you ask about after choosing a vendor.
HROpsLab takes no vendor money and publishes no paid placements, which is why this page says "not published" seven times rather than estimating.