---
title: "Offboard a leaver"
description: "From the termination date, brief the manager two weeks out, walk the leaver through their last two weeks, raise the access ticket with IT and send one note to their personal address after they have gone."
sidebar:
  order: 3
area: use-cases
appPath: /flows/home
lastVerified: 2026-11-16
version: "2026-11-13"
audience: admin
related:
  - flows/automations/tutorial-offboarding-flow
  - flows/automations/configure-a-date-trigger
  - flows/steps/raise-a-ticket
  - flows/automations/handle-late-enrollments
---

Every leaver has a clear last two weeks, their manager has a handover checklist, IT gets the access ticket a week ahead, and the person hears from you once after they have gone, all from one automation on the termination date. **For:** admins and owners. **Time:** about 45 minutes.

![The finished automation: the Off-boarding trigger two weeks before the termination date, the manager's handover, three notes to the leaver and one to their personal email a week after, in Verification.](https://support.pyn.ai/media/use-cases/offboarding/use-cases-offboarding-automation.png)

## What you'll need

- **Termination Date** synced; the **Off-boarding** trigger runs on it. In a Workday report it is the `Termination_Date` or `Term_Date` column; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/) and [Workday](https://support.pyn.ai/integrations/workday/).
- **Personal Email Address** synced for the post-exit note (`Home_Email_Address` in a Workday report).
- An email sender; see [Add an email sender](https://support.pyn.ai/settings/senders/add-an-email-sender/).
- For the IT ticket, Jira connected with your IT project ticked **Available to steps**, for a **Raise Ticket** step where enabled for your workspace; see [Jira](https://support.pyn.ai/integrations/jira/). Otherwise a verified custom email recipient for IT's queue, where enabled for your workspace; see [Add a custom email recipient](https://support.pyn.ai/settings/custom-email-recipients/add-a-custom-email-recipient/).
- Optional: a leaver FAQ in **Library** > **Content**, and an exit survey form.

## Build it

1. Create an automation with the **Off-boarding** trigger under **Employee Lifecycle** and change **This flow starts** from **the day before** to **2 weeks before**; the termination date stays the reference date; see [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/).

2. Keep **Lifecycle** at **Current**, because the audience is checked when the flow starts, two weeks before the last day; see [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/).

3. Add a **Send Email to Employee** step with **To** set to **Manager**, **2 weeks before**, carrying the handover checklist, a **Link Button** with **Track Action** ticked and a reminder **2 days after send**; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/), [Add a button to a message](https://support.pyn.ai/flows/steps/add-a-button-to-a-message/) and [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/).

4. Add three steps to **Employee**: **10 days before** on pay, benefits and equipment, **1 week before** to confirm their personal email, and **on the day of** to say goodbye; see [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/).

5. Add a **Raise Ticket** step, where enabled for your workspace, **1 week before**, with your IT project and issue type and a summary such as `Remove access for @principal.name`; a ticket offers `principal` tokens only, so the date is the step's schedule, not a token; see [Raise a ticket](https://support.pyn.ai/flows/steps/raise-a-ticket/).

6. Add a **Send Email to Employee** step **1 week after** with **To** set to **Employee (Personal)**, and on its **Audience** tab add **Terminated** to the lifecycle; see [Set a step audience](https://support.pyn.ai/flows/steps/set-a-step-audience/).

7. Turn on **Skip if overdue at enrollment** on the manager's step and the 10-day step so a same-day exit does not send them; see [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).

8. Publish, set the mode to **Verification** and review the first departures in **Needs Review** before moving to **Automated**; see [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/) and [Change the mode of an automation](https://support.pyn.ai/flows/automations/change-the-mode/).

## Variations

**Slack**

Before the last day, the manager's checklist and the leaver's messages work as **Send Direct Message** steps; see [Add a direct message step](https://support.pyn.ai/flows/steps/add-a-direct-message-step/). A Slack account is often deactivated on the last day and an unmatched recipient gets a **Bounced** delivery, so keep the post-exit note as an email to **Employee (Personal)**.

**Email**

Keep every step as **Send Email to Employee** and set **From** to your People team's mailbox, as in [Choose a sender](https://support.pyn.ai/flows/steps/choose-a-sender/), so a reply about final pay reaches a person.

Without Jira, the IT step is a **Send Email to Employee** step **1 week before** with the IT queue's custom email recipient under **To**. For a departure handled by hand, the catalogue's **Employee resigns** template has **No trigger**; enrol the person with **Manual Enroll** and **Verify Mode**; see [Use a flow without a trigger](https://support.pyn.ai/flows/automations/use-a-flow-without-a-trigger/).

## Watch out for

- **Off-boarding** is a date trigger on **Termination Date**; its default start, **the day before**, leaves no time for a handover; see [Trigger catalogue](https://support.pyn.ai/flows/automations/trigger-catalogue/).
- A Workday column with another name shows nothing under **Fields in Report** and nobody enrols; Pyn reads `Termination_Date` or `Term_Date`; see [Workday](https://support.pyn.ai/integrations/workday/).
- A last day under two weeks away is a late enrollment: the steps already due send at once unless they have **Skip if overdue at enrollment**; see [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).
- The post-exit step needs **Terminated** on its own **Audience** tab, or it reads **No recipient** and is **Skipped**; a leaver with no personal email address is skipped there too; see [Set a step audience](https://support.pyn.ai/flows/steps/set-a-step-audience/).
- A ticket step has no **To**, so no issue is created if its step audience excludes the employee. Identify the leaver with `principal.name` and `principal.email`; see [Raise a ticket](https://support.pyn.ai/flows/steps/raise-a-ticket/) and [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).
- A withdrawn resignation does not stop the enrollment by itself; stop it in Activity; see [Stop an enrollment](https://support.pyn.ai/activity/enrollments/stop-an-enrollment/).
- If **Publish** appears to do nothing, a step has no recipient; check each step's **To** field. See [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/).

## Check it worked

Two weeks before a termination date, the person appears under [Enrollments](https://support.pyn.ai/activity/enrollments/) with the termination date as **Reference Date**. In **Verification** it waits in **Needs Review**; see [Review and unpause enrollments](https://support.pyn.ai/activity/enrollments/review-and-unpause-enrollments/). Once unpaused, the manager's email shows as delivered the same day, the ticket's delivery links to the issue in Jira, and the post-exit email is scheduled a week after the last day at the personal address. [Track actions](https://support.pyn.ai/activity/actions/track-actions/) shows whether the manager has used the checklist button.

## Related

- [Tutorial: offboarding flow](https://support.pyn.ai/flows/automations/tutorial-offboarding-flow/) for the same automation with the message copy.
- [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/) for the offset.
- [Raise a ticket](https://support.pyn.ai/flows/steps/raise-a-ticket/) for the Jira step.
- [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/) for short-notice exits.
