Gantt Chart Predecessors Explained: A Beginner’s Guide 2026

A Gantt chart can look organized while hiding a serious scheduling problem. Tasks may appear in the right order, yet one delay can quietly disrupt everything that follows. Without clear relationships, your timeline becomes a list of dates instead of a working plan.

That confusion often starts with one term: predecessor. If you misunderstand it, you may connect tasks incorrectly, create impossible dates, or miss the activity controlling your project finish date. The good news is that the concept is simple once you see it in action.

This guide explains what a predecessor means in a Gantt chart, how it connects tasks, and how to use dependencies confidently in 2026. You will also see practical examples, common mistakes, and ways to manage linked schedules more clearly.

What Is a Predecessor in a Gantt Chart?

A predecessor in a Gantt chart is a task that controls when another task can start or finish. The task affected by it is called the successor.

For example, “Approve website design” is the predecessor of “Start development.” Development depends on the approval, so the second activity cannot begin freely.

Here’s why: predecessors show the logic behind your schedule. They explain which activity must happen first, which activities can overlap, and what delay could affect later work.

Predecessor and successor in plain English

Think of two connected activities:

• Predecessor: the earlier or controlling task.
• Successor: the later task that depends on the relationship.

Suppose your team must install electrical wiring before closing a wall. “Install wiring” is the predecessor, while “Close wall” is the successor.

The relationship does not always mean the predecessor must finish completely. In some schedules, a successor can begin while the predecessor is still underway.

Why predecessors matter

A predecessor helps you turn separate activities into a logical sequence. That sequence supports planning, forecasting, resource coordination, and progress tracking.

Without dependencies, moving one activity requires manual changes across the schedule. With dependencies, connected dates can adjust when the controlling activity changes.

The best part? You can spot risk earlier. If a supplier approval controls three later activities, the approval deserves closer attention than a task with plenty of schedule flexibility.

A quick example

Imagine a product launch with these activities:

1. Define launch requirements.
2. Create the campaign design.
3. Approve the campaign design.
4. Publish promotional content.

“Define launch requirements” can precede “Create the campaign design.” Then “Approve the campaign design” precedes “Publish promotional content.”

If approval takes two extra days, publishing may also move two days later. The dependency makes that effect visible.

How Predecessors Connect Tasks

Gantt chart relationships usually describe how the start or finish of one activity relates to another. The connection can be strict, flexible, or separated by a waiting period.

You might be wondering: does every predecessor need to finish before the next task begins? No. The relationship type determines the answer.

Finish-to-start dependency

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

Example: “Complete safety inspection” must finish before “Open the facility.” This pattern suits work that requires a formal handoff.

Start-to-start dependency

Start-to-start means the successor can begin after the predecessor starts.

For example, “Begin software testing” may start after “Begin system integration.” Both activities can continue at the same time, though their start dates remain connected.

Finish-to-finish dependency

Finish-to-finish links the completion of two activities. The successor cannot finish until the predecessor finishes.

Consider “Write training materials” and “Review training materials.” Review might begin early, yet final review completion depends on the writing being complete.

Start-to-finish dependency

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

A practical example involves a support shift. “Night support begins” may control when “Day support ends.” The incoming shift must start before the outgoing shift can finish.

Lag and lead time

Some relationships include a delay or overlap.

• Lag: waiting time added between connected activities.
• Lead: permitted overlap between connected activities.

For example, concrete may need three curing days before painting begins. That relationship uses finish-to-start with three days of lag.

A lead might allow a reviewer to begin checking a long report before the writer completes every section. Use lead carefully because excessive overlap can create rework.

How to Add a Predecessor to Your Schedule

Creating a useful relationship takes more than drawing a line between two bars. You need to understand the work, confirm the handoff, and choose the correct dependency type.

Step 1: List the activities

Write each meaningful activity as a separate task. Avoid combining unrelated work under a vague label such as “Prepare launch.”

A clearer breakdown might include research audience needs, draft messaging, review messaging, build the landing page, and test the page.

Step 2: Identify the handoff

Ask what must happen before each activity can begin or finish. The answer usually reveals a predecessor.

For “Test the landing page,” the predecessor might be “Build the landing page.” For “Publish the landing page,” the predecessor could include testing and legal approval.

Step 3: Choose the relationship type

