✨ New feature alert
This feature is available from Thursday, 19th November 2026.
Overview
Workflow branching lets you tailor a workflow so each learner only gets the onboarding steps that apply to them. You can make any step conditional, based on a value on the learner record or an answer given in an earlier form step.
Steps that don't apply to a learner are skipped automatically and hidden from them, which makes onboarding shorter and more relevant. Staff can still see every skipped step and why it was skipped.
User Roles
This feature can be used by:
- Admin
How Conditions Work
- For each conditional step, you choose whether learners who match the condition do the step or skip it.
- A condition can be based on the learner record or on an answer in an earlier form step.
- You can add several conditions to one step. All of them must be true for the condition to be met.
| Condition based on | Examples | Good to know |
|---|---|---|
| The learner record | Programme, Funding type, Has an employer | Uses the value currently on the learner record. |
| An answer in an earlier form step | A question such as LLDD on an earlier onboarding form | There must be an approval pause between the form step and the conditional step, so everyone has finished the form before the condition is checked. |
Steps to Add a Condition to a Step
- Click Workflows from the left-hand menu.
- Click the three dots next to the draft workflow and select Edit.
- On the Workflow plan tab, open the step you want to make conditional.
- Open the Who does this step? tab.
- Choose whether learners who match the condition do this step or skip it.
- Add a condition by choosing a learner record field, or a question from an earlier form step, and the value to match.
- To add another condition, repeat the previous step. All conditions must be true.
- Save the step.

Conditional steps show a summary on the Workflow plan, such as Only if LLDD = Yes or Skipped if Funding type = Non-levy. When you collapse a stage, it shows how many steps it has and how many of them are conditional.
Preview a Learner's Path Before Publishing
Use the path preview to check your conditions behave as expected before you publish the workflow.
- On the Workflow plan tab, open the path preview.
- Enter example form answers and learner record values.
- Review which steps a learner with those details would get, and the reason each step is included or skipped.

What Happens When a Learner's Details Change
- If an earlier form answer changes, or an Admin corrects a learner record value that a condition uses, the learner's steps that haven't been started yet are checked again.
- If a step is added back, the learner is told.
- Steps that are already in progress or completed are never changed automatically. Staff see a Condition no longer met: review banner instead, so they can decide what to do.
⚠️ Important: Published workflows can't be edited. To add conditions to a live workflow, duplicate it, add the conditions to the copy and publish it.
Tips & Notes
- Always preview a few example learners before publishing, especially when a step has more than one condition.
- Learners and employers don't see skipped steps, and forms on skipped steps don't appear in task lists or send notifications.
- A learner's progress percentage only counts the steps that apply to them.
- Admins can skip or reinstate a learner's incomplete steps by hand. See View, Skip or Reinstate a Learner's Workflow Steps in Enrol Onboarding.
Terminology
The terminology used in this article may differ depending on your Centre's configuration.