Predecessors in Gantt Charts: A Clear Guide for Beginners

Planning a project can feel simple until one missed task delays everything after it. A designer waits for approved requirements. A developer waits for the design. Testing waits for a working build. Without clear task relationships, your Gantt chart becomes a collection of dates rather than a reliable project plan.

That confusion creates duplicate work, unrealistic deadlines, and surprise delays. A small change in one activity can quietly affect an entire delivery path.

But here's the truth: a predecessor gives you a clear way to show what must happen before another task can begin or finish. Once you understand predecessor relationships, you can build schedules that reflect how work actually happens.

What Is a Predecessor in a Gantt Chart?

A predecessor in a Gantt chart is a task or milestone that controls when another task can start or finish. The related task is called the successor because it follows the predecessor in the project sequence.

For example, “Approve homepage design” may be a predecessor to “Build homepage.” The build should begin only after the design receives approval. A Gantt chart usually shows this relationship with a connecting line or arrow.

Predecessors help you represent task dependencies, calculate realistic dates, and identify the work that may affect the schedule. They are especially useful when several people contribute to the same project.

Key Parts of a Predecessor Relationship

• Predecessor: The earlier task that creates a condition for another task.
• Successor: The later task affected by the predecessor.
• Dependency: The relationship connecting the two activities.
• Dependency type: The rule explaining how one activity relates to another.
• Lag or lead: Extra waiting time or permitted overlap between connected tasks.

Simple Example

Imagine you are launching a small website. You cannot publish the site before the final quality check. In this case, “Complete quality check” is the predecessor, while “Publish website” is the successor.

If the quality check moves from Tuesday to Thursday, the publishing date may also move. The predecessor makes that scheduling effect visible.

How Predecessors Work in a Project Schedule

To use predecessors correctly, connect tasks according to the work required between them. Start with the activity that must happen first, then identify what can begin afterward.

1. List the project activities. Break the project into clear tasks, such as “Write product copy,” “Review copy,” and “Publish page.”
2. Identify the required order. Ask what must happen before each task can begin or finish.
3. Choose the dependency type. Select finish-to-start, start-to-start, finish-to-finish, or start-to-finish.
4. Connect the activities. Link the predecessor to its successor in your scheduling tool.
5. Add lag or lead when needed. Include waiting periods or planned overlap instead of hiding them in task durations.
6. Review the schedule. Check whether the relationships create sensible dates and reveal possible bottlenecks.

Here's why: a task duration tells you how long work may take, while a predecessor explains when that work is allowed to happen. You need both details for a dependable schedule.

Four Common Dependency Types

Finish-to-Start

Finish-to-start is the most common relationship. The predecessor must finish before the successor can start.

Example: “Approve contract” must finish before “Begin supplier work” starts. If approval takes longer, supplier work moves later.

Start-to-Start

Start-to-start means the successor can begin after the predecessor starts. The first task does not need to finish.

Example: “Begin video editing” may allow “Begin caption writing” to start once enough footage is available. Both activities can continue at the same time.

Finish-to-Finish

Finish-to-finish means the successor cannot finish until the predecessor finishes.

Example: “Complete final testing” may need to finish before “Complete release preparation” can finish. The preparation may start earlier, but its completion depends on testing.

Start-to-Finish

Start-to-finish is less common. The successor cannot finish until the predecessor starts.

Example: an overnight support team may continue working until the daytime team begins its shift. The daytime shift starting allows the overnight shift to finish.

Why Predecessors Matter

Predecessors turn a list of activities into a connected plan. Without them, a schedule may show dates that look precise but ignore the conditions behind those dates.

Suppose a product launch includes marketing approval, packaging production, and shipping. If packaging production begins before approval, the team may produce materials that require expensive changes. A clear dependency prevents that waste.

They Improve Schedule Accuracy

When you connect related tasks, changing one date can reveal the effect on later work. This helps you assess schedule risk before a delay reaches the customer.

For example, a three-day delay in technical review may shift training, launch preparation, and customer communication. The Gantt chart shows that chain more clearly than a simple task list.

They Clarify Responsibilities

A predecessor often reveals who must complete work before another person can proceed. A writer may wait for a subject expert. A developer may wait for a completed design. A sales team may wait for approved pricing.

