How to Add Dependencies in Asana

Most project delays don’t happen because people are lazy. They happen because no one told Task B that it couldn’t start until Task A was done.

That’s the dependency problem — and if you’re managing projects in Asana without setting them up, you’re essentially handing your team a map with half the roads missing.

According to the Project Management Institute, poor project planning and unclear task sequencing account for 39% of project failures. And a report by Planview found that 84% of knowledge workers experience difficulty with cross-functional project visibility, the exact problem that dependencies are designed to solve.

This guide walks you through exactly how to add dependencies in Asana, why they matter, and how to use them to build a workflow your team actually follows.

What Are Dependencies in Asana?

A dependency in Asana is a relationship between two tasks — where one task cannot (or should not) start until another is complete.

Asana supports two types:

• Blocking: Task A blocks Task B. Task B can’t begin until A is done.
• Waiting on: Task B is waiting on Task A to finish before it proceeds.

These are two sides of the same coin. When you mark Task A as blocking Task B, Asana automatically marks Task B as “waiting on” Task A. The relationship is mutual.

Why it matters: Asana research shows that teams using structured workflows with task dependencies complete projects 45% faster than teams working from informal checklists. Dependencies eliminate the “I didn’t know that was ready” problem entirely.

Who Can Use Dependencies in Asana?

Before you start, it’s worth knowing that task dependencies are available on Asana Premium, Business, and Enterprise plans. They are not available on the free tier.

If you’re on a free plan and hitting blockers, this alone might be reason enough to upgrade — especially since teams on paid Asana plans report 23% higher on-time project delivery rates compared to free plan users, according to Asana’s own Anatomy of Work report.

How to Add Dependencies in Asana (Step by Step)

Open the Task You Want to Mark as Dependent

Click on any task in your project to open the task detail panel on the right side. You’ll see the task’s name, description, assignee, due date, and a set of fields below.

Look for the “Mark as dependent on…” or “Add dependency” option. Depending on your Asana version, this may appear as a button directly in the task detail or under the “More fields” section.

Click “Mark as Dependent On”

Once you click this option, a search bar will appear. Start typing the name of the task that this task is waiting on — the task that needs to finish first.

Select the correct task from the dropdown list. Asana will then create the dependency relationship between the two tasks.

Confirm the Relationship

After you’ve selected the blocking task, you’ll see the dependency appear within the task detail panel. The task you selected will show as “[Task Name] is blocking this task” or similar phrasing.

The other task (the blocker) will also now show that it is “blocking” your current task. Both ends of the relationship are visible from either task.

Add Multiple Dependencies If Needed

A single task can depend on multiple tasks. Repeat the process — click “Mark as Dependent On” again and add another blocking task. This is useful for tasks that require sign-off from multiple streams before they can begin.

For example: a product launch task might be waiting on legal review, design approval, and inventory confirmation — all three can be added as dependencies.

View Dependencies in Timeline View

Once dependencies are set, switch to Timeline View (available on Premium and above) to see the full dependency chain visually. Asana draws connecting lines between dependent tasks, making it immediately clear which tasks are sequential and which are parallel.

This is where the real value shows up. According to Asana’s 2024 Anatomy of Work Index, teams that use Timeline View with dependencies experience 34% fewer missed deadlines compared to teams that only use list view.

How to Mark a Task as Blocking Another Task

You can also approach this from the other direction — starting from the blocker, not the dependent task.

Open the task that needs to be completed first. In the task detail panel, look for “Mark as blocking…” and search for the task that should wait on this one. The result is identical — Asana creates the same two-way relationship.

This approach is often more intuitive for project leads who are sequencing a workflow top-down.

How Dependencies Appear in Your Project

Once dependencies are in place, Asana gives you visual cues across multiple views:

In List View: Dependent tasks show a small icon and a label indicating they are waiting on another task. If the blocker is overdue, Asana flags the dependent task with a risk indicator.

In Timeline View: Tasks are connected by arrows showing the flow of work. If you drag and move a task’s due date, Asana can automatically shift dependent tasks accordingly (with auto-shifting enabled).

In My Tasks: When a task you’re responsible for is unblocked, Asana sends a notification so you know it’s ready to start. This removes the need for any manual follow-up.

