Does have dependencies?

To answer briefly, all of our boards, groups, and pulses are independent of one another, so when one of those elements is changed, it won't affect another. We did this in order to encourage communication and collaboration amongst team members so that the workflow is more efficient. Sometimes when changes are automatic, tasks slip through the cracks, and we don't want that to happen for you and your team!

That being said, we do still have some ways that you can represent dependencies in the platform while encouraging your team to interact with one another:

High Level Board

One workaround for setting up dependent tasks is to use a High Level Board structure, like the one shown here:


In that example above, there are three status columns next to one another, and each one represents the phases of a project or task. Each phase needs to be completed in order, from left to right.

You can learn more about setting up a High Level board here. 

Grouping by Phase

Another way to construct task dependencies is by using the groups on your board to represent the phases of the project. Each group will contain multiple pulses, which are the tasks you need to complete for each phase. Here is an example of what that would look like for the phases of a project that starts with the "Design" phase and ends with the "Assembly" phase:

You can set up a board with a similar structure by using the “Project Plan” featured template. You can find more information about using our templates here.

*NEW* In addition to this, you can use the new Formula column to set up an IF formula so that the status column will automatically affect the result in the Formula column. Here is an example formula you could use: IF({Status}="Done","start phase 2","still working on phase 1")

The result would look like this:

You can read more about setting up a formula like this through this article under "Get a value based on several conditions." The full list of formulas can be found here

Communicating about Next Steps

As for the communication aspect of dependencies, team members can send notifications to one another whenever they complete a step so that the next person can start the next phase.

Here is an example:

When a user changes the status of task A to "done," they can leave a note in that status and @mention the next person in line to start task B.

@mentioning a team member


Fig1. - View of @ mentioning team member from Status label.

You can also @mention the pulse or "Task B" in the status note and say that this task can now be started.

@mention pulse/board


Fig1. - View of @ mentioning a task from a Status label.

Here is more information about leaving comments in a status label.

By using these methods, you and your team members will be in sync with one another, and it will be easy to stay on the same page!

By the way, have you checked out yet?
Here you'll find real stories of our users through a variety of industries, explaining how helps them set their goals and improve their teamwork.

What do you think about these solutions for representing dependencies within

 Tip: We might implement dependencies in the future. For that, we need your help! Write to us at and let us know which type of dependencies you'd like to see.


Please feel free to reach out to our Customer Success team with any questions or comments. Your feedback is important to us! :)