This makes conversations more specific. Instead of saying “the project is behind,” you can ask, “Which predecessor is preventing this activity from starting?”

They Expose Bottlenecks

A bottleneck is a task that many other activities depend on. If five activities wait for one approval, that approval deserves close attention.

The best part? You can often reduce delays by improving one heavily connected activity rather than speeding up every task.

Predecessors, Successors, and Milestones

These three scheduling ideas work together, although they serve different purposes. A predecessor controls timing, a successor follows the relationship, and a milestone marks an important point in the project.

A milestone can act as a predecessor. For instance, “Design approved” may unlock several activities, including development, marketing preparation, and training creation.

You might be wondering: can one task have several predecessors? Yes. “Launch website” might require final testing, legal approval, payment setup, and content approval. Every required condition should appear in the schedule.

One Predecessor and Several Successors

A single predecessor can unlock many later activities. After “Approve campaign concept,” a team may begin visual design, ad setup, landing page creation, and sales training.

This pattern helps you identify high-impact approvals. If the approval slips, several workstreams may pause together.

Several Predecessors and One Successor

One activity may require multiple earlier tasks. A product launch might need completed testing, approved messaging, finished packaging, and trained support staff.

In that case, the successor usually waits for the last required predecessor. One unfinished condition can delay the entire launch.

Practical Examples for Beginners

Let me explain with three common project situations. Each example shows how the relationship changes the schedule.

Example One: Website Redesign

The content and design work can start together after the outline is approved. The build waits for the design, while publishing waits for quality approval.

Example Two: Office Move

An office move may include signing a lease, ordering furniture, installing internet service, packing equipment, and moving teams. Some activities can overlap, while others require a clear order.

Internet installation may depend on access to the new location. Employee relocation may depend on both furniture delivery and working connectivity. These relationships prevent the team from moving people into an unusable space.

Example Three: Product Release

A product release could include coding, internal testing, security review, customer training, release notes, and deployment.

Training may begin before every defect is fixed, but deployment may require security approval and passed testing. Using different dependency types lets the schedule show this realistic overlap.

Common Mistakes When Adding Predecessors

Predecessors are helpful when they reflect real conditions. Poor relationships can create an unnecessarily rigid schedule or hide important risk.

Linking Every Task to the Previous Task

Some people connect activities in one long chain because it feels orderly. This can delay work that could happen at the same time.

For example, design research and stakeholder interviews may begin together. Linking them end-to-start would make the schedule longer without adding control.

Ignoring External Waiting Time

Approvals, inspections, shipping, and vendor responses often add waiting time. If you leave that time out, the finish date becomes optimistic.

Add lag where a genuine waiting period exists. For example, a two-day review period may occur after submission and before approval.

Using the Wrong Relationship Type

Choosing finish-to-start for every relationship can misrepresent work that overlaps. A content review may begin while writing continues, which could require start-to-start instead.

Ask what actually controls the later activity. That answer should determine the dependency type.

Creating Circular Dependencies

A circular dependency occurs when Task A waits for Task B, while Task B also waits for Task A. Neither activity can proceed.

Review connected activities for loops. If the relationship reflects a real collaboration, divide the work into smaller stages with clear handoffs.

Natural Project Scheduling Solution: ONES.com

ONES.com combines project management and knowledge management in one platform, with AI support through ONES Assistant. ONES Project is its project management product and can serve as a Jira alternative for teams that need connected scheduling and delivery control.

Value Proposition

For teams managing dependency-heavy work, ONES.com can bring task relationships, custom workflows, reporting, and team knowledge into a connected workspace.

ONES Project is sold separately from ONES Wiki, so you can choose the product that fits your planning needs.

Core Capabilities

Scattered task relationships → Gantt scheduling and dependencies → Clear predecessor and successor links

When task relationships are spread across messages and separate planning areas, dependency tracking becomes unreliable. ONES Project supports Gantt-style planning so you can connect activities and see schedule effects in context.

Rigid planning rules → Custom workflows and fields → Project-specific scheduling control

Different projects need different approval stages, ownership fields, and status rules. Custom workflows and fields let you represent those requirements without forcing every team into the same process.

Unclear delivery targets → Sprint management → Short planning cycles with visible commitments