Use finish-to-start when the next activity truly waits for completion. Use start-to-start when both activities can proceed together.

Do not select a relationship simply because it appears frequently in your planning tool. The work itself should determine the connection.

Step 4: Add lag only when reality requires it

Lag represents a real waiting period, such as curing, shipping, regulatory review, or scheduled access.

Avoid adding lag as a cushion for uncertainty. Use a realistic duration or risk allowance instead. Hidden padding makes the schedule harder to understand.

Step 5: Review the chain with the team

Ask the people performing the work to verify each relationship. A planner may assume approval is required first, while a specialist knows preparation can begin earlier.

Let me explain: a dependency is a planning decision. Team review helps you distinguish a true constraint from a convenient assumption.

Predecessors, Critical Path, and Schedule Risk

Predecessors become especially important when you analyze the critical path. The critical path is the sequence of dependent activities that determines the earliest possible project finish.

If a task on that path slips by three days, the project finish may slip by three days. A task outside the path may have float, allowing it to move without changing the final milestone.

Example of a dependency chain

Consider this sequence:

The linked chain lasts 11 working days. If “Build prototype” takes seven days, the release date moves unless another activity absorbs the delay.

How float changes the impact

Suppose “Prepare internal training” takes four days but has two days of float. A one-day delay may not change the project finish.

That distinction helps you focus attention. Track every dependency, then prioritize activities with little or no scheduling flexibility.

Multiple predecessors

A successor can depend on several earlier activities. “Launch campaign” might require approved creative, a tested landing page, and confirmed tracking.

In this case, the launch waits for the latest required predecessor. Even if two activities finish early, one delayed approval can still control the launch date.

Common Mistakes When Using Dependencies

Most scheduling problems come from relationships that reflect habit instead of actual work. A few practical checks can prevent major confusion.

Linking every task to the previous row

Some planners connect each activity to the line above it. That creates a neat visual chain, but the work may not follow that order.

For example, preparing training material may start while quality testing continues. A forced link could delay useful work without a real reason.

Using too many dependencies

Extra relationships create a rigid schedule. If every minor activity controls another task, small changes can trigger widespread date movement.

Connect activities when a real handoff, restriction, or timing condition exists. Leave independent work independent.

Ignoring external predecessors

A schedule may depend on a customer decision, supplier delivery, inspection, or access window. These conditions still affect your timeline, even when your team does not perform them.

Represent them as milestones or clearly named activities. Otherwise, your plan may appear achievable while depending on an invisible event.

Choosing finish-to-start by default

Finish-to-start is useful, but it can make a schedule longer than necessary. Review whether the successor can begin earlier.

For example, content review may start as sections become ready. A start-to-start relationship could reflect that workflow more accurately.

Failing to update relationships

Project conditions change. A new approval route, supplier, or technical approach can alter the correct predecessor.

Review dependencies during milestone meetings, scope changes, and major risk updates. A stale relationship can be as harmful as a missing one.

Practical Ways to Improve Dependency Planning

Clear dependency planning combines accurate task names, realistic timing, and regular review. You do not need a complicated method to improve quickly.

Use action-based task names

“Review contract terms” communicates more than “Contract.” Action-based names make handoffs easier to identify.

Separate approval from production

Approval often controls later work. Give it its own activity instead of hiding it inside a broad production task.

For example, separate “Draft product page,” “Approve product page,” and “Publish product page.” Each step can then show its own owner and timing.

Mark milestones clearly

A milestone represents an important event with little or no duration, such as signed approval or launch readiness.

Milestones make predecessor relationships easier to understand. Several activities may lead into one decision point, which then controls later work.

Review the longest chains first

Start schedule reviews with the path controlling the finish date. Then examine activities with low float and several successors.

This approach gives you more value than reviewing every task equally. It connects planning effort with schedule risk.

Use a dependency review checklist

• Does each relationship reflect a real work condition?
• Can the successor begin earlier?
• Is the dependency type correct?
• Does the relationship include a justified lag or lead?
• Could an external event affect the timing?
• Would a delay change the final milestone?

Natural Project Scheduling Solution: ONES.com

Value Proposition

ONES.com combines project management and knowledge management in one platform, with AI support through ONES Assistant. ONES Project is the project management product and can serve as a Jira alternative, while ONES Wiki supports knowledge management as a Confluence alternative.

