A working offboarding checklist assigns a single owner to each task across IT, HR, and Security, sequences from at least 5 days before the last day through 14 days after, and ties device retrieval, access revocation, and compliance documentation into one workflow instead of three parallel ones. The most common failure is the handoff between HR's exit process and IT's retrieval follow-through.
That handoff is where, according to a 2023 Allwork.Space survey, 42% of companies lose at least one device per year during offboarding. The pattern is consistent: HR closes the file after the exit interview, IT waits for a device that may never arrive, and Security revokes access without ever confirming the disk was wiped. At Rayda, the offboarding workflow plugs into your HRIS so the retrieval task is created automatically when HR marks an employee for departure, and IT, HR, and Security all see the same status. If you are trying to align three teams across multiple countries and the process keeps stalling, talk to us, or keep reading for the full checklist and the RACI behind it.
This post covers why offboarding typically fails for distributed teams, how to assign clear ownership across IT, HR, and Security, what the actual checklist should include, how to sequence the steps so they get done, and where Rayda plugs into an existing workflow.
For the full end-to-end offboarding workflow including retrieval, wipe, and disposition, see The Global Device Offboarding Playbook.
Why Does Offboarding Typically Fail in Distributed Companies?
Offboarding fails in distributed companies because three teams each run their own checklist, and no single owner holds accountability across all of them. HR closes the file after the exit interview. IT waits for the device. Security revokes access on day one but never confirms the wipe was completed. The gaps between those parallel processes are where devices disappear, credentials linger, and compliance evidence goes missing.
The three-team coordination problem
HR, IT, and Security each have legitimate offboarding workflows of their own. HR is focused on payroll close-out, the exit interview, and the employment file. IT is focused on device recovery and asset records. Security is focused on access revocation and audit trail. None of these teams owns the full chain end-to-end. When something falls between two teams, like the wipe certificate that IT thinks Security tracks and Security thinks IT generates, it doesn't get done.
Why a shared checklist beats three separate ones
A shared checklist works because every team can see what the others have done and what remains open. Each task has one accountable owner, and the rest of the teams are either consulted or informed. The most common offboarding failures are not skill problems or motivation problems. They are coordination problems. A single source of truth solves them.
Where contractors fall through entirely
Contractors are often outside HR systems entirely, which means none of the three teams gets a clean offboarding trigger when a contractor's engagement ends. The retrieval workflow that fires automatically for full-time departures simply never starts. Contractor offboarding needs its own track, which is covered in offboarding contractors vs. full-time employees: what changes.
Who Owns What in an Offboarding Process?
A working offboarding RACI assigns IT to own device retrieval and wipe, HR to own employee communication and exit timing, and Security to own access revocation and compliance verification. Each task has exactly one accountable owner. The other teams may be consulted or informed, but accountability sits with one team and one team only.
The RACI matrix for the offboarding process looks like this:
| Task | IT | HR | Security |
|---|---|---|---|
| Confirm termination date | I | A | I |
| Notify all teams of offboarding | C | A | C |
| Communicate return policy to employee | I | A | I |
| Trigger device retrieval | A | I | I |
| Coordinate device pickup | A | C | I |
| Audit employee access profile | C | I | A |
| Revoke credentials and tokens | I | I | A |
| Perform certified data wipe | A | I | C |
| Issue wipe certificate | A | I | C |
| Verify wipe before reassignment | C | I | A |
| Update asset register | A | I | I |
| Close HR file | I | A | I |
(A = Accountable, R = Responsible, C = Consulted, I = Informed)
What HR is responsible for
HR confirms the termination date, notifies IT and Security no later than five business days before the last day, communicates the device return process to the employee, and confirms the signed equipment agreement is on file. HR closes the offboarding file only after IT confirms the device has been returned or formally written off, not before.
What IT is responsible for
IT triggers the retrieval workflow on notification from HR, coordinates pickup logistics (local vendor, prepaid label, or drop-off depending on region), tracks device status in the asset management system, and confirms receipt, condition, and certified wipe. IT updates the inventory record and flags the device for redeploy or dispose decision.
What Security is responsible for
Security revokes all access credentials on the last day or immediately on termination, verifies MDM enrollment status, confirms a certified wipe has been completed before any reassignment, and either issues or archives the certificate of data destruction for compliance records. The handoff between IT and Security on the wipe step is where most audits find gaps. IT considers its job done when the device arrives. Security considers its job done when MDM access is revoked. Neither team is confirming the device was physically sanitized to a documented standard. For what a compliant wipe actually requires, see device data wipe compliance across countries.
What Should the Offboarding Checklist Include?
A complete offboarding checklist covers three time windows: pre-departure (5+ days before the last day), the last day itself, and 14 days after the employee leaves. Each window has concrete actions, named owners, and deadlines. The most common mistake is treating "last day" as the start of the offboarding process. By then, it is too late to coordinate retrieval in another country.
Pre-departure (Day -5 to Day 0)
- HR confirms termination date and notifies IT and Security
- IT logs the device location, model, and assigned region
- IT initiates the retrieval workflow (local vendor, label, or drop-off)
- Security audits the employee's access profile and identifies high-risk credentials
- HR confirms the equipment return policy with the employee
- IT confirms the wipe procedure and certificate template are ready
Last day (Day 0)
- HR conducts the exit interview and confirms device return logistics
- IT confirms retrieval is in progress and gives the employee any final instructions
- Security flags all access for revocation at the end of the business day
- All three teams confirm the offboarding tracker shows expected next steps
Post-departure (Day 1 to Day 14)
- Security revokes all access credentials, tokens, and MDM enrollment
- IT completes device pickup and inspection
- Device is wiped to NIST 800-88 Purge standard
- Wipe certificate generated and stored against the asset record
- IT updates asset register with final disposition status
- HR receives confirmation that all three workstreams are complete and closes the file
How Do You Sequence the Steps So They Actually Get Done?
The offboarding checklist only works if it is triggered automatically when HR confirms a termination, not when someone manually remembers to start it. The working sequence is: HRIS event fires, IT receives the retrieval task, Security receives the access revocation queue, and all three teams see shared status until close-out. Manual notification creates the coordination gaps that lose devices.
Why "last day" is too late for retrieval setup
International device pickup takes 5 to 10 days from notification to physical collection, depending on country. If retrieval starts on the last day, the device does not come back for two to three weeks at best, and often does not come back at all. Pre-departure triggering is the only sequence that works for distributed teams. For the full retrieval workflow including method comparisons by region, see how to retrieve company laptops from remote employees.
Trigger-based automation
The cleanest sequence ties the HRIS event to both IT and Security workflows automatically:
- HR marks employee as departing in BambooHR, Rippling, JustWorks, or similar
- HRIS fires a webhook to IT's asset management or ticketing system
- IT receives a retrieval task with device, region, and termination date pre-populated
- HRIS fires a parallel webhook to Security's access management system
- Security receives an access audit task and a scheduled revocation for the last day
- HR sees back-confirmation from both IT and Security in the HRIS
This sequence removes the most error-prone step: the manual handoff from HR to the other two teams. According to Rayda's research on company device return rates, the absence of an automatic retrieval trigger is one of the largest single drivers of device loss at offboarding.
How Does Rayda Plug Into an Existing Offboarding Workflow?
Rayda integrates with major HRIS platforms so the moment an employee is marked for offboarding, a retrieval task is created automatically and routed to the local pickup network in the employee's country. IT, HR, and Security all see the same status in a shared dashboard. The integration removes the manual notification step that causes most offboarding gaps.
HRIS trigger integration
When HR marks an employee for departure in their HRIS, Rayda creates the retrieval task automatically. The employee's address, device, and target retrieval date are populated from the HRIS record. No one in IT or Security needs to manually start the workflow, which removes the lag that causes most retrieval failures in the first place.
Shared dashboard for IT, HR, and Security
The dashboard gives all three teams a single source of truth for every active offboarding. IT sees retrieval and wipe status. HR sees confirmation of device return for file close-out. Security sees the wipe certificate and access revocation status. Each team works from the same data without needing to email each other for updates.
Status updates pushed back into HRIS
When retrieval completes and the wipe certificate is generated, status updates flow back into the HRIS so HR can close the file without leaving their workflow. The certificate is retained for SOC 2, ISO 27001, and GDPR Article 30 records. The entire workflow closes the loop on what is typically the most fragmented part of the employee lifecycle.
FAQ
How long should the full offboarding process take for a remote employee?
A well-run offboarding process takes 14 to 21 days from termination confirmation to closed file. Pre-departure planning takes 3 to 5 days, retrieval takes 5 to 10 days depending on country and method, and wipe plus inspection takes 2 to 4 days. Manual processes that rely on prepaid labels in emerging markets routinely take 45 to 90 days, and often do not complete at all. The 14-to-21 day target only holds if the retrieval trigger fires automatically before the last day, not after.
Who should send the device return reminder to the employee?
HR should send the initial communication about device return, since the relationship with the employee is theirs. IT can send the practical pickup details (date, courier, packaging) once retrieval is scheduled. If the employee is unresponsive after the last day, escalation should go from HR first (relationship-led), then to legal or finance if non-return becomes a payroll deduction question. The handoff sequence matters because employees respond better to HR-led messaging than to a cold pickup notification from a logistics partner.
What's the right time to revoke access during offboarding?
For voluntary departures, revoke access at the end of business on the last day. The employee may still need limited access during exit handover, and revoking it earlier can create friction without security benefit. For involuntary terminations or any case where there is a security concern, revoke access immediately at the moment of termination, before the employee leaves the meeting. Security should pre-stage the revocation in the access management system during pre-departure so the actual revocation is a one-click action.
How do we handle offboarding when the employee is in a different country than HR and IT?
A distributed offboarding workflow requires a local retrieval partner in the employee's country, an HRIS trigger that fires regardless of geography, and a wipe step that does not require the device to ship internationally. Devices recovered locally should be wiped locally and stored or redeployed in the same region. International return shipping is rarely worth the customs and freight cost. The full breakdown of why is in the customs and tax post in this cluster, and the operational details for cross-border retrieval are in the retrieval guide linked above.
Should we use the same offboarding checklist for contractors?
No. Contractors are typically outside HR systems, have shorter notice periods, and may have received devices through informal channels without signing a standard equipment agreement. Forcing them through the full-time offboarding process either misses them entirely or creates artificial steps that do not apply. A separate contractor offboarding track, triggered by procurement or the hiring manager rather than HR, works better. The full breakdown is in offboarding contractors vs. full-time employees.
What happens if HR doesn't notify IT before the last day?
If HR notification slips past the last day, retrieval is delayed by however long the notification gap was, plus the standard 5 to 10 day pickup window. Devices in distributed teams often do not come back at all in this scenario, because momentum to follow up dies once the employee has formally left. The fix is structural, not procedural: the HRIS trigger should fire automatically when the termination date is entered, not when someone remembers to message IT. Manual notification is the single largest source of avoidable device loss at offboarding.
If your team is running parallel offboarding processes across IT, HR, and Security and the handoffs keep breaking, the shared-checklist approach above is what good offboarding looks like in practice. Rayda's HRIS integration creates the retrieval task automatically and gives all three teams the same view of every active offboarding, across 170+ countries. Book a demo to see how it lines up with your existing workflow.
