Draft · not indexed。 Part of what this page describes is not generally available yet.
Peak One · Product · Planned
One task slips by three days. What does that do to the whole project?
A scenario simulator for projects is planned. On this page you delay a task in a sample project and see how end date and critical path move.
What happens if …?
Sample data · nothing is savedGo-live stays at day 24
Critical path: Concept → Design → Build → Go-live。
Interactive demo with invented sample data. No account, nothing is saved or sent.
How it works
Consequences before the decision
Before you agree to a delay, you see which other tasks move with it.
Critical path in view
The demo marks the chain of tasks that sets the end date. Delays outside it often do no harm.
Built on dependencies
Dependencies and the critical path exist today in the Work V2 beta. The simulator is meant to build on them.
Nothing changes unasked
A scenario is a thought experiment. The real plan stays until you change it yourself.
All pages in this area
Honest limits
Planned, not available
The project scenario simulator does not exist in Peak One yet.
Demo runs in your browser
Six invented tasks, fixed rules, no AI. Nothing is saved or sent.
Not Peak Command
Scenarios in Peak Command are about the company, not the timeline of a single project.
Frequently asked questions
Is the simulator available?
No, it is planned. Dependencies and the critical path already exist in the Work V2 beta.
Where does the demo data come from?
From an invented project with six tasks, fixed in the browser.
Does a scenario change my plan?
No. A scenario only shows consequences. You change the plan yourself.
Know the impact before you commit.
Delay a task in the demo, then start with your own timeline for free.
Start for free