Work Breakdown Structure (WBS) to Gantt Chart Conversion

Why Both Tools Are Needed

A Work Breakdown Structure (WBS) and a Gantt chart solve adjacent problems. The WBS answers "what needs to be done"—it decomposes the project scope into a hierarchical list of deliverables and work packages. The Gantt chart answers "when does it happen"—it schedules those work packages on a timeline with durations, dependencies, and resource assignments.

Skipping the WBS and jumping straight to a Gantt chart often means the schedule misses entire categories of work. Building a WBS without converting it to a Gantt chart means you have a scope document with no execution plan.

The correct sequence: WBS first, then Gantt chart.

What a WBS Looks Like

A WBS breaks the project into levels:

Level 1: The project itself (e.g., "Website Redesign")

Level 2: Major deliverables or phases (e.g., "Discovery," "Design," "Development," "Launch")

Level 3: Work packages within each phase (e.g., under "Design": "Wireframes," "Visual design," "Prototype," "Design review")

Level 4 (optional): Tasks within work packages (e.g., under "Wireframes": "Homepage wireframe," "Product page wireframe," "Checkout flow wireframe")

Each item at the lowest level—called a work package—is what you'll convert into a Gantt chart task. If your WBS goes four levels deep, the Level 4 items become Gantt tasks. If it only goes three levels, Level 3 items become the tasks.

Step 1: Extract the Task List from Your WBS

Start by listing every work package from your WBS as a flat list. This becomes your Gantt chart task list. Don't worry about order or dates yet—just get every item on the list.

For the website redesign example:

Stakeholder interviews
Competitive analysis
Content audit
Homepage wireframe
Product page wireframe
Checkout flow wireframe
Visual design system
Component library
Homepage development
Product page development
Checkout development
QA testing
Performance optimization
Launch preparation
Go-live

Step 2: Group Tasks into Phases

In your Gantt chart, organize the flat task list back into the WBS phases. Use summary rows (parent tasks) that match your WBS Level 2 categories. This maintains the hierarchical structure of the WBS while adding time dimensions.

In gantt-chart.io, create a row for each phase ("Discovery," "Design," "Development," "Launch"), then add the work package tasks as children within each phase.

Step 3: Estimate Duration for Each Task

Now add time estimates. Work packages without time estimates are the most common gap between a WBS and a usable schedule.

For each task, estimate:

Best case duration (everything goes well)
Most likely duration (normal friction, some rework)
Worst case duration (dependencies delayed, scope expands)

Use the most likely estimate in your Gantt chart. Note the worst case duration for tasks on your critical path—those are the ones that can blow your end date if they slip.

If you're uncertain about an estimate, pad it by 25-30%. It's better to deliver early than to replan constantly.

Step 4: Identify Dependencies Between Tasks

Go through your task list and identify which tasks can't start until another is complete. This is the dependency mapping step—it's what transforms a list of tasks into a network of interconnected work.

Common dependency types:

Finish-to-Start (FS): Task B starts after Task A finishes (most common)
Start-to-Start (SS): Task B can start at the same time as Task A
Finish-to-Finish (FF): Task B must finish at the same time as Task A

In your website redesign example:

Visual design starts after wireframes are approved (FS)
Homepage and product page development can run in parallel (SS)
QA testing starts after all development is complete (FS)

Add dependency arrows in your Gantt chart on gantt-chart.io to connect these tasks.

Step 5: Set Start Dates and Sequence the Timeline

With tasks, durations, and dependencies in place, set your project start date and let the dependencies drive the rest. The Gantt chart will automatically sequence tasks based on dependencies.

Review the resulting timeline:

Does the end date match your target? If not, look for opportunities to parallelize or compress.
Are there tasks scheduled before their dependencies are met? Fix those.
Are any team members overallocated in specific weeks? Adjust.

Step 6: Validate Against Your WBS

Before finalizing, check your Gantt chart against the original WBS:

Does every WBS work package appear as a Gantt task? Missing tasks mean scope gaps.
Are the WBS phases represented as summary rows? Missing phases create organizational confusion.
Does the total duration make sense given the scope in the WBS?

This validation step is where you catch the errors that cause project overruns—work that was in the WBS but accidentally omitted from the schedule.

Maintaining Alignment During the Project

As work progresses, the WBS and Gantt chart should stay aligned. When scope is added:

Add the new work package to the WBS first
Estimate its duration
Add it to the Gantt chart with dependencies
Assess the impact on the end date and resources

When scope is removed:

Remove it from the WBS
Remove the corresponding task from the Gantt chart
Update any dependencies affected by its removal
Update the timeline

This two-document discipline—WBS for scope, Gantt for schedule—prevents the common failure mode where the schedule grows without formal scope acknowledgment.

Getting Started

If you have a WBS document already, the conversion to a Gantt chart takes 1-2 hours for a medium-complexity project. Open gantt-chart.io, create your phase rows, add your work package tasks, estimate durations, add dependencies, and set your start date.

The result is a project plan where every task traces back to an approved scope item—and every scope item is scheduled on a timeline.