Simulate the delay before you accept it
A supplier asks for two more weeks. Your instinct says there is slack somewhere. Your programme board wants a number. The Delay Simulator turns instinct into that number, in about a minute.
A sandbox, not an edit
Simulated delays are held separately from the plan of record and passed into the scheduling engine as an overlay. The Gantt, the Impact Matrix, and every task's float all recompute from that overlay, so you see the full consequence, but nothing is written and nothing is saved until you decide it should be.
This matters more than it sounds. If what-if analysis happens by editing real dates and undoing them afterwards, people stop trusting the plan, because they can never be sure what they are looking at. Keeping simulation strictly separate is what keeps the plan of record meaningful.
Compound delays follow real scheduling logic
One delay is usually absorbable. The interesting case is two delays on parallel chains that converge on a shared task, and this is where hand calculation reliably goes wrong.
When multiple delayed predecessors feed one task, that task inherits the largest incoming shift, not the sum of them. Two upstream chains running three and five days late push the task they converge on by five days, not eight. Depentra applies that rule at every node as it walks the graph in topological order, so a compound scenario across hundreds of tasks resolves correctly and immediately.
What you get back
Every affected task shows how many days it moved and which upstream task caused the move. Revised start and end dates are computed alongside the planned ones rather than replacing them, so the original plan stays visible for comparison. Float is recomputed on the revised schedule, which means the tasks with no room to slip under the new scenario are not necessarily the ones that had none before.
The practical workflow: enter the requested delay, read the cascade, and decide. If the end date holds, accept it with evidence. If it does not, you have specifics to negotiate with (one week absorbable, two not) instead of a promise to come back with numbers later.
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.
Related capabilities
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.
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.