When a laptop comes back from a departing employee, most IT teams put it in a cupboard.
Sometimes it gets reissued eventually. Sometimes it sits there until the battery fails and someone decides to write it off. Sometimes it gets stolen from the cupboard. Sometimes nobody is sure what happened to it.
This is the redeployment gap: the distance between the potential cost saving of reusing a retrieved device and what actually happens to most of them.
For companies with regular hiring and offboarding activity across multiple countries, this gap is measured in tens of thousands of euros per year.
The basic maths
A company laptop has an average replacement cost of 1,200 to 1,800 euros. A laptop that is 2 years old, in good condition, with a working battery and no screen damage, has an effective remaining useful life of 2 to 3 years. Its value as a redeployable asset is roughly 600 to 1,200 euros - the cost of a new device it replaces.
The cost of retrieving and redeploying that device: logistics for return (60 to 150 euros with a managed service), professional data wiping (covered in the service cost), functional check, and redeployment logistics to the next user (60 to 150 euros). Total: 120 to 300 euros.
Net saving per successfully redeployed device: 300 to 900 euros.
For a company offboarding 30 employees per year with a 70% retrieval and redeployment rate - which is achievable with a working process - that is 21 devices redeployed per year at an average saving of 600 euros each: 12,600 euros in avoided procurement spend per year.
Against a background cost of device management that most teams underestimate, this is a meaningful number. For the full cost picture on in-house device management, see our guide on the hidden cost of managing IT devices in-house.
Why most teams do not do this
The redeployment gap is not a knowledge problem. Most IT managers understand that reusing devices saves money. The gap is operational: the process for assessing, storing, and redeploying retrieved devices does not exist in a reliable form.
The specific failures:
No assessment process. When a device arrives back from a leaver, nobody has defined what should happen next. It goes in the cupboard because that is the default.
No storage system. Devices in the cupboard are not tracked. Nobody knows which ones are in good condition and which are not. The cupboard becomes a black hole.
No redeployment trigger. When a new hire joins, IT orders a new device because the cupboard situation is unclear. The redeployable devices sit unused while new devices are procured.
No data wiping at intake. Devices that arrive back from leavers and are not immediately wiped sit with the previous user's data on them. This is both a GDPR issue and a practical problem - you cannot redeploy a device that has not been securely wiped.
No condition tracking. A device that was fine when it came back six months ago may have a failing battery now. Without tracking, you find out at the worst moment: when you have promised a new hire their device and the redeployed laptop fails on day one.
Building a redeployment process
A working device redeployment process has four stages: intake, assessment, storage, and redeployment.
Intake
When a device arrives back from a leaver, the intake process should happen within 48 hours of receipt. This is not optional - a device sitting around uninspected is a device that could develop a problem before you spot it.
Intake checks: confirm the device is physically present and not damaged in transit. Log the device in the asset management system as "returned - pending assessment." Initiate secure data wiping immediately. Do not wait until the assessment is complete - wipe the device first.
Assessment
After wiping, assess the device against a standard checklist:
Battery health. Most operating systems have a battery health tool that shows the current capacity as a percentage of original. Above 80% is typically fine for redeployment. Below 60%, the device will need a battery replacement before redeployment or should be assessed for end-of-life.
Screen condition. Check for dead pixels, screen damage, or backlight issues. Minor cosmetic damage is acceptable. Significant screen damage reduces the device's usability and should be noted.
Keyboard and trackpad function. Every key. The trackpad physical click and gesture recognition. These are common wear points.
Port function. USB, USB-C, headphone jack, power connector. Check each.
Performance. Boot time and basic application launch give a rough indicator of system health. A significantly degraded boot time may indicate storage issues.
MDM enrollment. Confirm the device can be enrolled in MDM before listing it as redeployment-ready. A device that cannot be enrolled cannot be managed securely.
Document the assessment outcome against the device serial number. Outcome: ready for redeployment, requires repair (specify), end of life.
Storage
Devices assessed as redeployment-ready should be stored in a location that is:
Known. The location of every device in storage should be logged in the asset management system. Not "in the IT cupboard" - in the asset system, with location, condition, and available-since date.
Secure. Devices in storage are company assets. Unlocked storage in a shared office area is not appropriate. A locked room or cabinet with controlled access is.
Environmentally appropriate. Laptops stored for extended periods should be kept at room temperature, away from direct sunlight, with batteries maintained at 50 to 80% charge if they will be stored for more than a few weeks.
Tracked. The asset management system should be queryable: how many devices are available for redeployment, what condition are they in, how long have they been in storage. If you cannot answer these questions in under two minutes, the storage process needs work.
Redeployment
When a new hire joins, the first check should be: do we have a suitable device in storage that can be redeployed?
For this to work in practice, the check needs to happen at offer acceptance, not at the point where IT is setting up the device. The lead time for preparing a storage device for redeployment is shorter than for procuring a new device - but it is not zero.
A redeployment-ready device still needs: MDM enrollment (or re-enrollment if it was cleared), software installation to the new hire's role requirements, and delivery logistics to wherever the new hire is located.
For a domestic redeployment, this is a 1 to 2 day process. For an international redeployment - sending a retrieved device from your office in Amsterdam to a new hire in Warsaw - it requires customs documentation for intra-EU movement (minimal but not zero), carrier booking, packaging, and insurance.
A device operations partner simplifies this: you specify the device and the destination, they handle the logistics, customs, and insurance. The cost is typically 60 to 150 euros - significantly less than the cost of procuring a new device.
The end-of-life decision
Not every retrieved device is redeployable. Some are too old, too damaged, or too degraded to be worth redeploying. These need a different process.
Devices with residual market value can be resold. There is an active market for 3 to 4 year old business laptops in good condition. A certified IT asset disposition partner can handle assessment, data certification, and resale. Recovering even 10 to 20% of original value from a batch of retired devices is better than writing them off.
Devices that are beyond resale value should be recycled through a certified e-waste recycler. For European companies with ESG reporting obligations, documented responsible disposal is increasingly part of the compliance requirement. The Corporate Sustainability Reporting Directive (CSRD) applies to companies with 250 or more employees in the EU from 2026, and IT equipment disposal falls within its environmental reporting scope.
For the full picture on what to do with devices that are not suitable for redeployment, see our guide to what to do with old company laptops.
The case for making redeployment a default
The companies that execute redeployment well treat it as the default, not the exception. When a new hire joins, the first question is not "what device do we need to order" but "do we have a device available for this person."
This mindset shift requires reliable retrieval (you cannot redeploy devices you do not have), a reliable assessment process (you cannot redeploy devices you have not checked), and reliable storage tracking (you cannot redeploy devices you cannot find).
All three require a working offboarding process - specifically, a retrieval rate that is high enough to make redeployment a realistic option rather than an occasional bonus.
For the full offboarding process design, including the retrieval steps that make redeployment possible, see our guide on how to build an IT offboarding process that actually works.
The redeployment maths at scale
To close with a concrete number: a company with 200 employees, in a sector with 20% annual turnover, is offboarding 40 people per year. At a 70% retrieval rate with a working process, that is 28 devices returned per year.
If 20 of those devices are in good enough condition to redeploy, and the average saving per redeployment is 600 euros (cost of redeployment vs cost of new device), the total annual saving is 12,000 euros.
Against the cost of implementing a managed device operations service that makes retrieval and redeployment reliable - for a team of this size, roughly 3,000 to 5,000 euros per year - the return on investment is clear.
The devices are already being paid for once. Redeployment is how you get a second payment's worth of value from each one.
FAQ
How old is too old for a device to be redeployed? It depends on the role and the device's condition, not just its age. A 4-year-old laptop with a healthy battery, a functional screen, and adequate processing power for the role is redeployable. A 3-year-old laptop with a failing battery, physical damage, or performance issues may not be. Assess on condition, not on age alone.
What is the correct data wiping standard before redeployment? NIST 800-88, which specifies overwriting standards that make data unrecoverable. For solid-state drives, cryptographic erasure - destroying the encryption key - achieves the same result. A factory reset is not sufficient under GDPR. Every redeployed device should have a certificate of data destruction documenting the wipe.
What do we do with devices that fail the assessment for redeployment? Devices with repairable issues (battery replacement, keyboard replacement) may be worth repairing if the device is relatively new and in otherwise good condition. Devices beyond economic repair should be assessed for resale value, then recycled through a certified e-waste partner if resale is not viable. Document the disposal for ESG reporting purposes.
How do we track which devices are available for redeployment? In the asset management system, with a status field that distinguishes: assigned, returned pending assessment, assessed and available, in repair, retired. Every device in storage should have a location, condition, and available-from date recorded. If you cannot query "how many laptops are available for redeployment right now" in under two minutes, the tracking is not working.
Does redeployment work across borders - sending a retrieved device to a hire in a different country? Yes, with logistics support. Intra-EU redeployment requires standard commercial documentation but no import duties. EU to UK redeployment requires customs clearance in both directions. A device operations partner handles the customs layer, making cross-border redeployment as simple as domestic redeployment from an IT perspective.
