Custom Offboarding Checklist
Installing this workflow tells Sense to send tailored offboarding tasks to departing employees, their managers, and your HR team, all built from a checklist screen you design yourself rather than the default one-size-fits-all list.
How it works
Build your offboarding checklist screen then let Sense assign it to everyone involved
To use the Custom Offboarding Checklist workflow, simply create a Form screen named Offboarding Checklist, design it with headers to separate the tasks for each role, and build three screen variants named Employee, Manager, and Admin, setting field visibility and profile permissions for each.
Then, every time an admin marks an employee as a leaver, Sense will automatically generate three separate tasks from that screen and send them to the leaver, their manager, and your HR team.
If the leaver hasn't logged in yet, then their task waits on their dashboard until their next login, since Sense deliberately skips emailing them in case you don't want them logging in straight away; managers and admins, on the other hand, get an email as soon as their task is assigned.
More onboarding & offboarding workflows
See all onboarding & offboarding workflows
Common questions
What kicks this workflow off?
An admin marking an employee as a leaver.
Who receives tasks, and how do they find out?
The leaver, their manager, and your HR team each get their own task. Managers and admins are emailed as soon as their task is assigned; the leaver's task appears on their dashboard once they next log in, with no email sent to them.
Why doesn't the leaver get an email?
Because you might not want them logging in to Sense yet, so their task simply waits on their dashboard instead.
How do we build our own checklist?
By creating a Form screen named Offboarding Checklist, then setting up three screen variants, Employee, Manager, and Admin, each with its own fields and permissions.
What controls who can see which sections?
Screen variant permissions control field visibility and editability per role, and separate profile-level permissions control who can view the full checklist screen.