Free work breakdown structure template
A work breakdown structure
you can see whole.
Break the project into deliverables, then into work packages small enough to estimate and hand to one person.
Use it free — no card, no trial →
- Free forever — not a trial
- Up to 10 maps, kept for good
- Every export included
Free has no end date — upgrade only if you outgrow 10 maps. Opens with five numbered phases, sample deliverables and fields for owner, estimate and status.
The whole scope, one tree. Every deliverable hangs off the project. If it is not on the map, it is not in the project.
Owners and estimates on the work. Each work package has an owner, an estimate in days, a status and acceptance criteria.
Draft it in a minute. Ask ChatGPT or Claude for a first WBS. Then edit it by hand, branch by branch.
How to build a work breakdown structure, step by step
A work breakdown structure (WBS) splits a project's scope into smaller pieces. The top is the whole project. The bottom is the work package: a piece of work one person can own, estimate and finish. The WBS lists what gets delivered, not when.
- Name the project and its result. Put the final deliverable at the centre: "New company website live", not "Website work".
- Pick the first level. Split by deliverable (design, content, build) or by phase (planning, execution, closeout). Pick one rule and keep it on that level.
- Break each branch down. Ask what this deliverable is made of. Write nouns, not tasks: "Page designs", not "Design the pages".
- Check the 100% rule. The children of a branch must add up to all of its work. Nothing missing, nothing counted twice, nothing outside the scope.
- Stop at work packages. Stop when a piece has one owner and a sensible estimate. A common rule of thumb is between one day and two weeks.
- Number every item. Type the code into the title: 1, 1.1, 1.1.1. People can then refer to "3.2" in meetings and reports.
- Fill in the fields. Give each work package an owner, an estimate and acceptance criteria. This list of details is your WBS dictionary.
WBS example: a website relaunch
A small company relaunches its website. Phases sit on the first level. Deliverables and work packages sit beneath them. This is the map shown above.
- 🚩 1 Initiation
- 1.1 Project charterOwner: Maya · Estimate (days): 2 · Status: Done
- 🗺️ 2 Planning
- 2.1 Sitemap and content planOwner: Leo · Estimate (days): 3 · Status: Done
- 2.2 Schedule & budgetOwner: Maya · Estimate (days): 2 · Status: In progress
- 🛠️ 3 Execution
- 3.1 Visual design
- 3.1.1 WireframesOwner: Priya · Estimate (days): 4 · Status: In progress
- 3.1.2 Page designsOwner: Priya · Estimate (days): 6 · Status: Not started · Acceptance criteria: Signed off by marketing
- 3.2 Page copy and photosOwner: Leo · Estimate (days): 8 · Status: Blocked · Acceptance criteria: Copy for all 24 pages approved
- 3.3 Build
- 3.3.1 Page templatesOwner: Tom · Estimate (days): 10 · Status: Not started
- 3.3.2 Content migrationOwner: Tom · Estimate (days): 5 · Status: Not started
- 3.1 Visual design
- 📊 4 Monitoring & control
- 4.1 Weekly status reportsOwner: Maya · Estimate (days): 4 · Status: In progress
- 🏁 5 Closeout
- 5.1 Launch and redirectsOwner: Tom · Estimate (days): 2 · Status: Not started · Acceptance criteria: Every old URL redirects
- 5.2 Lessons learnedOwner: Maya · Estimate (days): 1 · Status: Not started
Estimates sit on work packages only, never on their parents. That way nothing is counted twice. Here they add up to 47 days. The blocked copy is easy to spot before it holds up the build.
Let ChatGPT or Claude draft it
Connect Atlas Red to ChatGPT or Claude once. It is free. Then ask:
Make a work breakdown structure in Atlas Red for this project: [describe the project and its final deliverable]. Use the WBS template, number every item, and break each branch down to work packages with an owner and an estimate in days.
You get the same template, filled in, in your own account. Fix what it got wrong by hand. Or ask for another round.
Questions people ask
What is a work breakdown structure in project management?
A tree of everything a project must deliver. The project sits at the top. Each level splits the one above into smaller parts. The lowest level is the work package, which one person owns and estimates. The idea is central to PMI's PMBOK Guide. Schedules, budgets and risk lists are built on it.
Can ChatGPT make a work breakdown structure?
It can draft one. Connect Atlas Red to ChatGPT or Claude and describe your project. It builds the WBS from this template in your workspace. Then check it yourself: the assistant only knows what you told it. Look for missing deliverables and work counted twice.
Is the WBS example above deliverable-based or phase-based?
Both. The first level is phases, and the deliverables sit beneath them. A deliverable-based WBS puts the products on the first level, such as design, content and build. A phase-based WBS puts the stages there. Pick one rule per level and stick to it. Mixing them on one level leads to double counting.
Is this work breakdown structure template free?
Yes. It is part of Atlas Red's Free edition: up to 10 maps, kept with no end date, every export included, no credit card. Pro is a one-time $99 payment for unlimited maps.
Can I export the WBS to Excel, Word or PowerPoint?
Not as an Excel, Word or PowerPoint file. You get PDF, PNG, JPEG and SVG images, slides, an interactive web page, Markdown, OPML and plain text. Markdown keeps the fields as "Label: value" lines. It pastes into Word or Google Docs.
What is the difference between a WBS and a Gantt chart?
A WBS says what the project delivers. A Gantt chart says when each piece happens and what depends on what. Most teams build the WBS first and schedule its work packages next. Atlas Red is not a Gantt tool. Use it for the WBS, then take the work packages into your scheduling tool.
Does this template work for a PBS, RBS or CBS?
Yes. They are the same kind of tree. A product breakdown structure (PBS) splits a product into parts. A risk breakdown structure (RBS) groups risks by source. A cost breakdown structure (CBS) splits the budget into cost items. Rename the branches and keep the fields you need. Atlas Red does not add up the amounts for you.