---
title: "Mark a promotion or change of manager"
description: "The day a reporting line changes, introduce the employee to their new manager and brief the manager on who has joined their team; send a promoted employee a note from HR, by trigger where your HRIS carries the change and by hand where it does not."
sidebar:
  order: 2
area: use-cases
appPath: /flows/home
lastVerified: 2026-11-15
version: "2026-10-23"
audience: admin
related:
  - flows/automations/configure-a-team-change-trigger
  - flows/automations/configure-an-employee-property-trigger
  - flows/automations/manually-enroll-employees
  - use-cases/new-manager
---

The day someone's reporting line changes, they hear how the handover works and their new manager gets a briefing on who has joined their team. A promoted employee gets a note from HR on the effective date, by trigger where your HRIS carries the change and by **Manual Enroll** where it does not. **For:** admins and owners. **Time:** about 30 minutes per automation.

![The finished automation: the Change of Manager trigger, a note to the employee and a briefing to the new manager, both on the day.](https://support.pyn.ai/media/use-cases/promotion-or-manager-change/use-cases-promotion-or-manager-change-automation.png)

## What you'll need

- **Manager** synced and populated for everyone; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/) and [Fix a missing manager, time zone or email](https://support.pyn.ai/directory/employees/fix-missing-details/).
- For promotions by trigger, a property that changes with the promotion: **Job title**, or a level field mapped as a custom field; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/). Without one, a list of the promoted people and their effective dates.
- An email sender, or Slack connected for direct messages; see [Add an email sender](https://support.pyn.ai/settings/senders/add-an-email-sender/) and [Slack](https://support.pyn.ai/integrations/slack/).
- Optional: a demographic group per level, so a **Group Change** trigger can watch people entering it; see [Configure a group change trigger](https://support.pyn.ai/flows/automations/configure-a-group-change-trigger/).

## Build it

1. Create an automation with the **Change of Manager** trigger under **Team and Org Changes**; its principal is the employee whose manager changed; see [Configure a team change trigger](https://support.pyn.ai/flows/automations/configure-a-team-change-trigger/).

2. Keep **Lifecycle** at **Current** and exclude any group whose reporting lines should not count, such as contractors; see [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/).

3. Add a **Send Email to Employee** step to **Employee**, **on the day of**, introducing the change, and a second step with **To** set to **Manager** briefing the new manager on who has joined their team; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).

4. Write both with `@principal.managerPreferredName` for the new manager and `@recipient.preferredName` for whoever receives the message; see [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).

5. For promotions your HRIS exposes as a title or level, create a second automation on **Employee Properties** with the property and the exact value to match, or on **Group Change** with **Employee enters group** on the level's group; see [Configure an employee property trigger](https://support.pyn.ai/flows/automations/configure-an-employee-property-trigger/) and [Configure a group change trigger](https://support.pyn.ai/flows/automations/configure-a-group-change-trigger/).

6. For promotions your HRIS does not expose, create an automation with **No trigger**, publish it in **Manual** mode and enrol each promoted person with the effective date as **Reference Date**; see [Use a flow without a trigger](https://support.pyn.ai/flows/automations/use-a-flow-without-a-trigger/) and [Manually enroll employees](https://support.pyn.ai/flows/automations/manually-enroll-employees/).

7. Publish each automation and preview the manager's step for a current employee to confirm the resolved recipient in the preview header; see [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/) and [Preview and send a test](https://support.pyn.ai/flows/steps/preview-and-send-a-test/).

## Variations

**Slack**

Swap each **Send Email to Employee** for **Send Direct Message**, as in [Add a direct message step](https://support.pyn.ai/flows/steps/add-a-direct-message-step/). A manager with no matched Slack account gets a **Bounced** delivery, so keep the manager's briefing on email unless every manager is in Slack.

**Email**

Keep the steps as **Send Email to Employee**, set **From** to your People team's mailbox so a reply reaches a person, and Cc **HRBP** on the manager's briefing; see [Choose a sender](https://support.pyn.ai/flows/steps/choose-a-sender/).

For a batch of promotions after a review cycle, upload a spreadsheet with a **Reference Date** column and a `New Title` column, read in messages as `custom.newTitle`; see [Enroll from a spreadsheet](https://support.pyn.ai/flows/automations/enroll-from-a-spreadsheet/). For someone gaining their first direct report, use the **Promoted to Manager** trigger and the series in [Support a new manager](https://support.pyn.ai/use-cases/new-manager/).

## Watch out for

- **Change of Manager** fires on every change of manager, including an HRIS correction, with a one-month gap before the same person enrols again; see [Prevent repeat enrollments](https://support.pyn.ai/flows/automations/prevent-repeat-enrollments/). Run it in **Verification** mode at first so a data fix does not send an introduction; see [Change the mode of an automation](https://support.pyn.ai/flows/automations/change-the-mode/).
- A text property match is exact and case-sensitive: `Senior Engineer` does not match `senior engineer`. Copy the stored value from a promoted employee's record; see [Configure an employee property trigger](https://support.pyn.ai/flows/automations/configure-an-employee-property-trigger/).
- The reference date is the day the change reaches Pyn, not the effective date in the HRIS. A backdated promotion enrols late and the steps already due send at once; see [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).
- Tokens are filled when the message is sent, so `@principal.managerPreferredName` in a step weeks after the change names whoever is the manager then; keep introductions **on the day of**; see [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).
- Team change and group change triggers ignore changes during the first HRIS load, so nobody is enrolled for a reporting line that existed when you connected the HRIS; see [Trigger catalogue](https://support.pyn.ai/flows/automations/trigger-catalogue/).
- 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

The day a reporting line changes, the employee appears under [Enrollments](https://support.pyn.ai/activity/enrollments/) with that date as **Reference Date**, and the manager's step lists the new manager by name. A property or group trigger enrols within a few hours. A manual enrolment shows the reference date you set, and in **Verification** it waits in **Needs Review**; see [Review and unpause enrollments](https://support.pyn.ai/activity/enrollments/review-and-unpause-enrollments/).

## Related

- [Configure a team change trigger](https://support.pyn.ai/flows/automations/configure-a-team-change-trigger/) for Change of Manager.
- [Configure an employee property trigger](https://support.pyn.ai/flows/automations/configure-an-employee-property-trigger/) for a title or level match.
- [Manually enroll employees](https://support.pyn.ai/flows/automations/manually-enroll-employees/) for promotions the HRIS lacks.
- [Support a new manager](https://support.pyn.ai/use-cases/new-manager/) for first-time managers.
