The best way to handle remote employee laptop retrieval at a mid-size company is to run it as a scheduled operation with one owner, not a favor you ask of someone who has already left. Trigger it on the notice date, ship a prepaid kit with a booked door pickup, lock the device through MDM, treat any remote wipe as a documented decision, and close every case with a serial-level chain-of-custody record and a sanitization certificate, whether you run it in-house or through a laptop retrieval service. At 100 to 1,000 employees, what decides your recovery rate is ownership, written SLAs, and a plan for countries where you have no entity.
From our own operations: over the last 12 months, GroWrk recovered 10,257 devices across 98 countries, with a 99% retrieval success rate and a median recovery time of 14 days. This guide is built on what that volume shows about where retrievals stall.
The five moves that matter most:
Who this is for: IT operations managers and IT directors at distributed companies of roughly 100 to 1,000 people. If you want the day-by-day procedure for a single departure, start with our 9-step remote employee laptop retrieval workflow. This guide covers the operating model around it: volume, ownership, SLAs, KPIs, countries and vendors.
Mid-size teams lose laptops because they have enterprise volume with startup staffing. A 40-person company can treat each departure as an exception. A 5,000-person company has a logistics function. A 400-person company spread across six countries has neither the slack nor the department.
Your baseline retrieval load is a simple formula:
Monthly retrievals ≈ (headcount × annual turnover rate ÷ 12) + monthly refreshes and role changes.
Illustrative numbers at a 15% annual turnover rate (replace it with your own):
| Headcount | Departures per year | Retrievals per month | What it feels like |
|---|---|---|---|
| 150 | 23 | ~2 | A side task someone forgets |
| 400 | 60 | ~5 | A weekly recurring job |
| 800 | 120 | ~10 | A queue that needs an owner and an SLA |
Add hardware refreshes, role changes and broken-device swaps and the real number of device movements is higher. Once you pass about five a month, retrieval stops being an offboarding checklist item and becomes an operation.
The buyer data backs this up. On inbound booking forms, written before any sales contact, roughly 30% of IT buyers named offboarding, retrieval or storage as the reason they reached out. And when buyers describe why they want to leave a current provider, they talk about execution, such as slow pickups, devices that arrive un-wiped and chasing for status, rather than missing features. One buyer evaluating vendors put the bar plainly: “if it takes too long, like a few days, it might be better for us to just move on.”
How someone leaves changes how you retrieve. Most guides write one process for everyone. A resignation gives you a notice window and goodwill; a termination gives you neither; a layoff gives you volume all at once.
| Resignation (employee quits) | Termination (involuntary) | Layoff or reduction in force | |
|---|---|---|---|
| Lead time | The notice period, often 1 to 4 weeks | Usually none | Days to weeks of private planning |
| When to reconcile assets | On the notice date | Before the termination meeting | During planning, for the whole list |
| When the kit ships | So it arrives before the last day | Same day as the meeting | Pre-staged; ships on announcement day |
| MDM lock | Day before the last day | At the start of the meeting | At announcement, in bulk |
| Privileged access | Removed at notice | Removed before the meeting | Removed before the announcement |
| Who sends the request | IT, with a friendly tone | HR, with the separation paperwork | One central message and one portal |
| Biggest risk | Drift: nobody chases after the farewell | Non-response and disputes | Pickup and intake capacity |
| Escalation path | Manager, then HR | HR and legal from day one | Central ops team with daily reporting |
For resignations, use the goodwill. Confirm the shipping address and a courier-reachable phone number while the person still answers messages. A box that arrives during their last week is a reminder; one that arrives after they have mentally left is a chore.
For terminations, do the work before the meeting. Reconcile assets, stage the kit and prepare the MDM lock in advance. Put the return instructions and the signed equipment agreement in the separation packet so the request comes with the paperwork, not as a separate email from IT.
For layoffs, plan for throughput. Bulk-upload the affected list, pre-book pickups in waves, and confirm your warehouse or vendor can receive and process the volume within your SLA. A layoff is where an ad-hoc process fails all at once, in public.
Not legal advice. Don’t plan on deducting a laptop’s value from final pay. Under US federal rules, deductions for employer property losses can’t cut into minimum wage or overtime (US Department of Labor, Fact Sheet #16); many states restrict them further, and most other countries limit them too. Have counsel confirm your options in each jurisdiction before you write them into an agreement.
A complete laptop recovery process has six phases, and each one ends with a piece of evidence, not a feeling that it is done. Day 0 is the employee’s last working day.
| Phase | When | Owner | Done when you have |
|---|---|---|---|
| 1. Trigger and reconcile | Notice date (Day -5 or earlier) | HR triggers, IT reconciles | An itemized list of serials checked against MDM, shipping and expense records |
| 2. Confirm and dispatch | Day -3 | HR confirms, IT or vendor ships | A confirmed address, phone number and outbound tracking number |
| 3. Secure | Day -1 to Day 0 | IT and Security | A confirmed MDM lock (not just a sent command) and a staged access-revocation log |
| 4. Collect | Day +1 to +7 (+14 cross-border) | Vendor | A carrier acceptance scan (not just a created label), the first entry in your chain of custody |
| 5. Intake and sanitize | On arrival | Warehouse or IT | A serial match against the assigned asset, condition photos, and a per-serial sanitization certificate |
| 6. Disposition | Within 30 days of arrival | IT Ops with Finance | A recorded decision: redeploy, store, buy back or dispose |
The step-by-step detail for each phase, including the employee message template and the minimum chain-of-custody fields, is in our 9-step retrieval workflow. If you are building the HR side, pair it with our guide to employee offboarding for remote laptop recovery.
Most stalled retrievals stall for one of three reasons: the former employee goes quiet, the shipment is missing a detail the courier or customs needs, or the device arrives locked. Between June 25 and October 8, 2026, GroWrk’s logistics team raised 1,423 exception tickets to clients through a structured request form. These were the named causes.
| Exception type | Tickets | Share |
|---|---|---|
| Former employee unresponsive | 264 | 18.6% |
| Missing details (tax ID such as Brazil’s CPF, phone, address, postal code) | 203 | 14.3% |
| Device locked | 197 | 13.8% |
| Buyback or recycling eligibility and pricing | 132 | 9.3% |
| Item discrepancy (wrong, extra or missing device) | 76 | 5.3% |
| Windows Autopilot hardware hash needed | 51 | 3.6% |
| Shipping or delivery change | 31 | 2.2% |
| Repair approval | 26 | 1.8% |
| Legal hold or wipe authorization | 19 | 1.3% |
| Other | 424 | 29.8% |
Source: GroWrk logistics exception tickets, June 25 to October 8, 2026 (n=1,423, de-duplicated by order and type). Tickets span all order types the team handles, not only retrievals.
Of the 197 locked-device tickets, 47% asked for a device PIN or password, 13% involved MDM or Apple Business Manager enrollment, 12% Apple Activation Lock, 10% a BitLocker recovery key and 5% a firmware password. A device locked at intake waits until someone finds the credential. In some Activation Lock cases, Apple asks for the original purchase invoice before it will release the device.
| Blocker | What to do while the employee is still responsive |
|---|---|
| Former employee goes quiet | Collect a personal email and phone at notice. Ship the kit before the last day. Have the manager or HR send the request, not only IT |
| Missing courier or customs details | Capture tax ID where required, a local phone number and the exact postal code on the notice date |
| Device locked | Escrow BitLocker keys and firmware passwords in MDM. Enroll Macs through Apple Business Manager so Activation Lock can be bypassed. Ask the employee to sign out of their Apple ID before packing. Keep purchase invoices |
| Wrong or missing item | Send an itemized list with serials. Open a discrepancy instead of marking the laptop returned |
| Device already sitting in an office | Record its location and collect it. Cancelling the retrieval order closes a ticket, not the asset |
One safety note: ask employees to report swollen or damaged batteries before packing. A damaged lithium battery needs specialist handling and must not go into an ordinary return shipment (FedEx battery-shipping guidance).
IT operations should be accountable for the physical device; HR should be responsible for triggering the process and confirming the address. Split accountability without one named owner is the most common structural reason laptops go unrecovered.
R = responsible, A = accountable, C = consulted, I = informed.
| Activity | HR / People Ops | IT Ops | Security | Finance | Manager | Vendor |
|---|---|---|---|---|---|---|
| Trigger retrieval on notice date | R | A | I | I | I | – |
| Reconcile assigned assets | C | A/R | C | C | C | – |
| Confirm address and phone | R | A | – | – | C | I |
| Ship kit and book pickup | I | A | – | – | – | R |
| MDM lock and access revocation | I | A/R | R | – | – | – |
| Chase non-responders | R | A | – | – | C | R |
| Intake, log and sanitize | – | A | C | – | – | R |
| Disposition decision | – | A/R | C | C | – | C |
| Unrecovered-device escalation | R | A | C | C | I | – |
These are reasonable starting points, not an industry standard. Agree them with your vendor and put them in the contract.
| KPI | How to calculate it | Why it matters |
|---|---|---|
| Verified recovery rate | Devices received and serial-matched within 30 days ÷ devices expected from that month’s departures | Your headline number; report it by country |
| On-time handoff rate | Returns accepted by the carrier by their deadline ÷ returns due | Separates employee delay from carrier delay |
| Days to verified recovery | Median days from Day 0 to serial-verified intake | Shows where the process stalls |
| Cost per verified recovery | All retrieval costs, including failed attempts ÷ devices verified as recovered | Exposes the IT time nobody budgets |
| Certificate coverage | Devices with accepted sanitization evidence ÷ devices sanitized | Your audit answer |
| Devices in limbo | Devices received with no disposition after 30 days, plus open exceptions by cause and age | Residual value draining away |
Count cost per verified recovery, not per label. Say one month’s retrievals cost $1,000 in packaging and transport, $1,200 in internal handling time and $300 in intake and sanitization. If 20 laptops from that month are serial-verified by the reporting cutoff, the cost is $2,500 ÷ 20 = $125 per verified recovery. These figures show the calculation; they are not market prices.
There is no reliable public benchmark for recovery rates, and any number quoted without its denominator should be treated with caution. For reference, GroWrk’s own figures for the last 12 months are a 99% retrieval success rate and a 14-day median recovery time across 10,257 devices. Report approved write-offs and employee-kept devices separately from physical recoveries, and segment by country: the country with the worst days-to-recover is usually where you need a local partner.
Outside your home country, a returning laptop is a customs event, not a parcel. The rule that works: retrieve into in-country storage wherever you have staff and no entity, and redeploy locally, so the device never crosses a border twice.
These are the countries IT buyers bring up most in GroWrk’s call corpus, sorted by distinct accounts, and what changes for retrieval in each.
| Country | Calls naming it (of 3,977) | Distinct accounts | What changes for retrieval |
|---|---|---|---|
| India | 665 | 386 | Moving goods above a value threshold needs an e-way bill and GST paperwork; a prepaid label alone will not clear |
| Canada | 513 | 345 | A return to a US warehouse is an import into the US; in-country storage avoids it |
| Brazil | 430 | 275 | Import taxation and documentation make re-entry slow and costly; receive locally |
| Mexico | 417 | 254 | Needs locally compliant paperwork and, in practice, a local receiver |
| Argentina | 341 | 245 | Import paperwork and duty exposure on re-entry; avoid sending devices out and back |
| Philippines | 386 | 226 | Few local resellers; often “no one to collect” without a partner |
| Colombia | 323 | 203 | Local documentation and a local receiving party |
Source: GroWrk Call Intelligence (n=3,977), April 2024 to August 2026.
India is the most-discussed deployment market in the data by a clear margin, and its paperwork is a recurring question. One buyer asked: “how are you going to navigate around the India e-way bills?” Another described the reseller gap in Southeast Asia and Central America: “there’s no VARs out there that could just ship the devices. And there’s also no one to collect.”
Capture the details customs will need while the employee is still responsive: national ID or tax ID where export paperwork requires it, a local phone number, and the exact device value from your asset register. Chasing those after the employee has gone quiet is what turns a two-week retrieval into a two-month one.
How a laptop leaves an employee’s home depends on the market. Across GroWrk’s network, collections run on four models:
| Collection model | How it works | Example markets |
|---|---|---|
| Kit plus scheduled courier pickup | A box and label are shipped; a courier collects from the door | US, Canada, Mexico, Argentina, Chile, Australia, India |
| Kit plus pickup or drop-off | The employee chooses a home pickup or a courier-store drop-off | Ireland, Netherlands, Poland, Spain, Greece |
| Courier packs on-site | The courier arrives with the box and packs the device at the door | Philippines, Japan, Israel, Nigeria |
| Local pickup representative | No national courier; a local rep schedules the visit and brings a box if needed | Brazil, UAE, Saudi Arabia, Egypt, Kenya, Pakistan |
A single “print this label” instruction doesn’t fit the last two models at all. Ask any vendor which model applies in each of your countries, and what the employee has to do in each.
A laptop is recovered when you can prove it from a record: who held it, when custody changed, what state it arrived in, and how its data was destroyed. “We got it back” is not an audit answer. Certified wipe, SOC 2 and destruction came up unprompted in 12.1% of 3,977 calls, so expect the question from auditors and customers alike.
Each retrieved device needs, at minimum:
Link the carrier tracking number to the serial number, and verify the contents at receipt. Carrier tracking proves shipment events, not person-to-person custody, so don’t describe it as continuous custody. For high-assurance returns, add numbered seals, package photos or signed handoffs before shipment, and record any gap in the history rather than papering over it.
NIST published SP 800-88 Rev. 2, Guidelines for Media Sanitization in September 2025. It supersedes Rev. 1 from December 2014, which many vendor certificates and internal policies still cite.
Three practical changes for IT operations:
What to do: update policy language that cites Rev. 1, and ask your retrieval or ITAD vendor which standard their tooling follows and how they validate it. Require a certificate per serial number, not a batch statement covering dozens of devices in one paragraph. For disposal, use partners certified to R2v3 or e-Stewards, and NAID AAA for data destruction, and record the certificate number.
There is no universal rule. Lock the device and revoke access on schedule, then treat a remote wipe as a documented decision rather than a reflex.
| Situation | Decision path |
|---|---|
| Routine departure, cooperative return | Lock, revoke access, and sanitize at intake where you can certify it against the serial |
| Suspected theft, compromise or unauthorized access | Escalate to security immediately; a remote wipe may be the right containment |
| Legal hold or investigation | Get preservation direction before any destructive action |
| Offline or unmanaged device | Record the limitation and assess the remaining exposure |
| Remote action sent but not confirmed | Keep the outcome unverified until the device reports back |
Locking, retiring, deleting a management record and wiping are different actions, and their effects vary by platform. Microsoft notes that a wipe sent to an offline Intune device can stay pending, and that retiring a device does not by itself revoke access tokens (Microsoft device-action troubleshooting). Check identity controls, device controls and physical recovery separately. On Macs, a premature wipe can also leave you with an Activation Lock you can’t clear, one of the lock types in the exception data above.
Getting the laptop back is where most guides stop, but it is where the cost decision starts. The three most-discussed topics in our call data are all about this middle of the lifecycle: storage (22.8% of calls), retrieval (22.6%) and MDM enrollment before shipping (22.0%).
| Disposition | Choose it when | Watch out for |
|---|---|---|
| Redeploy | A hire in the same country starts within weeks | Re-enroll in MDM at the warehouse, not at the new hire’s kitchen table |
| Store in-country | Hiring is lumpy but expected in that country | Set a review date; residual value drops every month it sits |
| Buy back or resell | No redeployment within your window | Compare buyback quotes; 10.7% of buyers raised resale value unprompted |
| Dispose | End of life, failed hardware, or data too sensitive for reuse | Use certified ITAD and keep per-serial certificates |
Set a default: any device without a redeployment plan 30 to 60 days after arrival goes to buyback. One IT lead described their incumbent’s offer bluntly: “the buyback option they’re giving me is terrible.” Model it before you sign.
A note on leasing: GroWrk offers leasing in the United States only. Outside the US, buyback is the equivalent lever.
In-house retrieval works for a single country and low turnover; once you have staff in several countries or more than a few departures a month, a lifecycle platform is usually cheaper than the IT hours it replaces. Here is how the four common models compare.
| In-house | Reseller (VAR) + ad hoc shipping | Return-shipping software | IT lifecycle platform | |
|---|---|---|---|---|
| Best fit | One country, under ~100 staff | One or two mature markets | Domestic teams that want label automation | Multi-country, retrievals every month |
| Door pickup | You arrange it | Sometimes | Label or QR drop-off, sometimes pickup | Standard |
| Cross-border | Very hard | Fails where no VAR exists | Usually limited | Core capability |
| Chain of custody | Whatever you build | Shipping tracking only | Shipment-level | Per serial, auditable |
| Storage between hires | An office closet | Rarely | No | In-country warehousing |
| Sanitization and certificates | Your tools, your proof | Separate ITAD vendor | Separate ITAD vendor | Included, per serial |
| Main risk | Doesn’t scale past one country | Country gaps found mid-offboarding | Gaps after the box arrives | Paying for seats that hold no device |
Price is the most common objection IT buyers raise when evaluating lifecycle vendors, appearing in roughly half of the new-business calls we hand-coded. But the complaint is rarely the number. It is the structure: per-employee licences charged for people who hold no device, or annual regional commitments. One buyer at an infrastructure services company drew the contrast between a six-figure regional commitment and simply adding a small per-user monthly fee. Pricing model transparency came up, unprompted, in 6.7% of all 3,977 calls.
For a sense of scale, one vendor’s published guide puts standard US laptop return services at $80 to $200 per device. That covers the movement, not your team’s time, storage or depreciation.
A mid-size IT team can move from ad hoc returns to a measured retrieval operation in about a month, one focus per week.
Start with last year’s departures by country and the devices still unrecovered; that list sets your priorities. By week four you should be reporting the six KPIs above and clearing any device that has sat without a disposition for more than 30 days.
The fastest way to find your weak step is to audit the last ten departures. For each one, check for a named retrieval owner, an accurate itemized asset list, a carrier acceptance scan, a serial-verified receipt, and a documented final outcome.
Then fix the most frequent failure first. If kits sit unused, change the return method for that country. If delivered laptops sit unprocessed, fix intake. If devices arrive locked, fix credential escrow before the next departure. If returned devices can’t be reassigned, fix sanitization and re-enrollment.
GroWrk runs the middle of the IT lifecycle, the part between one employee and the next. That means laptop retrieval in 150+ countries, with 10,257 devices recovered across 98 of them in the last 12 months, in-country warehousing so devices don’t cross borders to be redeployed, MDM enrollment before a device ships to its next owner, per-serial chain of custody and sanitization certificates, and buyback when redeployment doesn’t make sense. Retrievals trigger from your HRIS through our integrations, and pricing is per device under management, not per employee seat. Book a demo below to map your current retrieval volume by country.
Methodology: This guide draws on three GroWrk datasets. Operating data: devices recovered, retrieval success rate and median recovery time cover the 12 months to October 2026. Logistics exception tickets: 1,423 tickets raised to clients through a structured request form between June 25 and October 8, 2026, de-duplicated by order and request type; lock causes were classified from ticket descriptions. Call intelligence: 3,977 customer calls recorded April 2024 to August 2026, counting themes only where the customer raised them before a GroWrk representative did, each pattern precision-tested by hand-reading a random sample; the price-objection finding comes from 41 randomly drawn new-business calls coded by hand. Booking-form figures are directional, from 100 hand-classified inbound forms. Customer quotes are used with identities withheld. Nothing here is legal or tax advice; employment and customs rules vary by jurisdiction.
Run retrieval as an owned operation that starts on the notice date. Reconcile the assigned devices, confirm the address in writing, ship a prepaid kit that arrives before the last day, and book a door pickup so the employee has nothing to arrange. Lock the device through MDM and treat any remote wipe as a documented decision, keep one contact channel open until the carrier acceptance scan, then serial-verify, sanitize and decide the device’s next use on arrival. For staff abroad, retrieve to in-country storage rather than across a border.
Multiply headcount by your annual turnover rate and divide by 12, then add refreshes and role changes. At 400 employees and 15% turnover, that is about five retrievals a month before refreshes. Above roughly five a month, you need a named owner and written SLAs.
A resignation gives you a notice window, so you can reconcile, ship the kit and confirm the address while the person is still cooperative. A termination usually gives you no window, so reconciliation, kit staging and the MDM lock must be prepared before the meeting, and the return instructions should arrive with the separation paperwork from HR.
IT operations should be accountable for the device, and HR responsible for triggering retrieval on the notice date and confirming the address. One named owner matters more than which team it sits in.
There is no reliable public benchmark. Measure the share of devices received and serial-matched within 30 days of departure, report it by country, and track the trend. As one reference point, GroWrk’s retrieval success rate over the last 12 months was 99% across 10,257 devices, with a 14-day median recovery time.
Published US price ranges for the return service alone run from about $80 to $200 per device. The number to track is cost per verified recovery: packaging, transport, customs, storage, provider fees and internal IT time, including failed attempts, divided by the devices actually serial-verified as recovered.
Not by default. For a routine departure, lock the device and revoke access, then sanitize at intake where you can certify it against the serial number. Escalate to a remote wipe when there is suspected theft or compromise, and get preservation direction first if a legal hold applies. Record whether the command was confirmed, because an offline laptop only receives it when it next checks in.
Treat it as a customs event. Collect the documents that country requires, such as India’s e-way bill and GST paperwork, and use a partner with a local receiving entity. In most cases, retrieving to in-country storage and redeploying locally is cheaper and faster than shipping the device home.
NIST SP 800-88 Rev. 2, published in September 2025, superseded Rev. 1 from 2014. Update policies that cite Rev. 1, and ask vendors which technique standard, such as IEEE 2883, their tools follow.
In-house works for one country and low turnover. With staff in several countries or several retrievals a month, a lifecycle platform with door pickup, in-country storage and per-serial certificates usually costs less than the IT time it replaces. Compare vendors on price per device under management, not per employee seat.
Choose one of four outcomes within 30 days: redeploy after re-enrolling in MDM, store in-country with a review date, sell through buyback, or dispose through a certified ITAD partner with per-serial certificates.
Mostly people and credentials. In 1,423 exception tickets GroWrk’s logistics team raised between June and October 2026, the top named causes were unresponsive former employees (18.6%), missing details such as a tax ID, phone or postal code (14.3%), and locked devices (13.8%). All three are cheapest to fix before the employee’s last day.
No. Delivery should trigger intake. Close the case only after the receiving team matches the serial number to the assigned asset, records condition and accessories, and logs any discrepancy.
No. Disabling accounts cuts access to company services, but it says nothing about data stored on the device, its encryption, or whether a remote command reached it. Check identity controls, device controls and physical recovery separately.