With many processes there are cases where a deadline or timescale is necessary. There are two different ways to set this up in beSlick: 

At the Template stage

When you create a Template, you can set an overall due date for how long any Tasks should take by default. As an example, a complaints Template might have an SLA of 7 days for it to be responded to.

You can select whether any Tasks should be done immediately, or in a specific number of days, working days, weeks or months. For example, on the Template you could set the overall due date for any Tasks created from it to be 3 weeks after the Task has been started.

Note: When you create a Task, the suggested default can still be changed if needed.


Within each Template you also have Steps, and these can also have due dates that are dependent on different things (and of course be assigned to different people or Groups).

The five dependent due date options for Steps are;

  1. After task start date

  2. Before task is due

  3. On task due date

  4. After task is due

  5. After step

'Before task is due' lets you set the due date in relation to when the task itself is due. You may want to use this for steps towards the end of the process, or if you like to 'work backwards' or reverse calculate from a specific date for what needs to happen before then to work out the due dates. 

Once you have selected Due you can then select When, choosing from;

  • Immediately

  • Days

  • Working days

  • Weeks

  • Months

After step lets you define the due date as being a certain amount of time after another step. For example, you could make the step 'File invoices' due 3 days after the step 'Approve invoices'. This is great for when steps should have consistent deadlines or where there are SLAs (service level agreements).

You can create a number of dependencies in this way, and Steps can also be due in parallel (even though it may look as though they have to be done in sequence).


When tasks are created from Templates with timescales on, dates are generated according to the rules set. However, the dates can be edited before publishing a Task if needed.

Employee Onboarding as an example

Here are some use cases for dependencies on each Step;

  1. The Template is due by default 2 weeks after the Task starts, and that is the anticipated start date of the employee.

  2. Before the employee starts, they need their laptop setup, so that has a due date of 5 working days before the Task due date.

  3. On the day the employee starts, they need an introduction from their manager - that Step has a default due date of immediately on Task due date.

  4. They also need a review with HR after they have started, that Step has a due date of one week after Task due date.

At the Task stage

On a task you can set exact due dates, or on steps you can also use the 'after step' due date feature on templates.

If a Task or any of its steps have due dates set, this will cause notifications to be sent out to the task or step assignee when the task is approaching its due date and when it is overdue. Read more about notifications here.


Setting a start date on a Task means that it won't appear in the task list for any user until that date has been reached. These tasks can be found by selecting the "Waiting" option in the status filter.

Did this answer your question?