Skip to main content
A cohort program groups people who start around the same time. Its tracks can run once for the cohort or separately for each person. Cohorts must be enabled for your workspace, and you need a cohort program first.

Attach a track to a cohort program

Create a track from the cohort program’s page, or choose a cohort trigger on a draft track. Select the program and run mode. You need editor or admin access to that program. A program can have one active broadcast track and multiple per-person tracks. You can prepare replacement drafts while the current track runs. Once a cohort track is active or paused, its program is locked. Create another track to use a different program. The track type is fixed at creation.

Start from an existing track

Choose Import an existing track from the program to copy an available track into a new draft. The original is unchanged. Review any steps flagged as incompatible with the chosen mode before activating.

When per-person tracks start

Day 1 follows the cohort’s start date, using the program’s start time in each person’s time zone. Members already in the cohort wait until it opens. Late joiners start on a later delivery day and run the sequence from the beginning. A person whose employment start date is still in the future waits until that date before receiving steps or a channel invitation. Catch-up settings control steps already due when an enrollment starts.

Where steps go

A cohort broadcast can post to the cohort channel, another channel, channel members by DM, groups or specific people. It supports the same step types as other broadcasts. A per-person cohort track sends to its participant, manager, mentor or other supported destinations. It doesn’t post to the cohort channel. To post to the cohort channel, the program must create or link a channel. The builder flags a mismatch before publishing. Use {{cohortChannel}}, {{cohortMembers}} and {{cohortFacilitators}} in messages to reference the cohort. See Placeholders.

Replace or edit a cohort track

Pause the current broadcast track before activating a replacement. Existing cohorts finish on the paused track; new cohorts use the replacement. Archiving cancels active runs. Published edits can affect steps not yet sent in running cohorts. Duplicate the track if they should finish the existing version.