Journey Sequencing

How to create Journey Sequences based on an employee's start date

Angelo Gargarutea avatar
Written by Angelo Gargarutea
Updated over a week ago

This article is designed for existing Qualee clients.

We highly recommend that you read the following articles before you proceed.

Now that you've read the articles above, let's review a use case for Journey Sequencing and how to achieve it using Step scheduling.

Depending on your preference, you have the full control on how and when you want Journeys and its steps to be made available to your employees.


Journey Deployment Options

I. Creating multiple-step journeys with scheduled step availability that remain viable for extended periods of time. eg, Journey A (Steps 1>2>3>4>5>6>7......>X).

II. Creating multiple journeys and deploying them individually/manually as soon as they are notified that an employee has completed a prior journey. eg, Manually assign Journey A, then manually assign Journey B.

III. Deploying multiple journeys (with all journey first steps configured to be available x days after an employee start date) at once and let Qualee do its magic. eg, Manually assign Journey A, auto-assigned Journey B, auto-assigned Journey C.

If you are one of the many clients who prefer III., then this article is the right one for you.

Here's a sample scenario:
According to your Employee Onboarding Structure, new employees are required to understand the journey structure and complete them within a 6 month period. Therefore, you will be deploying all 6 month's journeys at once which will make it visible to your employee's app dashboard.


Now, what you do not want to happen is for employees to complete all journeys deployed on their first day/week at work, as you have designed a 6 month journey that is meant to automatically run on its own and sustain the employee's engagement over that period of time.

Sample Journey Sequence Structure:

  1. Preboarding Journey (3 steps)
    5 days before start date

  2. Day 1 Onboarding (5 steps)
    On start date

  3. Week 1 Milestone (2 steps)
    7 days after start date

  4. Products and Services Overview (4 steps)
    14 days after start date

  5. 3 months review (3 steps)
    90 days after start date

  6. 6 months review (4 steps)
    180 days after start date

With the scenario above can be easily configured by following this method:

Preview - Day 1 Onboarding (Journey editor)

In the screenshot above, the Availability for the first step of Day 1 Onboarding Journey is configured to be Available Immediately. This means as soon as employee logs in, whether it's their start date or not, they can start completing this journey down to the last step as long as all steps are all set to Available Immediately.

Now, the next journey is a Week 1 Milestone, which you only want to be made available as soon as an employee reaches their 7th day at work.

Preview - Week 1 Milestone (Journey editor)

In the screenshot above, the "First step" is the most critical step to make a Journey sequence, because you are controlling a Journey's availability based on when that first step will be made available.

Going back to the screenshot above, step "Day 7" is made to be available only 7 days after start date. Therefore, if an employee attempts to complete the Week 7 Milestone Journey on their first day at work, they will see a similar message on their Qualee App:

Preview Week 1 Milestone (Employee app)

This method is repetitive, and not limited to preboarding and onboarding. Regardless of if you wish to deploy 10 onboarding journeys within a 6 month period, or 20 micro-learning journeys for the entire year, as long as the first step availability is configured accordingly, you will have the full control on your employees' experience.

Did this answer your question?