No due date, still a deadline
The customer FAQ has no date of its own. It gates the launch, so it inherits the launch’s date and its buffer is measured against that.
Drag a bar and watch what it does to the deadline of everything downstream. Gantt and advanced scheduling come with Individual and Business; the model below is a sample you can move.
Pick any task to see what it depends on, what is waiting on it, and what one lost day does to the launch forecast. In the app, the task dialog shows the first two and the Timeline shows the third.
Prepare the fulfillment plan depends on Finalize the launch date. Waited on by Run the dress rehearsal. Delaying it delays 2 downstream tasks.
One lost day here moves the launch forecast by 1 day. It is on the critical path.
Bars are derived from the dependency graph, not drawn by hand. Drag one to pin a start date and everything downstream re-plans around it. With a bar focused, the arrow keys move it a day and Backspace clears the pin.
Sample plan in calendar days: today is Sep 7 and the launch is due Sep 22. In the app, bars are forecast from your estimates, working hours and recent velocity, and the Timeline also reports that velocity.
Buffer is the time between when a task can realistically finish and when it actually has to, measured against the deadline that truly binds it, which is often not its own.
Launch still lands by Sep 22, with 2 days to spare.
The customer FAQ has no date of its own. It gates the launch, so it inherits the launch’s date and its buffer is measured against that.
Slip one upstream task and every gap downstream narrows without anyone editing a bar. When a gap hits zero the task is critical; past zero, the plan is behind.
Forecasts there use your recorded estimates, working hours and recent velocity. Every bar opens its task, where you set what it depends on and see what is waiting on it.