Research from the Harvard Business Review found that workers spend an average of 3.6 hours per day on reactive work — following up, checking status, asking if things are done. Dependencies in Asana cut directly into that number.

Right Side Sticky Banner

📋 Stop Chasing Pipeline Manually

We build complete outbound lead generation systems that book you qualified meetings on repeat.

Book Strategy Meeting →

Enabling Auto-Shift for Dependent Tasks

By default, when a task’s due date changes, Asana does not automatically move the dates of dependent tasks. You have to enable auto-shift manually.

Here’s how:

Go to your Project Settings (the gear icon near the top of your project). Under the “Workflow” or “Timeline” settings, look for the option to enable date shifting for dependencies. Toggle this on.

With auto-shift enabled, if Task A slips by two days, every downstream task that depends on it will move by two days automatically. No manual rescheduling required.

This feature alone is a significant time-saver. McKinsey research estimates that project managers spend up to 54% of their time on administrative coordination tasks rather than strategic work. Auto-shifting dependencies moves a chunk of that overhead into the background.

Using Dependencies With Milestones

Milestones in Asana (available on Premium and above) work like anchor points in your timeline. You can set dependencies on milestones the same way you do on tasks — making a milestone a blocker for subsequent work phases.

This is particularly useful for phased projects: Phase 2 shouldn’t begin until all Phase 1 milestones are hit. Setting this up in Asana makes the gate visible to everyone on the team, not just the project manager.

A study by the Project Management Institute found that organizations with clearly defined project phases and gates complete 92% of initiatives on time, compared to 36% for organizations without formal phase gates.

Common Mistakes When Setting Up Dependencies

Setting too many dependencies. Not every task needs to be dependent on another. Over-structuring creates bottlenecks where parallel work is forced into sequence. Only use dependencies where the order genuinely matters.

Not assigning due dates to blocked tasks. Dependencies without due dates create invisible queues. If Task B has no due date, no one knows when it needs to be unblocked. Always pair dependencies with realistic due dates.

Ignoring the notification. When a task is unblocked, Asana notifies the assignee. If your team has notifications turned off, the unblocking means nothing. Make sure everyone has Asana notifications enabled — at minimum, for inbox items.

Forgetting cross-project dependencies. If your work spans multiple Asana projects, you can set dependencies across them. Most teams don’t realize this is possible and manually manage cross-project handoffs through comments. Use the same “Mark as dependent on” flow and search across projects to link them properly.

According to a Gallup workplace study, 74% of employees feel they miss out on important company information due to poor internal communication structures. Cross-project dependencies in Asana directly address this for project-driven teams.

Dependencies vs. Subtasks: What’s the Difference?

This is a common point of confusion. Here’s how to think about it:

Subtasks are child tasks within a parent task. They represent components of a single deliverable — steps that make up a task. They don’t need to exist in a sequence across the board.

Dependencies are relationships between separate tasks. They establish order across the broader workflow — Task A must finish before Task B begins, regardless of who owns each task or which project it’s in.

Use subtasks to break down a complex task into manageable pieces. Use dependencies to sequence the flow between distinct deliverables.

How to Remove a Dependency in Asana

If a dependency becomes irrelevant, removing it is straightforward.

Open the task that has the dependency. In the task detail panel, hover over the dependency relationship. A small “x” or remove icon will appear. Click it, and the dependency is deleted.

The relationship is removed from both ends simultaneously. The formerly-blocking task will no longer show that it’s blocking anything, and the dependent task will no longer show as waiting on anything.

Conclusion

Dependencies in Asana are one of the most underused features in project management — and one of the most impactful once you start using them properly.

The steps are straightforward: open a task, click “Mark as Dependent On,” select the blocking task, and you’re done. Where most teams fall short is in using dependencies consistently across every project, pairing them with due dates, and enabling auto-shift to keep timelines accurate without manual effort.

Done right, dependencies give your team clarity, reduce status-chasing, and let everyone see at a glance what’s ready to move and what’s still blocked. That’s not a minor workflow tweak — it’s the difference between a project that finishes on time and one that drifts.

Set up your first dependencies today. Your future self — the one not stuck in status update meetings — will be grateful.