How to Add Dependencies in Microsoft Project

Managing a project without dependencies is like building a house without a blueprint. You’ll start things in the wrong order, create bottlenecks you never saw coming, and watch deadlines slip one after another.

Microsoft Project solves this — but only if you know how to use task dependencies correctly.

This guide walks you through exactly how to add dependencies in Microsoft Project, the types available, how to edit them, and how to avoid the mistakes that slow teams down.

What Are Task Dependencies in Microsoft Project?

Task dependencies define the relationship between two tasks — specifically, how one task controls when another can start or finish.

In practice, this means: Task B can only begin after Task A reaches a certain state. This sequencing is the backbone of any realistic project schedule.

According to the Project Management Institute (PMI), 77% of high-performing projects use project management software with dependency mapping as a core feature. Teams that skip this step face cascading delays that compound across every downstream task.

Microsoft Project lets you link tasks visually and logically, giving you full control over how your schedule flows — and flagging automatically when something upstream changes.

Types of Task Dependencies

Before you start clicking buttons, understand what you’re building. Microsoft Project supports four dependency types:

Finish-to-Start (FS) — The most common type. Task B cannot start until Task A finishes. Example: You can’t test software before it’s built.

Start-to-Start (SS) — Task B cannot start until Task A starts. Example: Drafting documentation can start when development starts, but not before.

Finish-to-Finish (FF) — Task B cannot finish until Task A finishes. Example: Quality review finishes only when testing finishes.

Start-to-Finish (SF) — Task B cannot finish until Task A starts. This is the rarest type and used in very specific scheduling scenarios like just-in-time production.

Why this matters: A study by Wellingtone found that only 58% of organizations fully understand the value of project management, which means most teams default to Finish-to-Start for everything — and then wonder why their schedules break down. Choosing the right type from the start prevents those surprises.

How to Add Dependencies in Microsoft Project

There are three methods. Use whichever fits your workflow.

Method 1: Using the Task Information Dialog

This is the most precise approach and works well when you want to control lag time, lead time, or dependency type explicitly.

Step 1: Open Microsoft Project and switch to Gantt Chart view (View > Gantt Chart).

Step 2: Double-click the task you want to create a dependency for. The Task Information dialog box opens.

Step 3: Click the Predecessors tab.

Step 4: In the Task Name column, click the dropdown and select the predecessor task — the task that must happen before this one.

Step 5: In the Type column, choose your dependency type: FS, SS, FF, or SF.

Step 6: If needed, add Lag (delay after the predecessor) or Lead (overlap before the predecessor finishes) in the Lag column. Use positive values for lag, negative for lead.

Step 7: Click OK to save.

Method 2: Linking Tasks in the Gantt Chart Directly

This is the fastest method when you’re setting up a straightforward Finish-to-Start sequence.

Step 1: In Gantt Chart view, select the predecessor task by clicking its row.

Step 2: Hold Ctrl and click the successor task (the one that comes after).

Step 3: On the Task ribbon, click Link Tasks (or press Ctrl + F2).

Microsoft Project automatically creates a Finish-to-Start dependency between them, shown as an arrow on the Gantt bar.

Pro tip: You can link multiple tasks at once. Select them in order (top to bottom), then click Link Tasks. Project chains them sequentially.

Method 3: Entering Predecessors in the Task Table

For power users managing large projects, this is the fastest bulk method.

Step 1: In Gantt Chart view, locate the Predecessors column in the task table on the left. If it’s not visible, right-click any column header and insert it.

Step 2: Click the Predecessors cell for the task you want to define.

Step 3: Type the task ID of the predecessor. For example, if Task 3 must finish before Task 7 starts, type 3 in Task 7’s Predecessors cell.

Step 4: To specify a type, add the abbreviation after the ID. For example: 3FS (Finish-to-Start), 3SS (Start-to-Start), 3FF (Finish-to-Finish).

Step 5: To add lag or lead, append a plus or minus value. Example: 3FS+2d means Task 7 starts 2 days after Task 3 finishes.

Step 6: Press Enter to confirm. The Gantt chart updates in real time.

How to Edit or Remove Task Dependencies

Schedules change. Here’s how to update dependencies without breaking your plan.

Editing a Dependency

