---
title: Handle late enrollments
description: Decide what happens when someone is enrolled after one or more steps were already due, whether by sending them at once, skipping them or reviewing them by hand.
sidebar:
  order: 2
area: flows
feature: automations
appPath: /flows/home
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
related:
  - flows/automations/manually-enroll-employees
  - flows/automations/move-an-enrollment-to-a-new-start-date
  - flows/steps
intercom:
  - id: "16729160"
    title: Handling late enrollments (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16729160-handling-late-enrollments-pyn-2
    note: replaces
  - id: "6024091"
    title: "Does an employee still receive an automated Pyn if they're added to the HRIS after the messages were scheduled to go out?"
    url: https://intercom.help/pyn/en/articles/6024091-does-an-employee-still-receive-an-automated-pyn-if-they-re-added-to-the-hris-after-the-messages-were-scheduled-to-go-out
    note: "Pyn 1 article, kept for reference"
---

A late enrollment is one created after some of its steps were already due. It happens most often in pre-boarding, when a new hire's record reaches your HRIS a few days before they start, and with backdated promotions, transfers entered after the fact and manual enrollments that catch people the trigger missed. Pyn gives you three ways to handle it.

## An example

A pre-boarding flow has three messages:

| Message | Timing | Matters if late? |
| --- | --- | --- |
| Welcome and paperwork | 14 days before start date | Yes |
| Countdown and what to bring | 7 days before start date | No |
| Your first day plan | 2 days before start date | Yes |

Someone is enrolled 5 days before their start date. The first two messages are overdue; the third is still ahead.

## Option 1: send the overdue steps at once (default)

A step whose scheduled time has passed when the enrollment is created is scheduled immediately and sends on the next delivery pass. In the example, the welcome and the countdown both go out within minutes of the enrollment, and the first-day plan sends two days before start as planned. Use this when every message is still useful on arrival.

## Option 2: skip steps that are overdue at enrollment

On a step, open the **Advanced** tab and turn on **Skip if overdue at enrollment**. Such a step is created as complete, without sending, whenever the enrollment is created after its scheduled time. In the example, turning it on for the countdown means the welcome sends immediately, the countdown is skipped and the first-day plan sends on schedule.

1. In Pyn, open **Flows** in the left navigation, then **Automations**, and select the automation.

2. Select the step card, then the **Advanced** tab in the drawer.

3. Turn on **Skip if overdue at enrollment**.

4. Select **Publish**. The setting applies to enrollments created from now on; existing enrollments keep their steps.

For a step scheduled in the recipient's time zone, Pyn resolves every recipient and skips the step only once all of their delivery times have passed.

## Option 3: decide per person with Verify Mode

Enrol the person yourself with **Verify Mode** on, as described in [Manually enroll employees](https://support.pynhq.com/flows/automations/manually-enroll-employees/). The enrollment waits in **Activity** > **Needs Review**. Open it and select **Verify**; the dialog **Select messages to unpause** lists every step with its recipients and scheduled date. Untick the ones you do not want, then select **Unpause**. Overdue steps you leave ticked send straight away; the rest keep their dates.

> **Tip:** Options 1 and 2 are rules that apply to every enrollment in the flow. Option 3 is for the one-off case where you would rather look at the list yourself.

## What you should see

Under [Enrollments](https://support.pynhq.com/activity/enrollments/), a skipped step shows as complete with no delivery, an overdue step sent at once shows a delivered date close to the enrollment time, and a paused enrollment sits in **Needs Review** until you unpause it.

## Related

- [Manually enroll employees](https://support.pynhq.com/flows/automations/manually-enroll-employees/) for Verify Mode.
- [Move an enrollment to a new start date](https://support.pynhq.com/flows/automations/move-an-enrollment-to-a-new-start-date/) for the start-date-changed case.
- [Steps and messages](https://support.pynhq.com/flows/steps/) for the rest of a step's Advanced tab.

## Related Intercom articles

- [Handling late enrollments (Pyn 2)](https://intercom.help/pyn/en/articles/16729160-handling-late-enrollments-pyn-2) — replaces
- [Does an employee still receive an automated Pyn if they're added to the HRIS after the messages were scheduled to go out?](https://intercom.help/pyn/en/articles/6024091-does-an-employee-still-receive-an-automated-pyn-if-they-re-added-to-the-hris-after-the-messages-were-scheduled-to-go-out) — Pyn 1 article, kept for reference