Predecessor

A predecessor is a task that must begin or finish before another task — the successor — can proceed. Predecessor relationships define the sequence network of a project schedule. Without them, a scheduler has no basis for determining task order, and critical path calculations cannot run. Every task except the first in a schedule should have at least one predecessor.

Predecessor and Successor

These terms describe the same relationship from opposite directions. If Design is the predecessor of Development — meaning Development cannot start until Design finishes — then Development is the successor of Design. A task can simultaneously be a successor to one task and a predecessor to another, forming a chain through the network.

A task with no predecessors is called a start task or open start — it can begin at any time, unconstrained by other work. A task with no successors is an end task. Most real schedules have one open start (project kick-off) and one or a few end tasks (final deliverables or milestones).

Predecessor Types

The relationship between a predecessor and its successor is defined by a dependency type:

• Finish-to-Start (FS): The predecessor must finish before the successor can start — the most common type.
• Finish-to-Finish (FF): The predecessor must finish before the successor can finish.
• Start-to-Start (SS): The predecessor must start before the successor can start.
• Start-to-Finish (SF): The predecessor must start before the successor can finish.

Lag or lead time can be added to any of these — extending the gap between the two tasks (lag) or allowing them to overlap (lead).

Predecessors and the Critical Path

The critical path is derived entirely from predecessor relationships. The scheduler traces every chain of predecessors from start to finish, identifies the longest chain by total duration, and marks those tasks as critical. Changing a predecessor link — adding one, removing one, or changing its type — can shift which tasks are critical and move the project end date.

Predecessors in Maverick

In Maverick, predecessor links are set by drawing connections between tasks in the Gantt chart or by entering them in the task properties panel. Each link appears as a dependency arrow on the Gantt chart. Maverick's AI chat can set predecessor links from plain language — "make Development depend on Design finishing" — and will cascade date changes through the network immediately.

Related Terms

Task Dependency  ·  Critical Path  ·  Float  ·  Gantt Chart  ·  Project Schedule