Employee offboarding for a remote worker is only finished when the laptop is back, matched to the asset record, and sanitized with a certificate to prove it. This is the runnable version of that process: a day-by-day workflow with a named owner for every step, the emails to send, the intake checklist to run at receipt, and the escalation thresholds that tell you when to stop waiting. It is built on GroWrk's own retrieval operation - 14,708 device retrievals across 4 years - and on what those retrievals show about where offboarding actually stalls. GroWrk runs this workflow as a managed equipment retrieval service; for the reasoning behind each step, see our complete guide to remote laptop recovery.
Most advice on this topic treats laptop recovery as a shipping problem. Our operating data says it is a waiting problem - and that the person being waited on is usually the departing employee, not the carrier.
GroWrk has initiated 14,708 device retrievals since September 2022, roughly 4,500 of them in the last twelve months, at a current run rate of about 375 per month. Of retrievals that have reached a resolved state, 13,101 completed and 1,087 were cancelled - a 92% completion rate. (Cancellations include customer-initiated changes and duplicate records, not only failed recoveries.)
The more useful number is what the open queue looks like right now. Here is every in-flight retrieval on 26 August 2026, by state:
| State of open retrieval | Orders | Share |
|---|---|---|
| Waiting on the employee | 123 | 23.7% |
| Waiting on the client (the IT team) | 49 | 9.4% |
| On hold | 37 | 7.1% |
| Delayed | 22 | 4.2% |
| Actively moving (placed, in progress, shipped, delivered) | 287 | 55.2% |
| Total blocked or waiting | 231 | 44.4% |
Two findings fall out of that table, and both should change how you design your offboarding workflow.
1. Nearly half of all open retrievals are waiting on somebody. Not in transit. Not being processed. Waiting. Any process that only measures "did the label get created" is blind to 44% of its own pipeline.
2. The employee is the bottleneck by 2.5 to 1. There are 123 retrievals waiting on the departing employee against 49 waiting on the IT team. The label exists. The box has often already arrived. The device simply has not been handed over. That is why the most important custody transition in the whole workflow is not delivery - it is the first carrier scan, the moment the device stops being with the employee.
Our buyer research points the same way. Across 3,977 recorded conversations with IT teams, offboarding and retrieval was raised by the buyer unprompted in 795 calls (22.6%), and speed or lead time in 629 (17.9%). Retrieval is not a niche complaint. It is one of the three most-discussed topics in the category - and the delay buyers feel is mostly the delay above.
In a 200-order sample of recent retrievals, devices were collected from 34 countries. The highest-volume markets were the United States, the United Kingdom, Mexico, the Philippines, India, Brazil and Colombia - which is worth noting, because a workflow designed only around US domestic parcel shipping will break on the majority of that list.
Print this table. Every row has one owner and one exit condition. A step with two owners has none.
| When | Step | Owner | Done when |
|---|---|---|---|
| Day 0 (notice) | Separation event opens a recovery case | HR → automated | Case ID exists with a frozen serialized asset list |
| Day 0 | Confirm personal email, phone, current address | HR | All three verified, not copied from a stale record |
| Day 0 | Schedule access revocation; announce backup window | IT / Security | Revocation scheduled, employee notified of the cut-off |
| Day 0 | Send the return instructions (Template A) | IT Ops | Delivered to personal address, receipt acknowledged |
| Day 0–1 | Dispatch the return kit | IT Ops / partner | Kit tracking number attached to the case |
| Day 1–3 | Confirm kit delivered; employee confirms return method | IT Ops | Kit shows delivered and method is on record |
| Kit dispatch | Issue MDM remote lock | IT / Security | Lock confirmed in the MDM console |
| Day 1–3 | Backup window closes; revoke all access | IT / Security | Revocation timestamp recorded |
| Day 3 / 5 / 7 | Escalation ladder (thresholds below) | IT Ops → HR | First carrier scan received, or case flagged |
| In transit | Issue remote wipe command | IT / Security | Wipe command logged (queued counts; verify later) |
| At delivery | Intake: match serial, inspect, photograph | Receiving | Serial matched to assignment record |
| Post-intake | Security hold until review completes | IT / Security | Encryption and wipe verified; hold released |
| Post-hold | Sanitize, release from MDM tenant, assign disposition | IT Ops | Certificate issued; disposition recorded; case closed |
Target: device in carrier custody by day 7 domestic, day 14 international. Case closed within 5 business days of delivery.
The separation event should create the recovery case automatically. In our call corpus, HRIS integration came up buyer-led in 418 of 3,977 conversations (11.9%) and ITAM or ticketing integration in 224 (6.4%). Teams are not asking for another dashboard. They are asking for the trigger to stop depending on someone's memory.
The case opens with a frozen serialized asset list pulled from your IT asset management record. Never ask the employee what they have. If your records cannot answer that, you have an inventory problem that will resurface as a serial mismatch at intake.
Personal email, phone and current physical address — each re-confirmed, not inherited. Given that 123 open retrievals are currently waiting on employees, the cheapest possible intervention is making sure your instructions and your box are going to an address the person actually lives at.
Cut every system at 9am on notice day and you remove the person's ability to retrieve personal files, read your return instructions, or care about your logistics problem — while their laptop is still in their house. Announce a backup window of 24 to 72 hours, then revoke on schedule. Record the timestamp on the case as the second entry in the chain of custody.
The kit ships while the person is still employed and still responsive. Not after the last day.
| Rule | Why |
|---|---|
| Maintain a short approved-carrier list | Standardization is what makes exceptions visible |
| Tracked service with signature confirmation, always | An untracked drop-off leaves no custody record |
| Insure for replacement value, not shipping cost | Default carrier coverage is a fraction of the device's worth |
| Offer both scheduled pickup and drop-off | Each wins a different population; offering one costs you the other |
| Pre-fill customs documentation on international returns | An employee cannot classify a commercial export |
| Attach the label number to the case before pickup | Ties the shipment to the asset record from the first scan |
A tracking number tells you where a parcel is once a carrier has it. It tells you nothing during the phase where 44% of our open retrievals actually sit. Run the case against states instead, and escalate on time without progress rather than waiting for a deadline to pass.
| Trigger | Action | Owner |
|---|---|---|
| No acknowledgement by day 3 | Automated reminder, email + SMS to personal address | Automated |
| No first carrier scan by day 5 | Verify address and kit delivery before assuming refusal | IT Ops |
| No first carrier scan by day 7 | Manager or HR contact, once, with tracking number and restated deadline | HR |
| No movement by day 10 | Issue MDM remote lock if not already locked | IT / Security |
| No movement by day 14 | Formal written demand stating fair market value and a final date | HR / Legal |
| No movement by day 30 | Civil recovery where value justifies it; legal referral if the device held regulated data | Legal |
| Recovery abandoned | Documented write-off with completed access-destruction record | IT Ops / Finance |
| Transit exception, any day | Carrier trace opened; case flagged, not left in transit state | IT Ops |
Never on this ladder: withholding wages, threatening to withhold wages, or conditioning a reference on the return. Federal law limits deductions that push a non-exempt employee below minimum wage, improper deductions from an exempt salary can jeopardize the exemption, and states including California and New York sharply restrict deductions for employer property. Route enforcement through a written demand and civil recovery, never through payroll. General information, not legal advice - have counsel review your escalation language for every jurisdiction where you employ people.
Carrier delivery is not recovery. Delivery means a box arrived. Recovery means the right device arrived, in known condition, and the record says so.
Do not route a device to redeployment or resale the day it arrives. Hold it until encryption status and the wipe are verified, not merely commanded. A wipe issued in transit may have queued against an offline machine and never executed — the command log proves you asked, not that it happened.
Certified wipe, SOC 2 and destruction requirements came up buyer-led in 425 of 3,977 conversations (12.1%), concentrated in regulated industries and in any deal carrying a security review. Sanitize to NIST SP 800-88 Rev. 2, published 26 September 2025 and superseding Rev. 1. A factory reset is not a sanitization standard.
Release the device from Apple Business Manager, Intune and your MDM tenant as part of processing. An activation-locked laptop has close to zero redeployment or resale value, and this is the most common reason a recovered device becomes dead inventory.
Then assign one of four dispositions at intake, before it goes on a shelf: redeploy, repair, resell or buyback, or retire through a certified processor. Retrieval without a disposition plan just relocates the problem — which is why storage between hires is the single most buyer-led topic in our call corpus at 800 conversations (22.8%), narrowly ahead of retrieval itself. Buyback and resale came up in another 375 (10.7%), often with real frustration about what incumbents offer.
Subject: Returning your [Company] equipment — kit arriving [date]
Hi [Name],
We're arranging the return of the equipment assigned to you. You don't need to buy anything or arrange shipping — a prepaid return kit is on its way to [address], arriving around [date].
What needs to come back:
• [Device], serial [XXXX]
• [Charger]
• [Dock, asset XXXX]
• [Security key, asset XXXX]
[Item] is yours to keep — no need to return it.When: within 7 calendar days of your last day, [date].
How: pack the items in the box provided, photograph them before sealing, apply the enclosed prepaid label, and either book the free pickup at [link] or drop the parcel at any [carrier] location.
Before [backup deadline]: please save any personal files. Your access to company systems ends at that time, and the device is remotely locked and erased as part of offboarding.
Questions, or something missing from the list? Reply to me directly — [name], [email], [phone].
Subject: Following up — [Company] equipment return
Hi [Name],
Our records show the return kit was delivered to [address] on [date], but the parcel hasn't been scanned by the carrier yet. Tracking number [XXXX].
If the kit didn't arrive, or that address is out of date, tell me and I'll send another wherever works — no cost to you either way. If you'd rather have it collected, I can book a pickup for a day that suits you.
If you're able to send it this week, the return closes out and nothing further is needed. Thanks, [name].
| Record | Contents |
|---|---|
| Assignment | Who received what, when, signed acknowledgement of the return obligation |
| Transit | Carrier, tracking number, pickup or drop-off confirmation, delivery signature |
| Sanitization | Method, standard applied, operator, date, verification result, certificate |
| Disposition | Redeployed to whom, resold for how much, or recycled by which certified processor |
If any one is missing, the device is functionally undocumented no matter where it physically sits. When an auditor asks, records answer - memory does not.
The SOP above holds everywhere. What changes per country is the physical execution — and that is where most offboarding workflows quietly break. Our retrievals in a recent 200-order sample came from 34 countries, led by the United States, United Kingdom, Mexico, the Philippines, India, Brazil and Colombia. Only one of those is a market where a US domestic parcel playbook works unmodified.
Customs, borders and duty came up buyer-led in 216 of 3,977 conversations (6.1%), and the friction is specific. Some markets have no reseller and no residential collection at all — one IT buyer told us plainly: “there's no VARs out there that could just ship the devices. And there's also no one to collect.” Some require a local importer of record, and a device leaving a country can trigger export documentation the outbound process never touched. Often the freight simply costs more than the asset is worth.
| Where the SOP breaks | What GroWrk runs instead |
|---|---|
| The trigger depends on someone remembering | HRIS-triggered case creation with a custody state per device |
| Nobody owns the 44% of retrievals sitting in a waiting state | A named owner and an exception queue that escalates on time without progress |
| No carrier will collect from a home address | Scheduled local pickup and in-country partners across 150+ countries |
| Freight costs more than the laptop is worth | In-region storage and redeployment to the next hire in the same market |
| Devices ship un-enrolled or return activation-locked | Device management that enrolls before shipping and releases the tenant at disposition, alongside Intune, Jamf and Apple Business Manager |
| Nothing to hand an auditor | Assignment, transit, sanitization and disposition records against every asset |
| Per-seat licences billed for people holding no device | Pricing you can model against real device count and departure rate |
GroWrk retrieval operations. Retrieval counts, completion rates and open-queue states are drawn from GroWrk's live operations platform on 26 August 2026, covering Offboarding and Collection orders initiated from September 2022 onward. Counts are order-level; a single order may cover more than one device. “Completed” means an order reached closed status; cancellations include customer-initiated changes and duplicate records, not only failed recoveries. Country figures are from a 200-order sample of recent retrievals and are indicative of mix, not a total country count.
GroWrk Call Intelligence. Figures cited as conversation counts come from analysis of 3,977 recorded customer calls, April 2024 to August 2026, counting only calls where the customer raised the topic before any GroWrk representative did. The corpus captures what buyers said and how often; it does not measure satisfaction, preference or win rates.
This guide provides general information on IT asset management practices and is not legal advice. Employment, wage, customs and data-protection requirements vary by jurisdiction.
Open a recovery case from the HRIS separation event with a frozen serialized asset list; verify personal email, phone and current address; schedule access revocation with a stated backup window; send return instructions to the personal address; dispatch a prepaid kit within a day; issue the MDM lock at dispatch and the wipe in transit; track custody states and escalate on lack of progress; match the serial at intake; hold the device until the wipe is verified; then sanitize, release it from the MDM tenant, and record a disposition.
The employee, not the carrier. Across GroWrk's open retrieval queue, 44% of in-flight retrievals are in a waiting or blocked state, and those waiting on the departing employee outnumber those waiting on the IT team by roughly 2.5 to 1 (123 versus 49). The label usually exists and the box has often already arrived; the device simply has not been handed over. This is why the first carrier scan — not delivery — is the custody transition worth measuring.
Schedule it on the separation trigger, execute it after a stated backup window of 24 to 72 hours. Immediate blanket revocation removes the employee's ability to save personal files or read your return instructions, which reliably slows the physical recovery. Record the revocation timestamp on the case as part of the chain of custody.
Target the device in carrier custody within 7 days domestically and 14 internationally, with the case closed within 5 business days of delivery. Treat the international clock as a separate target rather than an extension of the domestic one — carrier scheduling and customs add time you do not control.
Across 14,708 retrievals GroWrk has initiated since September 2022, 13,101 have completed and 1,087 were cancelled — a 92% completion rate on resolved retrievals, with cancellations including customer-initiated changes rather than only failed recoveries. Your own rate depends heavily on whether anyone owns the escalation when an employee stops responding.
Both. Issue the remote lock when the kit is dispatched and the wipe command once the device is in transit, because transit is part of the risk window. Then verify at intake and sanitize to NIST SP 800-88 Rev. 2 before any redeployment. A queued wipe command against an offline machine proves you asked, not that it happened.
A security hold is a mandatory pause between intake and disposition. The device is received and logged but blocked from redeployment or resale until encryption status and sanitization are verified. It exists because the most common data exposure in this workflow is not a stolen laptop — it is a device assumed wiped and pushed straight back into the fleet.
Work a threshold ladder: automated reminders at day 3, address and kit-delivery verification at day 5, one manager or HR contact at day 7, MDM remote lock at day 10, formal written demand at day 14, civil recovery or legal referral at day 30, then a documented write-off. Verify the logistics before treating silence as refusal — a wrong address explains more overdue devices than deliberate non-compliance does.
Usually not, and it varies by jurisdiction. Federal law limits deductions that push non-exempt pay below minimum wage, improper deductions from an exempt employee's salary can jeopardize the exemption, and states including California and New York sharply restrict deductions for employer property. Use a written demand and civil recovery instead. General information, not legal advice.
HR owns the trigger and the employee relationship; IT and Security own access, endpoint controls and sanitization; IT Operations owns logistics, tracking and the exception queue; Receiving owns intake verification. One of them must own the outcome. Programs fail when every function completes its own task and nobody is accountable for whether the device came back — which is exactly how a retrieval ends up sitting in a waiting state for a month.
Standardize the workflow and the custody record; localize the physical execution. A return may be a prepaid label, a courier pickup, a local drop-off, an office return or an in-country partner depending on the market. Where shipping a device internationally costs more than the device is worth, recover and redeploy it in-country instead. In a recent 200-order sample, GroWrk retrievals came from 34 countries led by the US, UK, Mexico, the Philippines, India, Brazil and Colombia.