You can enable the ASAP mode for strong dependencies - the scheduling mechanism will try to reduce the gap between dependent tasks to a minimum. When you set this toggle-switch to active, the App remembers the settings and all future dependencies are created in the ASAP mode.

The Source task date rules the Target task date. It's a uni-directional relationship.


There are four possible ways to connect tasks:

  • End to start - end date of a task dictates the ASAP start of a target task.

     Click here to expand...

    In the example below, you can see that the App takes into account non-working days.

  • start to end - a start date of a task dictates the ASAP end of another task. 

     Click here to expand...

  • end to end - end date of a task dictates the ASAP end date of a target task. 

     Click here to expand...

  • start to start - start date of a task dictates the ASAP start date of a target task. 

     Click here to expand...

The direction of the dependency is based on how you create a dependency (the direction of an arrow when connecting tasks).

In other words - dependency in ASAP mode always schedules target task as soon as possible based on dependency type. There are no restrictions on how many dependencies are created for each source or target task as long as they are not crating circular relationship. If a task is moved to a prohibited position (based on dependency type and mode) it is moved back/forward to the appropriate position.

To enable the ASAP mode, click on one of the dependencies:


Creating a dependency can re-adjust the task period, but deleting a dependency will not move tasks on the timeline.

Dependency Color

The dependencies with ASAP mode enabled are colored black.

Dependency Lag Time

It is possible to add lag time to an ASAP mode dependency. The system will add a delay equal to the specified number of days. 

Non-working days are included in the calculation. 

The Lag time is the minimum time between the tasks, but if you set a 3 day lag time and a task ends on Wednesday, effectively, the gap will last 4 days (Saturday is counted as the 3rd day, but it is not possible for the next task to start on Sunday).


ASAP "on" vs "off"

When the ASAP mode is activated, there is only one possible position for the target date. 

In the example below (no lag time), end date of PP-326 dictates the start date of PP-332. The target start date can't be manually overridden - it will always be the next possible day after the source end date. 

When the ASAP mode is "off" the target task cannot start before the source end date, but it can start at any point after it. There is more than one possible start date for the PP-332 task (any date after August 6th will work).