Know what a delay actually affects
A task list tells you when work is due. It does not tell you that six other tasks quietly assume that date holds. The Impact Matrix makes those assumptions visible, task by task, across the whole dependency network.
Every task, with its complete downstream chain
For each task, Depentra walks the dependency graph and collects the full transitive set of everything downstream: not just the tasks that link to it directly, but everything those tasks feed, and so on to the end of the chain. A task with two direct dependents that each feed four more is reported as affecting ten tasks, because that is what it affects.
The walk is iterative rather than recursive and stops at anything already collected, so it terminates on a deep chain and on a malformed graph alike. A dependency loop introduced by an import cannot hang the page or silently drop the looping tasks from the view.
Cascade risk, scored automatically
Counting downstream tasks by hand across a few hundred rows is not a thing anyone does twice. Depentra scores it instead. Three or more downstream tasks is CRITICAL. One or two is MODERATE. None is ISOLATED.
The score comes with the recommended action attached: protect a CRITICAL task because any slip cascades to a named number of tasks, monitor a MODERATE one, manage an ISOLATED one within its own delivery group. The point is triage. Not every slip deserves the same alarm, and the matrix tells you which ones do.
Root cause, traced back up the chain
When a task moves, the obvious question is which upstream task pushed it. Depentra records the responsible predecessor as it propagates each delay, then walks that trail back up the network to produce the causal chain in plain language.
That turns "the integration task moved three weeks" into "the integration task moved three weeks because the vendor API delivery slipped, which pushed the data mapping, which pushed integration", the version you can actually take into a status meeting.
Dependency Impact Matrix
See the full transitive downstream chain for every task, scored by cascade risk. Know what a slip actually affects before you accept it.
Related capabilities
Delay Simulator
Model a hypothetical delay across your whole roadmap without touching the live plan. See the cascade, the moved milestones, and the new end date before you commit.
Total Float and Slip
Total float for every task, recalculated whenever a date, duration, dependency, or delay changes, as a property you can add, filter and sort like any other.
See it on your own roadmap
Start from a template or import what you have, link the dependencies, and the analysis runs itself.