Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 17 tasks across 6 phases, about 7 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| 1 Project management | 1.1 Charter and kickoff | 2 days | Day 1 | Nothing (starts first) |
| 1 Project management | 1.2 Schedule and budget baseline | 3 days | Day 3 | 1.1 Charter and kickoff |
| 2 Requirements | 2.1 Stakeholder interviews | 4 days | Day 3 | 1.1 Charter and kickoff |
| 2 Requirements | 2.2 Requirements document | 3 days | Day 7 | 2.1 Stakeholder interviews |
| 2 Requirements | 2.3 Requirements sign-off | 1 day | Day 10 | 2.2 Requirements document, 1.2 Schedule and budget baseline |
| 3 Design | 3.1 Information architecture | 4 days | Day 11 | 2.3 Requirements sign-off |
| 3 Design | 3.2 Visual design | 6 days | Day 15 | 3.1 Information architecture |
| 3 Design | 3.3 Technical design | 5 days | Day 11 | 2.3 Requirements sign-off |
| 4 Build | 4.1 Front end | 12 days | Day 21 | 3.2 Visual design, 3.3 Technical design |
| 4 Build | 4.2 Back end and integrations | 14 days | Day 16 | 3.3 Technical design |
| 4 Build | 4.3 Content migration | 8 days | Day 15 | 3.1 Information architecture |
| 5 Test | 5.1 System testing | 5 days | Day 33 | 4.1 Front end, 4.2 Back end and integrations |
| 5 Test | 5.2 User acceptance testing | 4 days | Day 38 | 5.1 System testing, 4.3 Content migration |
| 6 Deploy | 6.1 User training | 3 days | Day 38 | 5.1 System testing |
| 6 Deploy | 6.2 Go-live | 1 day | Day 42 | 5.2 User acceptance testing, 6.1 User training |
| 6 Deploy | 6.3 Hypercare | 5 days | Day 43 | 6.2 Go-live |
| 1 Project management | 1.3 Project closeout | 2 days | Day 48 | 6.3 Hypercare |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 49 days instead of the 82 it would take one task at a time. The 12 darker bars are the critical path: a day lost on any of them moves the finish date.
About this work breakdown structure (wbs)
A work breakdown structure (WBS) splits a project into the deliverables it has to produce, then splits each deliverable into work packages small enough to estimate and assign. It is the step between "what are we making" and "when will it be done". Most WBS templates stop at the tree diagram. This one carries the numbering straight onto a Gantt chart, so each work package also has a duration, an owner and the packages it waits for.
The example project is a customer portal: a website where customers log in to see their account. It has six level-1 deliverables (project management, requirements, design, build, test and deploy), numbered 1 to 6, and two to three work packages under each, numbered 1.1, 1.2 and so on. The numbers stay in the task names, so the Gantt chart and the WBS always match.
Replace the example with your own deliverables. The structure (deliverables first, then work packages, then links) works for any project, from an office move to a product launch.
Who it's for: Project managers building a plan from scope, and students learning how a WBS turns into a schedule.
How to use it
- Use this template. Click Use this template. Each level-1 deliverable opens as its own lane, with the work packages as tasks and the links between them already drawn.
- Replace the level-1 deliverables. Write the five to eight main deliverables of your project as lanes and number them 1, 2, 3. Together they should cover the whole scope and nothing outside it.
- Break each deliverable into work packages. Under each deliverable, add work packages numbered 1.1, 1.2 and so on until each one is small enough to estimate and give to one owner. Then set durations and say what each package waits for.
- Check the critical path. The darker bars show which work packages set the finish date. If the path is not what you expected, a link is probably missing or wrong.
How to break down the work
Start from deliverables, not activities. "Visual design" is a deliverable; "have design meetings" is an activity. Deliverables make the WBS a complete picture of scope, which is the point of it: the level-1 items together should add up to everything the project produces, and nothing else. This is often called the 100% rule.
Stop breaking down when a work package can be estimated with confidence and handed to one person or team. A common rule of thumb is that a work package should take somewhere between a day and two weeks of effort. Larger than that and progress is hard to see; smaller and the plan becomes a to-do list that nobody maintains.
From WBS to schedule
A WBS on its own says nothing about order. The schedule comes from the links: which work packages have to finish before others can start. In this example the back end waits only for the technical design, while the front end also waits for the visual design, so the two build packages start on different days. Content migration needs only the information architecture, so it runs alongside the build with slack to spare.
Keep the WBS numbers in the task names when you move to the schedule. They let anyone trace a bar on the Gantt chart back to the scope, and they make status reports easier to read because "4.2 is two days late" means the same thing to everyone.
Planning tips
- Write a one-line WBS dictionary entry for each work package (what is included and what done looks like) in the task notes.
- Put project management in as its own deliverable. Planning, reporting and closing take time and belong in the scope.
- Do not break down work that is far in the future in detail yet. Add the detail when the phase gets closer.
- Review the WBS with the people who will do the work. They will find the missing packages.
Frequently asked questions
- What is a work breakdown structure template?
- A starting structure for splitting a project into deliverables and work packages, usually numbered (1, 1.1, 1.2). This template also schedules each work package on a Gantt chart with durations and dependencies.
- How many levels should a WBS have?
- Most projects need two or three levels: the project, its main deliverables, and work packages under each. Go deeper only where a work package is still too large to estimate or assign.
- What is the difference between a WBS and a Gantt chart?
- The WBS shows what the work is, as a hierarchy. The Gantt chart shows when it happens, with durations and dependencies. This template is both: the WBS numbering is kept in the task names and the deliverables are the lanes.
- Can I export the WBS to Excel?
- Yes. Download CSV on this page gives every work package with its WBS number, deliverable, start and end dates and dependencies, ready for Excel or Google Sheets.
Related templates and guides
- Project Plan Gantt chart template
- Resource Plan Gantt chart template
- Software Development Project Gantt chart template
- IT Project Plan Gantt chart template
- Engineering Design Project Gantt chart template
- Smartsheet alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.