Conditionals allow you to control what happens next in a procedure based on defined criteria. The next action can be triggered by the completion or failure of a step, a user’s selection in a List, Custom List, or Number field, the value of a procedure variable, or the pass or fail state of a section.
When configured thoughtfully, conditional branches and step dependencies create clear, intuitive workflows. By using conditions to unlock steps or entire sections based on prior actions, inputs, or calculated values, teams can ensure procedures adapt dynamically to real-world scenarios while remaining easy to follow.
Conditionals are added like content blocks.
Conditionals based on Success / Failure
When the step is signed off, the procedure will flow to B1 and B2 requirements will remain unmet and therefore remain locked. If FAIL STEP is selected, the procedure will flow to B2 and B1 requirements will remain unmet and locked. If the step is skipped and NOT repeated, then both B1 and B2 will unlock so as not to block the procedure.
In this way, Conditionals are like Dependencies that direct the flow of the run.
As steps without signoffs can not be skipped or failed, any conditional based on step completion will only have the completion option.
Conditionals using List or Custom List field inputs
Ex: Conditionals based on List/Custom List - Set Conditionals drop down to Field Input name. (See Anatomy of a Step for more info on Lists and Custom Lists)
Select the step you want each option to flow to.
When the step is signed off, the procedure will flow to the option selected.
Conditionals using Number field inputs
Create Conditionals based on the PASS or FAIL of Number field inputs.
Pre-determine the flow of the procedure depending on if a Number that's been entered meets an expected value or falls within required parameters.
Note: A Number Rule must be added for this type of Conditional to work.
Select next steps depending on specific Fail conditions.
Using step dependency and conditionals together may result in circular references, thus rendering your steps unable to be completed as intended.
Conditionals are ideally suited for progressing to future / not previously completed steps. If navigating to a previously signed off step, the step will need to be manually repeated to input different values.
Conditionals Based on Durations
Branch a procedure based on how long a particular step takes to execute.
You will need to add Duration under Add Details at the top of the step.
Toggle on Record Duration AND add an Expected Duration in an HH:MM:SS format.
Once those are set, Expected Duration will be available in the Conditionals drop down.
Set the flow based on whether the step took more or less time than expected.
During a run, the start button must be clicked before any inputs can be entered in the step. The duration will be visible in the top right corner above the sign off. The duration will be set when the step is signed off and will flow based on the conditional selections.
Conditionals with Sections
Conditionals can use sections as part of the execution flow, allowing procedures to branch at a higher level than individual steps.
Sections can be used in two ways:
As a branching target, so conditionals can route execution to an entire section rather than a single step.
As a conditional source, where the pass or fail state of a section determines which path the procedure follows. (The entire section needs to be completed)
This makes it easier to manage complex procedures by grouping related steps and applying conditional logic based on the outcome of an entire section.
NOTE: If ANY steps in the section are marked as Failed, then the section conditional will follow the Fail condition.
If branching to a section (example remediation steps) that will eventually need to route back to the main track, the last step of the branched section will need to have a Step conditional where both the pass and fail options point back to the next step to be performed, typically the success path from the original conditional.
Conditionals Based on Variables
Conditionals can now be driven by procedure variables, providing the same logical branching options previously available with Field Input Conditionals.
This enables more flexible, data-driven workflows where decisions can be made once and referenced throughout the procedure.
Summary of Best Practices
Use conditionals to define clear pathways for branching workflows.
Establish dependencies between subsequent steps or within sections to ensure logical progression.
Ensure workflows dynamically unlock steps based on user selection and properly tailored conditions.
Test workflows thoroughly to identify and fix gaps or misconfigurations.