Double-click the task with the dependency you want to change → go to the Predecessors tab → update the type, lag, or predecessor task → click OK.

You can also click directly on the dependency arrow in the Gantt chart to open a quick editing panel.

Removing a Dependency

Option 1: In the Predecessors tab, select the row and press the Delete key.

Option 2: Select both tasks → click Unlink Tasks on the Task ribbon (or press Ctrl + Shift + F2).

Option 3: Click directly on the Gantt dependency arrow and select Delete.

Adding Lag and Lead Time to Dependencies

Lag and lead time give your dependencies nuance that a simple link can’t.

Lag time adds a buffer between tasks. Example: After sending a proposal (Task A), you wait 3 days before following up (Task B). Set this as 3FS+3d.

Lead time allows tasks to overlap. Example: You can start onboarding a client 2 days before the contract is fully signed. Set this as 2FS-2d.

To add lag or lead: Open Task Information → Predecessors tab → type the lag value in the Lag column using positive (lag) or negative (lead) numbers with a unit: d for days, h for hours, w for weeks.

Viewing and Managing All Dependencies

Use Network Diagram View

Go to View > Network Diagram to see all task relationships displayed as a flowchart. This is especially useful for spotting circular dependencies (where Task A depends on Task B, which depends on Task A — a loop that makes your schedule impossible).

Check the Task Path Feature

Go to Format > Task Path and choose Predecessors, Driving Predecessors, Successors, or Driving Successors. Microsoft Project highlights the relevant tasks on the Gantt chart in color, making it easy to trace any critical path.

Use the Task Inspector

On the Task ribbon, click Inspect. The Task Inspector panel opens on the left and shows all factors controlling a task’s start date — including its predecessors and any constraints.

Common Mistakes That Break Project Schedules

Over-relying on Finish-to-Start: Not every task needs to be fully complete before the next begins. Using SS or FF where appropriate can compress timelines significantly.

Ignoring the critical path: Microsoft Project’s critical path feature (View > Gantt Chart > Format > Critical Tasks) shows which tasks directly affect your end date. Dependencies on non-critical tasks rarely cause project delays — dependencies on critical tasks always do.

Adding too many constraints alongside dependencies: Constraints like “Must Start On” override dependency logic. Use them sparingly, or your dependency relationships become meaningless.

Forgetting to update dependencies when scope changes: When tasks are added or removed, linked dependencies don’t update automatically. A quarterly dependency audit saves significant rework.

According to KPMG’s Global Project Management Survey, 70% of organizations have experienced at least one project failure in the past year — and poor dependency management is consistently listed as one of the top three causes. Getting this right isn’t optional; it’s foundational.

Microsoft Project and Project Management: Key Statistics

Understanding the landscape helps put these skills in context:

• 77% of high-performing projects use purpose-built project management software (PMI, 2023)
• Only 43% of projects are completed within their original budget (PMI Pulse of the Profession)
• 48% of projects miss their deadline due to poor planning or dependency mismanagement (Wellingtone State of Project Management Report)
• $50,000 is wasted every minute globally due to poor project performance (PMI)
• Projects using structured scheduling techniques — including dependency mapping — are 2.5x more likely to succeed than those that don’t (Standish Group CHAOS Report)
• 58% of organizations don’t fully understand the value of project management (Wellingtone)
• Teams that use the critical path method — which depends entirely on correct task linking — reduce project delays by up to 30% (Gartner)
• 70% of business transformations fail, with scheduling errors cited as a leading contributor (McKinsey)
• Microsoft Project has over 20 million users across enterprise organizations worldwide (Microsoft)
• Organizations with mature project management practices waste 28 times less money than those without (PMI)

Conclusion

Adding dependencies in Microsoft Project is what separates a real schedule from a list of dates.

When you link tasks correctly — using the right dependency type, adding lag or lead where needed, and auditing your critical path — your plan becomes predictive, not reactive. You stop chasing fires and start anticipating them.

Start with Method 1 (Task Information dialog) to build precision habits. Graduate to Method 3 (direct table entry) as your project complexity grows. And always validate your dependency structure against the critical path before locking in your baseline.

The data is clear: teams that use structured dependency management complete projects faster, within budget, and with fewer surprises. That’s not a coincidence — it’s the compounding result of getting the fundamentals right.