Before
Project completion: Mon 12:00
- PreparationMon 09:00–Mon 11:00
- ReviewMon 11:00–Mon 12:00
Planning / Dependencies
A dependency says that work must wait for other work to finish. Can You Just combines those prerequisites with calendars, capacity and priorities when calculating the forecast.
Understand the model ↓See the worked example →A stage dependency releases work after its specific prerequisite stage finishes. It can link stages in different projects. Later stages elsewhere in the prerequisite’s project do not silently become part of that handoff.
A project-level dependency waits for all required work in the prerequisite project. Adding another required stage can move that boundary without anyone editing the dependency.
Stage prerequisites and project prerequisites work together. Circular dependencies are rejected; a blocked or unforecastable prerequisite is shown as a constraint rather than assigned a fictional finish.
Alice’s preparation is delayed by an urgent request. Ben’s review waits for her preparation, then uses the next available time in his calendar. His estimate and assignment have not changed, but his forecast has.
A higher priority does not let Ben review work that is not ready. The timeline and forecast explanations help trace the release point.
A FICTIONAL SCHEDULING STORY
Alice prepares the work from 09:00 to 11:00. Ben reviews it from 11:00 to noon.
Alice takes a committed one-hour export fix at 10:00. Ben’s calendar, estimate and assignment stay unchanged.
Project completion: Mon 12:00
Project completion: Mon 13:00
Example assumptions. Monday 19 October 2026. Both people work 09:00–18:00 without breaks in this isolated example. One explicit stage dependency connects preparation to review.
THE CONSEQUENCE
Preparation finishes at noon. The finish-to-start dependency prevents Ben reviewing it at 11:00.
THE REVISED PLAN
Ben reviews from 12:00 to 13:00. His work moved because its prerequisite moved, not because someone edited his task.