For teams working in iterations, sprint management helps group related activities around a defined delivery period. You can connect sprint tasks to larger milestones and release goals.

Manual follow-up → Automation → Faster handling of routine transitions

Repeated actions can slow a team down. Automation can help update statuses, assign routine work, or trigger notifications when a predecessor reaches a required stage.

Limited schedule visibility → Built-in reporting → Earlier awareness of delays and workload pressure

Managers need more than task completion percentages. Built-in reporting can help reveal delayed work, overloaded contributors, and activities affecting delivery dates.

Plugin-heavy workflows → Native Jira-compatible workflows → Fewer moving parts to maintain

Teams familiar with Jira-compatible workflows can use a similar planning approach while keeping more functionality within the main platform. This can reduce reliance on multiple plugins.

Restricted hosting requirements → Cloud, on-premise, private cloud, and air-gapped deployments → Deployment flexibility

Some organizations need tighter control over hosting and access. ONES.com supports cloud, on-premise, private cloud, and air-gapped deployments, with full feature parity between cloud and self-hosted versions.

Small-team budget pressure → Free plan for up to 30 seats → A lower-barrier starting point

A team with up to 30 seats can begin without a platform subscription cost on the free plan. You can test dependency planning before deciding whether a larger rollout is appropriate.

Application Scenarios

Software release planning: A product team can link coding, testing, security review, release preparation, and deployment. If testing slips, connected activities show which dates may require attention.

Marketing campaign delivery: A campaign team can connect approved messaging to design, landing page creation, advertising setup, and launch. Stakeholders gain a clearer view of approval bottlenecks.

Restricted-network project work: An organization with strict network controls can use an air-gapped deployment while maintaining the same core planning capabilities available in the cloud version.

Common Challenges and Practical Solutions

Challenge: A predecessor blocks work longer than expected

Solution: Break the predecessor into smaller checkpoints. Instead of waiting for “Complete campaign,” allow landing page work to begin after messaging approval if that is genuinely sufficient.

Challenge: A task has too many predecessors

Solution: Separate required conditions from helpful conditions. A task should wait only for activities that truly control its start or finish.

Challenge: The schedule changes every week

Solution: Review dependencies during planning meetings. When scope, staffing, or approval rules change, update the relationships rather than changing dates alone.

Challenge: Team members misunderstand the arrows

Solution: Explain each important dependency in plain language. “Testing must pass before deployment” is easier to understand than an unexplained connector.

FAQs

What is the difference between a predecessor and a dependency?

A predecessor is the specific activity that comes earlier. A dependency is the relationship between that activity and the later activity. For example, “Approve design” is the predecessor to “Build page,” while the finish-to-start connection is the dependency type.

Can a milestone be a predecessor?

Yes. A milestone can represent a decision or approval that unlocks later work. “Contract signed” might act as a predecessor for supplier production, even though the milestone itself has no meaningful duration.

Can one task have multiple predecessors?

Yes. A launch may depend on completed testing, legal approval, final content, and payment configuration. The successor may wait until all required predecessors reach their conditions. Reviewing these links helps you identify the activity most likely to affect the launch date.

What is the most common dependency type?

Finish-to-start is the most common type. It means one activity must finish before the next can begin. For example, a team may need to finish security approval before deploying a product. Other relationship types are useful when activities can overlap.

Should every task have a predecessor?

No. The first activity in a project may have no predecessor. Some independent tasks can also begin without waiting for another activity. Add a relationship only when a real timing condition exists, because unnecessary links can make the schedule harder to manage.

How do I find the right predecessor?

Ask, “What must happen before this activity can begin or finish?” Then check whether that condition is essential. If the answer is “approved design,” connect the design approval activity. If the answer is vague, break the work into smaller activities before adding a dependency.

Conclusion

A predecessor is the earlier task, milestone, or condition that controls a later activity in a Gantt chart. It helps you show the real order of work, reveal bottlenecks, and understand how delays may spread through a project.

Start with the required conditions, choose the correct dependency type, and add realistic waiting periods. Review the links whenever scope, staffing, or approval requirements change.

But here's the truth: a schedule becomes useful when its relationships reflect reality. With clear predecessors, you can move from a list of dates to a plan your team can actually follow.