A big advantage of using Rindle is that tasks can be created on-demand through automations, at specified steps in a process. Many times the creation of a task or sub task is dependent on another task, or tasks, being completed or the completion of one or more custom fields.

We call this stairstepping. It’s very similar to task dependencies without all of the complicated planning. It’s driven strictly by Automation Rules.

Think about it like a staircase...

Task #1

Task #2

Task #3

Task #4

When Task #1 is completed, create Task #2 and so on.

It can also look like this...

Example 2:

Task #1

Task #2

Task #3

Task #4

When Task #1 is completed, create Task #2 and Task #3. When Task #2 and Task #3 are complete, create Task #4.

For Example 1 above, create a new Rule that applies to Tasks.

Your trigger, condition, and action will look like this:

The above rule says:

When you mark the Sub Task complete, with the title Task #1, create a new sub task named Task #2.

It’s important to note that Perform Action On for the Action is set to Parent. Since your marking a sub task complete, you typically want to create the next sub task at the same level (the parent).

Learn more about Perform Action On

For Example 2 above, create a new Rule that applies to Tasks.

Your trigger, condition, and action will look like this:

The above rule says:

When you mark the Sub Task complete, with the title Task #1, create two new sub tasks named Task #2 and Task #3.

For the next stair step, you’ll need to create a new Rule that also applies to Tasks.

Your trigger, condition, and action will look like this:

The above rule says:

When Sub Task #2 and Sub Task #3 are marked complete, create a new sub task named Task #4.

It’s important to note that Perform Action On for the Action is set to Parent. Since your marking a sub task complete, you typically want to create the next sub task at the same level.

Learn more about Perform Action On