A task dependency is a rule that one task cannot start or finish until another task has started or finished. On a Gantt chart it is the arrow between two bars. Dependencies are what turn a list of tasks with dates into a schedule: change one duration and every task linked after it moves.
There are four types, named after which end of each task the link connects. Finish-to-start is by far the one you will use most; the other three exist for work that overlaps. Each can also carry lag (a wait) or lead (an overlap), which is how you model things like concrete curing or starting to write before the research is finished.
Worked example: a short report
Eight tasks linked finish-to-start. Each task starts when the latest of the tasks it waits for has finished; the print approval is a milestone.
| Task | Days | Waits for | Starts | Ends | Slack |
|---|---|---|---|---|---|
| A. Collect data | 5 | — | Day 1 | Day 5 | 0 (critical) |
| B. Analyse data | 4 | A | Day 6 | Day 9 | 0 (critical) |
| C. Write draft | 6 | B | Day 10 | Day 15 | 0 (critical) |
| D. Design charts | 3 | B | Day 10 | Day 12 | 6 days |
| E. Edit and fact-check | 3 | C | Day 16 | Day 18 | 0 (critical) |
| F. Layout | 4 | D, E | Day 19 | Day 22 | 0 (critical) |
| G. Print approval (milestone) | 0 | F | Day 22 | Day 22 | 0 (critical) |
| H. Print and distribute | 3 | G | Day 23 | Day 25 | 0 (critical) |
The project finishes on day 25. Critical path: A → B → C → E → F → G → H.
Charts (D) have six days of slack because layout also waits for the edited text. Now change one link: if writing (C) starts two days after analysis (B) starts, a start-to-start link with 2 days of lag, writing begins on day 8 instead of day 10 and the report is out on day 23 instead of day 25. That is the kind of decision dependency types exist for: the work is the same, only the overlap changes.
Opens with the same links and parallel paths as above, and no account.
The four dependency types
In every case A is the predecessor and B the successor. Read the type as "A's end, B's end": finish-to-start joins the end of A to the start of B. Start-to-finish is rarely needed; most plans that seem to need it read more clearly as a finish-to-start link pointing the other way.
| Type | Rule | Example |
|---|---|---|
| Finish-to-start (FS) | B cannot start until A finishes | Pour the foundation (A), then frame the walls (B) |
| Start-to-start (SS) | B cannot start until A starts | Start editing chapters (B) once writing has started (A), usually with lag |
| Finish-to-finish (FF) | B cannot finish until A finishes | Testing (B) cannot finish until development (A) has finished |
| Start-to-finish (SF) | B cannot finish until A starts | The old shift (B) cannot end until the new shift (A) has started |
Lead and lag
Lag is a wait added to a link. Finish-to-start with 3 days of lag means B starts three days after A finishes, which is how to show a wait nobody is working on, such as paint drying, a review turnaround or a delivery. Putting the wait on the link instead of stretching task A keeps A's duration honest.
Lead is negative lag: B starts before A finishes. Finish-to-start with 2 days of lead lets the next task begin two days before the first one ends. Lead and lag can be used with any of the four types; the most common pairing is start-to-start with lag, for work that follows a few days behind other work.
FS, lag 0: B starts = A finish
FS, lag +3: B starts = A finish + 3 days
FS, lag -2: B starts = A finish - 2 days (lead)
SS, lag +2: B starts = A start + 2 days
FF, lag 0: B finishes no earlier than A finishesMandatory, discretionary and external dependencies
Separately from the four types, it helps to note why a link exists. A mandatory dependency comes from the work itself: you cannot test code that has not been written. A discretionary dependency is a choice, such as finishing design before starting build to avoid rework; it can be changed if the schedule needs it. An external dependency is on someone outside the team: a permit, a supplier, a client approval.
When a plan is too long, discretionary links are the first ones to question, because they are the only ones you can change without changing the work. External links are the ones to chase early and to track as their own tasks, so the wait is visible.
Setting dependencies in gantt-chart.io
In the editor, drag from the end of one bar to the start of another to create a finish-to-start link. Dragging start to start makes a start-to-start link, end to end makes finish-to-finish, and start to end makes start-to-finish. A link that would create a loop is refused.
Click an arrow to open its settings: change the type, or set the lag in whole days, from 30 days of lead (-30) to 90 days of lag. The arrow is redrawn from the right ends of the two bars, and the link is saved with the plan. Templates and the worked example on this page open with finish-to-start links, which you can change the same way.
Frequently asked questions
- What is a finish-to-start dependency?
- It is a link where the second task cannot start until the first has finished. It is the default and most common type: pour the foundation, then frame the walls.
- What are the four types of task dependencies?
- Finish-to-start (B starts after A finishes), start-to-start (B starts after A starts), finish-to-finish (B finishes after A finishes) and start-to-finish (B finishes after A starts).
- What is the difference between lead and lag?
- Lag adds a wait to a link, so the successor starts later. Lead is negative lag, so the successor starts before the predecessor has finished. Both can be used with any dependency type.
- Which dependency type is used least?
- Start-to-finish. It fits handovers such as shift changes, but most plans express the same idea more clearly as a finish-to-start link in the other direction.
- How do dependencies relate to the critical path?
- The critical path is the longest chain of linked tasks from start to finish. Without dependencies there is no chain, so the links you set decide which tasks are critical and how much slack the others have.
Sources
Related
Try it on your own plan
Paste a task list on the homepage and get a live Gantt chart with dependencies and a critical path. No account needed to try.