Employee offboarding software
An employee leaves. Their responsibilities shouldn't.
01A successor on every termination
The termination can't be saved until someone is named to take over.02Ownership moves on its own
The day after the termination date, reports, departments, workflows, and approvals change hands.03A fallback if the successor leaves too
Skailer goes up the management chain to the first active employee.04Every change on record
The audit log lists what moved, what closed, and when.The problem
When someone leaves, their work stays behind
An employee's last day closes their laptop, and often that's all it closes. Their direct reports still list them as manager. Time off requests wait in an approval queue nobody will open. A workflow they owned keeps running with no one to fix it, and the integration they connected loses its owner. Review forms and signature requests addressed to them stay open, so the cycles around them can't finish. HR goes looking for every place the person's name appears, one module at a time, and usually finds the last one when a process breaks. Skailer changes that by building the handover into the termination itself. Name a successor once, and the rest follows.
Successor
Name a successor on every termination so no work goes unowned
The termination form asks for a successor in Handover to, and it won't save without one. Pick anyone who stays with the company; they don't have to take over the role itself. If the successor has left by the time the handover runs, Skailer takes the first active person up the chain: their manager and that manager's manager, then department managers, then the organization owner. Terminations from an import or the API follow the same order.
01Required Handover to field
Every termination names who continues the work.02Fallback up the chain
Manager, department manager, then the organization owner.03Terminated people skipped
A team leaving at once still ends with a live successor.04Import and API covered
The same order applies when no replacement was set.05Older records too
Editing a past termination asks for a successor before saving.Handover
Move everything they owned the day after they leave
The handover runs once, on the day after the termination date, by your organization's timezone. Direct reports get the successor as their manager, with a new position record. Departments, workflows, company integrations, goals, message templates, news channels, and job offers change owner. Approvals move in open requests and in approval policy stages. Who created what stays as it was, because author fields are never rewritten.
01People and structure
Direct reports, managed departments, and team lead roles.02Processes and integrations
Owned workflows, Slack, Google, ATS, and HRIS connections.03Approvals
Open requests and policy stages; duplicate stages are skipped.04Owned objects
Goals, message templates, news channels, and job offers.05Assignment rules
Rules naming them pick the successor when nobody else remains.Clean close
Close what can't change hands so nothing waits forever
Some work belongs to one person and can't be passed on. A signature request holds the signer's own name, email, and identity check, so the signing is cancelled and the requester is notified to send it again. Review forms, survey answers, and interview feedback addressed to them are cancelled, and answers already submitted stay. Their pending requests and candidate email sequences stop, and their personal mailbox connection is switched off. Nobody gets access to someone else's mail.
01Signature requests
Cancelled with a notice to the requester; existing signatures stay.02Reviews and surveys
Open forms cancelled, so cycles can finish without them.03Own requests and sequences
Pending requests cancelled, candidate email sequences stopped.04Time off settled
Final accrual, later leave cancelled, overlapping leave trimmed.05Sign-in disabled in one action
Reversible, with employment records left untouched.Exit steps
Run exit steps on the termination date so nothing is missed
Handover covers what lives in Skailer. The rest of the exit runs on dates tied to the termination: IT gets a task to collect the laptop, the manager gets one to plan knowledge transfer, and the team hears the news by email or in Slack. On the last day, the employee's Google Workspace account can be deleted and other systems updated through a signed HTTP request. Exit surveys and documents go out before the termination date, while the employee can still respond.
01Timed to the termination
On the termination itself, or a set day before or after it.02Tasks for IT and the manager
With due dates, reminders, and the employee's name.03Google Workspace account removal
Deleted as a step in the exit.04Team and external notices
Email, Slack, a Slack channel, or an outside address.05Exit survey and documents
Sent before the last day.
Records & reporting
Keep the history so every exit stays traceable
Termination ends the employment, and the record stays. The profile, Employment history, and position changes remain for compliance and reporting. Leave type and termination reason come from your own lists, so every record uses the same options. Headcount, retention, and salary reports filter by terminated employees. A future termination date keeps the employee active until that day, then switches their status to Terminated automatically.
01Audit log per termination
Every automatic change in one list.02Position history
A new manager record for each direct report.03Consistent reasons
Leave type and termination reason from configured lists.04Turnover reporting
Headcount, retention, and salary reports filter by terminated employees.05Status on the right day
Future-dated terminations switch status on the effective date.One HR platform
Close the loop that onboarding opened
Offboarding works on the same employee record that onboarding started. Handover is built into every termination; Flows adds the exit steps your team runs, from IT tasks to account removal. Time off is settled on the termination date, approvals move to the successor, and the departure lands in headcount and retention reports.
What is employee offboarding in Skailer?
Compliance
See every change a departure made
Each termination keeps its own audit log of automatic changes, and Position history shows every new manager record. Nothing personal changes hands: the departing employee's mailbox connection is switched off, and signature requests are cancelled, since a signature carries the signer's own identity. The profile and employment records stay in the system for compliance and reporting. Disabling sign-in and deleting profiles each require their own permission.
Skailer vs. the alternativesMost HR tools treat offboarding as a checklist: tasks for HR, IT, payroll, and the manager, due before the last day. The better ones also track equipment, close access on schedule, and calculate final pay. A checklist still can't find every place a person's name is attached and reassign it, so that part usually stays with HR.
See where offboarding checklists stop
| Capability | Spreadsheets & email | Checklist-based offboarding tools | Skailer |
|---|---|---|---|
| Successor | Named in an email, if at all | Handover written up as a task or notes | Required on every termination, with a fallback chain |
| Direct reports & departments | Reassigned by hand, one by one | Usually updated manually | Moved to the successor the day after the termination date |
| Approvals in progress | Wait until someone notices | Often rerouted by hand | Move to the successor in open requests and policy stages |
| Flows & integrations | Lose their owner | Depends on the tool | Change owner automatically |
| Open signatures & reviews | Stay open | Closed by hand | Cancelled, with the requester notified |
| Exit tasks | Spreadsheet checklist | Checklist with due dates | Tasks and notices tied to the termination date |
| Record of changes | None | Task completion history | Audit log of every automatic change |
How it works
How employee offboarding works in Skailer
01Record the termination
Enter the termination date, leave type, reason, and the successor in Handover to. With a future date, the employee stays active until that day.02Add your exit steps
Set up the steps your team runs when someone leaves: IT and manager tasks, Google Workspace account removal, team notices, and an exit survey, each timed to the termination date.03Let the handover run
The day after the termination date, direct reports, departments, workflows, integrations, goals, and approvals move to the successor. What can't move is closed, and time off is settled.04Check what changed
Review the termination's audit log and Position history. When the exit is done, disable sign-in from Manage access in one action.Employee offboarding in Skailer: common questions
What is employee offboarding software in Skailer?
It's the termination process that hands a departing employee's work to a successor. Skailer moves their reports, departments, workflows, integrations, goals, and approvals, closes what can't be reassigned, and runs exit steps on dates tied to the termination.