Three Hundred and Forty Laptops in Two Hundred Living Rooms

The old model worked like this: employees used company laptops at the office. When the lease ended or the refresh cycle hit, IT collected them. All of them. From desks. In one building. On one day. A pallet was assembled. A truck was called. The ITAD process began.

That model assumed employees were in the same place as their devices. As of 2026, that assumption is, to use a technical term, hilariously wrong.

The new model: 340 employees in 200 homes across 6 countries, each with a company laptop that needs to come back. Some employees are in cities. Some are in rural areas where the nearest parcel pickup point is a 40-minute drive. Some have moved since the device was deployed and HR doesn't have the current address. One employee is on extended leave and isn't responding to emails. Another resigned two months ago and nobody asked for the laptop back.

The ITAD process hasn't started yet. The ITAD process can't start. Because the ITAD process requires a device, and the device is in someone's living room in a suburb of Lyon, possibly under a couch cushion.

Retrieval Is the New Bottleneck

In a centralised model, retrieval is free — the devices are already in your building. In a distributed model, retrieval is the most expensive and unpredictable part of the entire lifecycle. You need to:

Identify who has what. Contact each person. Provide packaging materials and shipping labels. Coordinate pickup or drop-off. Track whether the device was actually shipped. Handle the ones that weren't — the lost, the forgotten, the "I thought I already sent it back," the "I need it for one more week."

Each of those steps has a failure rate. Some people don't open the email. Some open it and ignore it. Some intend to ship but forget. Some ship the wrong device. Some ship the right device but without the charger. Each failure adds cost, delays the process, and extends the window during which sensitive data sits in an uncontrolled environment.

Failed retrieval equals failed ITAD. A device that never enters the process is a device that never gets wiped, never gets graded, and never stops being a liability.

The Data Risk Nobody Talks About

While the device is in someone's living room, it's in an uncontrolled environment. The data on it hasn't been erased. The endpoint security may or may not be current. The person in possession of it may or may not still be an employee. And you, the ITAD provider, have no visibility into any of this.

Remote wiping helps — if it's configured, if the device is connected to the internet, if the MDM agent is still running, if the employee hasn't reformatted the drive to use it for personal projects (this happens more than anyone admits). Remote wiping is a mitigation, not a solution. The solution is physical retrieval and confirmed erasure.

What the Process Needs to Look Like

The retrieval workflow for distributed devices needs to be as structured as the processing workflow in your warehouse. That means:

Automated triggers when a lease ends or an employee offboards. Personalised communication to each device holder with clear instructions. Pre-paid shipping materials sent to their current address (which means having their current address). Real-time tracking of shipment status. Escalation workflows for non-response. Integration with HR systems for offboarding triggers.

Once the device arrives at your facility, the standard ITAD process takes over: receiving, testing, grading, erasure, disposition. But that handoff — from "in someone's living room" to "on your dock" — is where the 2026 ITAD challenge lives.

---

340 laptops. 200 living rooms. 6 countries. The device you need to process is sitting on a kitchen table in Bordeaux, and the person who has it is on holiday. Your SLA clock is ticking. Your compliance exposure is growing. The old model — pallets at the dock — was a logistical operation. The new model is a retrieval operation disguised as a logistics challenge. And retrieval requires a different kind of system entirely.