This article is designed to guide intermediate to advanced Qualee clients on how to operate and configure Concurrent Journeys in Qualee.
It is highly recommended that you are familiar with Journeys & Journey sequences before you proceed to reading this article.
Completing tasks at the same time creates real value in the workplace. In onboarding, for example, a new hire can work on their steps—like reading policies or setting up accounts, while the manager prepares resources, plans introductions, or assigns a buddy. Neither has to wait, so things move faster, productivity stays high, and both feel ownership of the process.
This approach keeps everyone aligned without creating bottlenecks. It saves time, smooths the experience, and helps the organization stay agile.
Statement: Concurrent work means employees and managers move forward together, faster, more efficiently, and with shared accountability for success.
IIn Qualee, this is made possible through Concurrent Journeys & Assignments.
Concurrent Journeys let you design a sequence of Journeys and assign them to different individuals (e.g., Employee, Manager, Buddy), allowing each to complete their tasks simultaneously without relying on others.
Journey Assignments give you the flexibility to assign a specific Journey within a sequence to either an individual or a group.
To create and Assign Concurrent Journeys
Log in to your Qualee Console
Navigate to Journey Sequences
Create a Sequence of Journeys by selecting and adding Single Journeys accordingly.
In each Single Journey, assign them accordingly using any of the following;
Individual name look up e.g. John Doe
Segment type e.g. Gender, Department, Location etc.
Segment value e.g. Male, Human Resources, Singapore etc.
Personalized Tokens e.g. {manager.name}, {buddy} etc.
Hint: By default, the Assigned to field automatically assigns the Single Journey to the Journey sequence invitee. When added with values e.g. Segment, Segment type, Token or Individual names, default assignment is overwritten.
Enable Concurrent Journey Completion toggle
Click Save to apply configuration then publish the Journey Sequence.
Hint: Personalized tokens use employee records to link people. For example, if John Doe’s manager is Steve Perry and the token {manager.name} is used, Steve Perry will be invited to complete the part of the Journey sequence assigned to that token.
When a Journey sequence is assigned to multiple employees, Steve Perry will receive the same Journey invitation for each of his subordinates, meaning he may need to complete it multiple times.
On the other hand, when inviting a group or segment, multiple individuals receive the same Journey assignment. For example, assigning a “Welcome the New Hire” Journey to John Doe’s entire team will invite all teammates to complete the Journey of welcoming him.