How offboarding works
1
Termination detected
Layer receives a termination event from your connected HRIS (e.g. BambooHR, Gusto, Rippling) or identity provider. The event includes the departing employee’s identity, last working day, manager, and return shipping address (if available).
2
Task created
Layer creates an offboarding task for the employee. It queries the employee’s assigned assets and generates a per-app action plan automatically.
3
Actions executed
Layer executes each action through your connected integrations, with automatic retries for transient failures.
4
Hardware return tracked
If the employee has assigned devices, Layer initiates the hardware return workflow with shipping labels, tracking, and escalation.
Action types
Layer determines the correct action for each asset based on the asset type and authentication method:
Each action moves through these statuses: Pending → In progress → Completed (or Partial if only partially successful).
Deduplication
Layer prevents duplicate offboarding tasks for the same employee. If a task already exists in apending or in_progress state, new termination events for that employee are ignored. This is enforced both at the application level and by a database constraint.
Hardware returns
When a departing employee has assigned devices, Layer tracks the full return lifecycle:Return statuses
Escalation schedule
If an employee hasn’t returned their device, Layer escalates automatically:
Escalation notifications are sent via your configured notification channels.
Device inspection
When a device is received, it goes through an inspection checklist:- Screen cracks
- Dents or physical damage
- Missing keys
- Port damage
- Battery health issues
- Accessories present