An Employee Left Three Weeks Ago. Who Owns the Laptop Recovery?

It's a scenario every IT and security team has lived through: someone resigns, HR processes the paperwork, the account gets disabled in Active Directory, and everyone quietly assumes the laptop situation is "handled." Three weeks later, nobody can say where the device is, whether it's been wiped, or who was supposed to chase it down. The account is dead, but the hardware — and whatever data is still sitting on its disk — is very much alive somewhere out in the world.

This is not a rare edge case. It's the default failure mode of offboarding at most companies, and it happens because the question in the headline almost never gets a clear answer before someone leaves. So let's answer it properly.




The Short Answer: It's Both, With One Twist

The honest answer is that laptop recovery is a shared responsibility between HR and IT, but shared responsibility without a named owner is exactly how devices go missing for three weeks. HR owns the employment event — they know the departure date, they hold the exit interview, and they typically have the only channel left to a former employee once their corporate account is dead. IT owns the technical side: the authoritative asset inventory, access revocation, MDM lock and wipe commands, and serial number verification when something does come back.

Where most organizations get this wrong is treating that split as the end of the conversation. In practice, the handover between HR and IT is exactly where recovery breaks down, because each side assumes the other is tracking the physical device. One source puts it bluntly: the accountable person should sit in IT, not HR, because HR can facilitate communication but the technical custodian of the device is the one who should own the recovery task and close it out with confirmation. Whatever org chart you use, the critical rule is that one team or one named individual must remain accountable until the device is physically back in hand and the asset record is closed.

Why Three Weeks Is Already a Red Flag

If it's been three weeks and nobody owns this, you've likely already skipped the two moves that determine whether recovery succeeds: starting early and having a return kit ready before the last day. The retrieval process should trigger the moment someone resigns, not on their final day and certainly not after they're gone. Best practice calls for issuing return instructions or a prepaid shipping kit within 24 to 48 hours of the termination notice, while the person is still engaged, still checking a channel you control, and still has some incentive to cooperate.

Once someone is three weeks past their last day, you've lost the easiest leverage point: their active employment relationship. Now recovery depends on a personal email address, maybe a phone number, and whatever equipment agreement they signed on day one. That's why a growing number of teams frame the return obligation as a lifecycle problem that starts at onboarding, not a scramble that starts at the exit interview.

What Should Have Happened Already — And What to Do Now

A functioning offboarding process separates the digital response from the physical response, because they move at different speeds and can't wait on each other. Digital access — email, VPN, SSO, shared credentials, cloud storage — should be revoked the day someone leaves, full stop, regardless of where the laptop physically is. The device itself, if it's under MDM, should be locked immediately to prevent further local access, and a wipe should be queued according to policy.

If you're three weeks in and this hasn't happened, here's the sequence to run now:

  1. Confirm the device is online. Check your MDM or endpoint tool to see if the laptop has phoned home recently and where. If it's reachable, lock it immediately to stop any further local data access.

  2. Verify the asset record. Pull the serial number, model, and any accessories assigned to that employee so you know exactly what's outstanding.

  3. Escalate to a named recovery owner. Someone — typically in IT, sometimes IT Operations or a dedicated People Ops function — needs to own tracking this to completion, not just flag it and move on.

  4. Reach the former employee directly. Use the personal contact information HR should have collected at offboarding, send one clear message with a deadline, and avoid a barrage of chase emails, which tends to reduce response rates rather than improve them.

  5. Decide between physical recovery and remote wipe. If the device can't be recovered quickly, or if it hasn't checked in for weeks, escalate the decision to remotely wipe it, accepting the loss of the hardware to protect the data.

  6. Document everything with timestamps. Chain of custody — who had the device, when access was revoked, when the wipe was issued, when contact was attempted — protects you if this ever becomes a legal or compliance question.

Building a Process So This Doesn't Happen Again

The real fix isn't a better chase email three weeks after the fact — it's structural. Put device return obligations in the employment contract and onboarding materials so employees know from day one that the laptop is company property and that failure to return it can be treated as retention of company property, not just an inconvenience. Build a simple ownership table into your offboarding runbook so nobody has to guess mid-crisis: HR triggers the offboarding case and captures personal contact details, IT confirms the asset list and issues the lock/wipe command, and one named recovery owner tracks the physical return until a serial number match confirms the device is back.

Some organizations skip the internal tug-of-war entirely by outsourcing device lifecycle management to a provider who handles shipping, follow-ups, and escalations as a service, reporting back only the outcome — device recovered or not — for internal action. Whether you build this in-house or outsource it, the underlying principle doesn't change: a disabled account is not a recovered laptop. Access revocation protects your systems today; physical recovery and verified data sanitization protect you for as long as that device exists. Three weeks in, the priority isn't assigning blame for the delay — it's naming an owner right now and closing the loop before it becomes three months.

Comments

Popular posts from this blog

The Inventory Illusion: Why Your Asset Register Will Fail the Audit

Compliance Check: Your Devices Are Secure, But Can You Prove Who Has Them?