Skip to main content
Step and Section Dependence

A Guide to Step/Section Dependency and logic.

Updated this week

Dependency is used to require the specified step(s) or section(s) to be completed prior to unlocking or entering information on the current step or section.

We currently support:

  • Step level step dependency

  • Step level section dependency

  • Section Level section dependency

Step Level Dependencies

If there are no content blocks added to a step yet, there will be a + Add Content button.

If there are already content blocks existing in a step, hover over a content block and click the + icon to the left of the block.

Select Dependencies at the bottom of the list.

Select the step or section in the drop down that you want the current step to be dependent on.

Section Level Dependencies

To add a Section dependency, click the + next to the section title and select Add Section Dependencies.

Dependency Logic

Dependencies can be added using AND/OR logic.

Adding two or more dependencies into the same block sets OR logic so the dependency is met if ANY 1 requirement per block is satisfied.

Each individual dependency block must be satisfied to unlock the step - multiple blocks use AND logic.

Ex: This step can not be unlocked until C1 AND either B1 OR D1 is completed.

ALERT! Be careful when setting up too many dependencies as you can over constrain your procedure.

Once added, click the eye icon to enter Preview mode.

In the above example, Step 1.4 will be locked until Step 1.3 is signed off. Step 2.1 will be locked until all of Section 1 is signed off.

Once the necessary requirements are met, the step will be unlocked.

Dependence is similar to Conditionals without affecting the flow of the run. Check out our article on Conditionals for more info.

Did this answer your question?