This article is part of a series on scheduling Workflows:

It is strongly recommended to read these in order, as they build in complexity, and later articles refer back to earlier ones.

Click below to jump to the relevant section:

Within a Workflow Template, the easiest way to schedule when steps happen is by using the timings in the step details. For example, do the kick-off call on day 2, and hold the first set-up meeting on day 7.

You can combine step timings with dependencies and conditions (described in later articles in this series), but firstly, here in this article we'll look at simple timings by themselves. The number of days specified starts counting when the Workflow Template is applied to a record (e.g. a Company or End User).

This is what simple timings for email steps in a Sequence Workflow Template can look like:

Click on the image to view it enlarged

Considering task steps in a Project Workflow Template, simple step timings look like this:

When a Workflow Template is applied to a specific Company or End User etc. and the steps are activated, the actual dates are filled in - so if we take the Project example we just saw:

As you can see:

The date that the Workflow Template is applied (e.g. to a Company) is counted as day 0.

Our Step 1 in this example has "Start After Days" set to 1. If we apply this Workflow Template to a Company on April 30, the "Start Date" will be May 1 (as in, 1 day after April 30). As the "Duration Days" is 0, the "Due Date" is the same as the "Start Date".

Step 2 here has "Start After Days" set as 5 and "Duration Days" as 2, so when the Workflow Template is applied on April 30, the "Start Date" of this task is May 5 (April 30 + 5) and its "Due Date" is May 7 (May 5 + 2).

To read more about Task "Start Date" and "Due Date", you can refer to our separate article here.

Your Workflow will consist of multiple steps (actions), but you typically don't want all the steps to happen at once. Setting step timings is a really simple way for you to control when actions occur.

For example, perhaps you're creating an onboarding Project, which includes a series of meetings with a Company scheduled over several weeks; or maybe you're re-engaging with low adoption End Users via an email "drip campaign" Sequence, where you want to send emails spaced out every few days.

By specifying on each step what the timings should be, you can very easily state in a Project that you want the first training session to be 7 days after the Workflow Template is applied, and the next training session should be 14 days after the Workflow Template is applied. Or if you're sending a series of emails in a Sequence to inform new End Users about various features of your product, you can set the first email to be sent as soon as possible after the Workflow Template is applied, and then the next email to be sent 2 days after it's applied, and so on.

Here we've talked through some simple examples, but in other cases, you might want a step to occur a certain number of days after the previous step happened (e.g. sending an automated follow-up email after a meeting takes place) or after a rule-based condition has been met (e.g. emailing instructions of next steps only after the End User has taken a specific action such as logging in) - you can do this by combining step timings with dependencies and rule-based conditions, which we'll discuss later in this article series.

You set these timings in the step details (and/or in the steps table when looking at the overall Workflow Template), and the options vary slightly depending on whether it's a task step or an email step.

Now you know all about simple step timings, let's add in the next layer of complexity: step dependencies.