You can purchase them separately. ONES.com offers a free plan for up to 30 seats and supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments.

Core Capabilities

• Scattered task relationships → Jira-compatible workflows → You can organize linked activities in a familiar project structure and make predecessor relationships easier to follow.
• Unclear schedule ownership → Custom workflows and fields → You can show owners, approval states, risk details, and dependency information in the same work process.
• Manual date coordination → Automation → Repetitive transitions and notifications can follow defined conditions, reducing avoidable coordination work.
• Weak sprint visibility → Sprint management → Agile teams can connect sprint activities with broader milestones and review how dependencies affect delivery.
• Limited schedule insight → Built-in reporting → Reports help you examine progress, workload, and delivery patterns without relying on separate systems.
• Too many disconnected plugins → Native project capabilities → Core planning features work together, which can reduce the need for multiple add-ons.
• Restricted deployment requirements → On-Premise, Private Cloud, and Air-gapped options → Teams with controlled environments can choose a deployment that fits their operational requirements.
• Different environments behaving differently → Feature parity across cloud and self-hosted versions → Teams can use the deployment model they need while retaining comparable capabilities.

Application Scenarios

Software release planning: A product team can connect requirements, development, testing, approval, and release milestones. If testing slips, linked activities reveal the likely delivery effect.

Regulated engineering work: An engineering team can keep approval gates, technical activities, and review steps connected in an On-Premise or Air-gapped environment.

Cross-functional launches: Marketing, product, design, and operations can coordinate shared milestones while keeping task ownership visible. ONES Wiki can hold supporting team knowledge separately from ONES Project.

Common Challenges and Practical Solutions

Challenge: The schedule becomes too rigid

Solution: Review whether every finish-to-start relationship is necessary. Replace artificial links with start-to-start or finish-to-finish relationships when parallel work is realistic.

Challenge: Teams disagree about task order

Solution: Ask each owner to describe the actual handoff. Capture the specific condition, such as approval, access, testing, or delivery, before choosing a relationship.

Challenge: Delays appear too late

Solution: Track activities with multiple successors and low float. These tasks can spread risk quickly across the schedule.

Challenge: External events are invisible

Solution: Add clear milestones for supplier deliveries, customer approvals, inspections, and access dates. Assign an owner to monitor each event.

Challenge: Dependencies become outdated

Solution: Review relationships at scope changes, milestone reviews, and major planning revisions. Remove links that no longer describe the work.

FAQs

What is the difference between a predecessor and a successor?

A predecessor is the activity that controls or influences another activity’s timing. A successor is the activity affected by that relationship. For example, “Approve design” is the predecessor of “Begin development.” A task can be a successor in one relationship and a predecessor in another, creating a chain across the schedule.

Can one task have several predecessors?

Yes. A task can depend on multiple activities. For example, a product launch may require approved marketing content, completed testing, and confirmed supply availability. The launch can proceed only when every required predecessor reaches its necessary condition.

Does a predecessor always need to finish first?

No. Finish-to-start requires completion before the successor begins, but other relationships allow overlap. Start-to-start can connect activities that begin together, while finish-to-finish can connect activities that complete together. The correct relationship depends on the real workflow.

What does lag mean in a Gantt chart?

Lag is a waiting period between linked activities. For example, painting may begin three days after concrete work finishes because the surface needs time to cure. Lag should represent a genuine timing requirement, rather than general uncertainty or extra padding.

How do predecessors affect the critical path?

Predecessors create the chains that determine project timing. When a chain has little or no float, a delay in one activity can delay the final milestone. Reviewing these chains helps you focus attention on the activities with the greatest schedule impact.

Can a milestone be a predecessor?

Yes. A milestone can represent an approval, delivery, inspection, or readiness decision. Later activities can depend on that event. For example, “Regulatory approval received” may act as a predecessor for production release, even though the milestone has no duration.

Conclusion

A predecessor is the task or milestone that controls when another activity can start or finish. Its relationship with a successor gives your Gantt chart practical scheduling logic.

Start with clear activities, identify real handoffs, choose the correct dependency type, and add lag only when a genuine waiting period exists. Then review critical chains, external conditions, and outdated relationships.

But here's the truth: a Gantt chart becomes useful when it reflects how work actually happens. With thoughtful predecessors, you can see risk earlier, coordinate teams more confidently, and make schedule changes with fewer surprises.