Skip to content
Task Dependencies

Task Dependencies Built for
Complex Project Sequencing

Link tasks with 4 dependency types. Circular detection, a ReactFlow graph, cascade reschedule skipping weekends, and undo.

Task Dependencies
How it works

From linking tasks to a safe, visualised dependency map in four steps

TARO handles the full dependency lifecycle: creating links, detecting conflicts, cascading changes, and rolling back.

1

Link

Four types. Every real world task relationship covered.

Most tools give you one dependency type blocks. TARO supports all four standard dependency relationships used in professional project management. Each type is set from the task detail panel in two clicks no separate editor.

2

Visualise

See the full dependency graph.Circular loops flagged immediately.

Every link renders in TARO's ReactFlow graph, a pannable, zoomable diagram with each task a node and each dependency an edge. When a circular link is created, TARO detects it, blocks the save, naming the loop.

3

Cascade

One date change cascades through every dependent task.

When a task's due date shifts, TARO automatically recalculates due dates for every downstream task in the chain, propagating the delay forward with working day awareness. A cascaded Saturday or Sunday moves forward to Monday.

4

Undo

Applied the wrong cascade? One click rolls back everything.

Every cascade reschedule generates a unique undo token a snapshot of all date changes in that operation. It expires after a configurable window (default 30 minutes). Within it, Undo restores every affected due date at once.

  • Lead created
  • Company auto created
  • Contact auto linked
  • AI score applied
  • Live table update
Why Task Dependencies

Six reasons teams never go back

One tool with four dependency types, a visual graph, circular detection, smart cascade reschedule, and a safety net without a separate app.

Four dependency types not just blocks

Four dependency types not just blocks

Finish to Start, Start to Start, Finish to Finish, and Start to Finish cover every sequencing constraint. One relationship type flattens every project. Four makes it accurate.

Circular dependencies blocked before they're saved

Circular dependencies blocked before they're saved

TARO detects circular loops the instant you create a link that would form one, before it's saved. The error names every task in the loop and rejects the link.

ReactFlow graph makes the whole chain visible

ReactFlow graph makes the whole chain visible

An interactive, pannable, zoomable graph shows every relationship as a directed edge. Critical path tasks are highlighted, completed tasks greyed, and any node opens its task.

Cascade reschedule propagates delays automatically

Cascade reschedule propagates delays automatically

One slip propagates forward through the entire dependency chain automatically. Every downstream due date is recalculated the instant the upstream changes.

Weekend skipping prevents nonsensical due dates

Weekend skipping prevents nonsensical due dates

Cascade reschedule is aware of working days. When a propagated date lands on a Saturday or Sunday, TARO moves it to the following Monday. No weekend due dates.

Token undo reverses the entire cascade in one click

Token undo reverses the entire cascade in one click

Regret a cascade? The undo token reverses every date change atomically, not field by field. Every affected task snaps back to what it was before.

Who uses it
Deepak MehrotraDeepak MehrotraDeepak MehrotraDeepak Mehrotra

800+

product teams

Built for every project where one slip cascades into many

Engineering leads, product managers, and scrum masters use Task Dependencies to make a project's chain visible before a delay becomes a missed deadline. The graph, cascade, and undo token do it.

4

Dependency types

0

Circular loops allowed

100%

Cascade skips weekends

1

Click to undo full cascade

Engineering Teams

The auth blocker moves everything downstream TARO shows exactly what and by how much.

Leads set links at planning: auth before API, API before tests. When auth slips three days, TARO cascades it through every downstream task, skips weekends, and shows the impact.

More from TARO

Dependencies are just the structure

TARO's intelligence reads your dependency graph to predict risk, surface bottlenecks, and forecast delivery.

Completion Analysis

Predicts your project's actual finish date from your dependency chain, current velocity, and known blockers. Date, variance, and confidence.

Risk Prediction

Reads your dependency graph to find blocked tasks with downstream dependents, surfacing escalations before a chain stall fails the sprint.

Bottleneck Analysis

Identifies single points of failure in the chain, where one stall blocks the most downstream work, and prescribes fixes before it costs the sprint.

Auto Prioritization

Ranks the backlog using dependency weight: tasks that unblock the most downstream work rank higher, so the most enabling work surfaces first.

Questions & answers

Everything you need to know about Task Dependencies

Common questions from engineering leads, PMs, and scrum masters evaluating TARO's dependency system.

Dependencies are created from the task detail panel. Open any task, go to the Dependencies section, and click Add dependency. Search for the task to link, select it, and choose from four types: Finish to Start, Start to Start, Finish to Finish, or Start to Finish. The relationship shows immediately in both tasks' panels the upstream shows blocks, the downstream shows depends on and the ReactFlow graph updates instantly.
When you save a new dependency link, TARO runs a graph traversal before writing to the database. Starting from the upstream node, it follows all existing edges forward. If that traversal reaches the task you're making the downstream node, the link would create a cycle, so TARO blocks the save and returns an error naming every task in the circular path. Detection is instant, so loops never reach the saved state.
A cascade reschedule triggers any time an upstream task's due date changes whether manually, by TARO's AI, or by drag and drop in the Gantt view. When the change is saved, TARO traverses the downstream chain and calculates new due dates for every task that depends on the changed task, directly or transitively. You get a preview of all proposed changes before they apply. Accept the full cascade, selected tasks, or cancel it's never silent.
When TARO calculates a cascaded due date, it checks whether the result falls on a Saturday or Sunday in the task's assigned timezone. If it does, TARO moves the date forward to the next Monday. This runs on every downstream task in the cascade. The preview shows which dates were weekend-adjusted with a note. Teams on non standard work weeks (e.g. Sunday to Thursday) can configure their working week in settings.
The default undo window is 30 minutes from when the cascade was applied, shown in the undo banner. Admins can adjust it between 5 minutes and 2 hours. After the token expires, the changes are permanent and can't be reversed with one undo; you'd edit each date manually. Each cascade generates one token. If you apply a second cascade before undoing the first, the first is retired and only the most recent is undoable.
Yes, TARO supports cross-project dependencies within the same workspace. A task in Project A can depend on one in Project B, and the link shows in both tasks' panels and in the ReactFlow graph for either project. Cascade reschedule works across project boundaries: if an upstream task in Project A slips, the cascade propagates to downstream tasks in Project B. Circular detection also spans the full workspace graph.
Taro · AI project management

Taro plans, tracks, and flags risks before they hit.

Keep every project on track with AI that spots slippage early and tells your team what to do next.

87%
on-time delivery
2.4x
team throughput
0
deadlines missed
35%
fewer status meetings
Worksbuddy© 2026 Worksbuddy