---
title: "Reach new starters before day one"
description: "In the week before someone starts, send them a welcome, a first-day plan and a see-you-tomorrow note at their personal address, and give their manager a checklist, from the Pre-onboarding trigger."
sidebar:
  order: 1
area: use-cases
appPath: /flows/home
lastVerified: 2026-11-16
version: "2026-11-13"
audience: admin
related:
  - flows/automations/tutorial-pre-boarding-to-a-personal-email
  - flows/automations/configure-a-date-trigger
  - flows/automations/handle-late-enrollments
  - directory/employees/add-an-upcoming-employee
  - use-cases/buddy-programme
---

Every new starter hears from you before day one, at an address they can read, and their manager has a checklist in hand a week out. **For:** admins and owners. **Time:** about 40 minutes with the messages written.

![The finished automation: the Pre-onboarding trigger a week before the start date, three emails to the personal address and the manager's checklist, in Verification.](https://support.pyn.ai/media/use-cases/pre-boarding/use-cases-pre-boarding-automation.png)

## What you'll need

- **Personal Email Address** and **Start Date** synced from your HRIS; every supported source provides both, see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/). Open an upcoming joiner in **Directory** to check.
- An email sender: your People team's mailbox or a verified address; see [Add an email sender](https://support.pyn.ai/settings/senders/add-an-email-sender/). Slack is not an option, because nobody has a Slack account before they start.
- The manager's checklist as a web page or published content for the button to open.
- Optional: the **Pre-onboarding** template from the catalogue. It gives you the trigger; you add the steps.

## Build it

1. Create an automation with the **Pre-onboarding** trigger under **Employee Lifecycle** and leave **This flow starts** at **1 week before**, so it fires on any day from a week before through the start date; see [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/).

2. On the **Audience** tab, tick **Joiner** and **Current** under **Lifecycle**, since people before their start date are joiners, not current employees; 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 **Employee (Personal)**, scheduled **1 week before** at 09:00 in the **Recipient Time Zone**, for the welcome; see [Add an email step](https://support.pyn.ai/flows/steps/add-an-email-step/) and [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).

4. Add a first-day plan **3 days before** and a see-you-tomorrow note **the day before**, both to **Employee (Personal)**, and turn on **Skip if overdue at enrollment** on the first-day plan; see [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).

5. Add an email **1 week before** with **To** set to **Manager**, a **Link Button** with **Track Action** ticked and one reminder **2 days after send**; see [Give managers a new-hire checklist](https://support.pyn.ai/use-cases/manager-checklist-for-a-new-hire/).

6. Open **Preview**, pick an upcoming joiner under **Preview for principal** and select **Send a test to yourself**, so you see the tokens with a real start date; see [Preview and send a test](https://support.pyn.ai/flows/steps/preview-and-send-a-test/).

7. Publish, set the mode to **Verification**, unpause the first two or three joiners from **Needs Review**, then switch to **Automated**; see [Tutorial: pre-boarding to a personal email](https://support.pyn.ai/flows/automations/tutorial-pre-boarding-to-a-personal-email/).

## Variations

**Contractors.** If your HRIS supplies an employment type, add the contractor demographic group under **Excluded** on the trigger's **Audience** tab, or put the employee group under **Included**; an exclusion wins over an inclusion. A contractor who was wrongly welcomed was in the audience, so check **Audience Preview** after the change; see [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/).

**Someone not in the HRIS yet.** Add them from **Directory** > **Upcoming** with their personal email, start date and manager; the trigger enrols them from there, and Pyn merges the HRIS record when it arrives with the same work email; see [Add an upcoming employee](https://support.pyn.ai/directory/employees/add-an-upcoming-employee/).

**The moment the record appears.** For a single hello the day someone first shows up in the HRIS, use the **Will be joining** trigger; it has no offset or recurrence; see [Trigger catalogue](https://support.pyn.ai/flows/automations/trigger-catalogue/).

## Watch out for

- Without a personal address, a step to **Employee (Personal)** has no valid recipient and is marked invalid, so the person gets nothing. Open their profile's **Sources** to see which system supplies the address and fix it there; see [Fix a missing manager, time zone or email](https://support.pyn.ai/directory/employees/fix-missing-details/).
- A record that reaches Pyn less than a week before the start date enrols late, and every step already due sends at once; the first-day plan is skipped by step 4. See [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).
- A step before the start date warns "Sent before the start date but the joiner isn't in the audience" when **Joiner** is missing; without it the flow enrols nobody; see [Set the audience for an automation](https://support.pyn.ai/flows/automations/set-the-audience/).
- The trigger's **Prevent repeat enrollments** is **Never reenroll**, so a corrected start date does not re-enrol anyone; stop the enrollment and re-enrol them by hand against the new date; see [Move an enrollment to a new start date](https://support.pyn.ai/flows/automations/move-an-enrollment-to-a-new-start-date/) and [Prevent repeat enrollments](https://support.pyn.ai/flows/automations/prevent-repeat-enrollments/).
- 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

Each upcoming joiner appears under [Enrollments](https://support.pyn.ai/activity/enrollments/) with their start date as **Reference** and four steps: three to their personal address and one to their manager, named, or **No recipient** when the relation is empty. In **Verification** the enrollment waits in **Needs Review**; see [Review and unpause enrollments](https://support.pyn.ai/activity/enrollments/review-and-unpause-enrollments/). A joiner whose record arrived late shows the welcome delivered within minutes of enrollment, the first-day plan complete without a delivery, and the rest on their dates.

## Related

- [Tutorial: pre-boarding to a personal email](https://support.pyn.ai/flows/automations/tutorial-pre-boarding-to-a-personal-email/) to build the same automation step by step, with the message copy.
- [Onboard from the first day to six months](https://support.pyn.ai/use-cases/onboarding-to-six-months/) for the flow that takes over on day one, to the work address.
- [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/) for offsets and the reference date.
- [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/) for the three ways to treat overdue steps.
- [Run a buddy programme](https://support.pyn.ai/use-cases/buddy-programme/) for the buddy nomination step that sits in this automation.
