---
title: "Give managers a new-hire checklist"
description: "Each manager gets the right ask at the right time, equipment a week out, a first-week plan on day one, a 30-day check-in, with a button to confirm, reminders if they do not, and a list of who has still to act."
sidebar:
  order: 1
area: use-cases
appPath: /flows/home
lastVerified: 2026-10-26
version: "2026-10-23"
audience: admin
related:
  - flows/steps/add-a-button-to-a-message
  - flows/steps/add-reminders
  - flows/steps/add-escalations
  - activity/actions/track-actions
---

A manager is asked three times, at the right moment each time: order the equipment a week before the start date, run the first-week plan on day one, hold a check-in at 30 days. Each ask has a button to confirm, a reminder if they do not, an escalation if they still do not, and HR sees who has acted. **For:** admins and owners. **Time:** about 30 minutes.

![The checklist step open: To is Manager, the message carries a tracked button, and the Reminders tab holds the reminders and, below them, the Escalations section.](https://support.pyn.ai/media/use-cases/manager-checklist-for-a-new-hire/use-cases-manager-checklist-for-a-new-hire-step.png)

## What you'll need

- **Manager** mapped and populated for every new starter; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/). A blank manager traces back to one source, see [Fix a missing manager, time zone or email](https://support.pyn.ai/directory/employees/fix-missing-details/).
- 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/).
- The checklist published in **Library** > **Content**, or hosted somewhere a **Link Button** can open; see [Publish content](https://support.pyn.ai/library/content/publish-content/).
- An automation to put the steps in: [Reach new starters before day one](https://support.pyn.ai/use-cases/pre-boarding/) or [Onboard from the first day to six months](https://support.pyn.ai/use-cases/onboarding-to-six-months/).

## Build it

1. In the automation, add a **Send Email to Employee** step scheduled **7 days before**, and under **To** choose **Manager**, so the step resolves to each new starter's own manager; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).

2. Write it to the manager with `@recipient.preferredName`, and name the new starter and their date with `@principal.preferredName` and `@principal.startDate`; see [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).

3. Add a **Link to Library Content** button that opens the checklist, or a **Link Button** to your own page, and leave **Track Action** ticked so the click counts as done; see [Add a button to a message](https://support.pyn.ai/flows/steps/add-a-button-to-a-message/) and [Link to content from a message](https://support.pyn.ai/library/content/use-content-in-a-step/).

4. On the **Reminders** tab add a reminder **2 days after send** and a second at 4 days; see [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/).

5. Under **Escalations**, add one **7 days after send** and change the recipient to **Skip-level Manager**, or a named person under **People**; see [Add escalations](https://support.pyn.ai/flows/steps/add-escalations/).

6. Repeat for the first-week plan **on the day of** and the 30-day check-in **30 days after**, each with its own button; see [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/).

7. Open **Preview**, pick an upcoming joiner under **Preview for principal** and check the header shows their manager as the recipient, then **Send a test to yourself**; see [Preview and send a test](https://support.pyn.ai/flows/steps/preview-and-send-a-test/).

8. Publish, and tick the running enrollments in **Update Enrollments** so starters already in the flow get the new steps; see [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/).

## Variations

**Slack**

Use **Send Direct Message** with **To** set to **Manager**, as in [Add a direct message step](https://support.pyn.ai/flows/steps/add-a-direct-message-step/). The button renders as a Slack button and the reminder is a copy of the same DM. An escalation goes out in the step's own medium, so a Slack step can notify your People team's channel, chosen under **Channels**.

**Email**

Keep **Send Email to Employee** so the ask sits in the manager's inbox, and set **From** to a mailbox a reply can reach. An email step escalates to a verified custom email recipient under **Email addresses**, where enabled for your workspace; see [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).

For a step only some managers get, use the step's **Audience** tab; it is checked against the recipient, so a department group there means the manager's department, not the new starter's; see [Set a step audience](https://support.pyn.ai/flows/steps/set-a-step-audience/).

## Watch out for

- A step without a tracked button or form is not actionable: the **Reminders** tab reads **This step has no actionable content such as buttons or forms**, and any reminder on it sends every time; see [Add a button to a message](https://support.pyn.ai/flows/steps/add-a-button-to-a-message/).
- An escalation that resolves to the original recipient is not created, so on a step to **Manager** pick **Skip-level Manager** or a named person; see [Add escalations](https://support.pyn.ai/flows/steps/add-escalations/).
- A reminder still pending when the manager acts is cancelled and shows as **Invalid** under **Enrollments**; the **Actions** view is the record to trust; see [Add reminders](https://support.pyn.ai/flows/steps/add-reminders/).
- Tokens follow roles: `@principal.startDate` is the new starter's date even in a message to the manager, and `@recipient.startDate` is the manager's own; see [Tokens](https://support.pyn.ai/flows/steps/reference-tokens/).
- A new starter with no manager makes the step read **No recipient**, then **Skipped** once its time passes; a relationship group of **Employees without a manager** finds everyone affected; see [Fix a missing manager, time zone or email](https://support.pyn.ai/directory/employees/fix-missing-details/).

## Check it worked

Under [Enrollments](https://support.pyn.ai/activity/enrollments/), each manager step lists the resolved manager by name, and a delivered step shows its reminders and escalation beneath it as **Scheduled**. Open **Activity** > **Actions** under **Messages**, filter **Status** to **Unactioned** and select **Export Data** for the CSV to chase from; see [Track actions](https://support.pyn.ai/activity/actions/track-actions/). A manager's own **Activity** tab lists the same asks under **Outstanding**; see [Read an employee profile](https://support.pyn.ai/directory/employees/read-an-employee-profile/).

## Related

- [What nudges and escalations look like](https://support.pyn.ai/for-employees/for-managers/what-nudges-and-escalations-look-like/) for what the manager and their skip-level receive.
- [Track actions](https://support.pyn.ai/activity/actions/track-actions/) for the Unactioned filter and the export.
- [Reach new starters before day one](https://support.pyn.ai/use-cases/pre-boarding/) for the pre-boarding automation the equipment ask belongs in.
- [Onboard from the first day to six months](https://support.pyn.ai/use-cases/onboarding-to-six-months/) for the day-one and 30-day steps.
