A complete work breakdown structure template for Excel
This free work breakdown structure template for Excel helps project managers turn an approved scope into organized, assignable, and measurable work.
The workbook uses a three-level hierarchy: the project at level 1, major deliverables or control accounts at level 2, and manageable work packages or milestones at level 3. Each work package can have an owner, estimate, actual hours, progress, start date, due date, priority, schedule flag, dictionary entry, and linked deliverable.
Unlike a simple task list, a project WBS focuses on the complete scope of work. If you are deciding how those concepts differ, see task management vs. project management. It helps teams confirm that nothing has been omitted, define responsibility, improve estimates, clarify acceptance, and establish a reliable structure for schedules, budgets, risks, and status reporting.
Download the free Excel WBS template
Includes sample data, formulas, dropdowns, conditional formatting, charts, a WBS dictionary, a deliverables log, a hierarchy view, and seven ready-to-use worksheets.
What is included in the Excel WBS template?
WBS dashboard
See work-package count, deliverables, planned and actual hours, weighted progress, completed packages, overdue items, phase workload, and acceptance status.
WBS register
Manage WBS ID, parent, level, phase, work package, owner, type, priority, status, hours, progress, dates, duration, earned hours, and schedule flag.
WBS dictionary
Define descriptions, acceptance criteria, inputs, outputs, assumptions, exclusions, dependencies, approvers, and dictionary status.
Deliverables and acceptance log
Track each major output, linked WBS ID, owner, planned and actual delivery, delivery status, acceptance status, approver, remaining days, and attention flag.
Formula-driven WBS tree
Present the hierarchy in a clean indented view that stays linked to the register and shows ownership, type, status, progress, and effort.
Sample project structure
Learn from a populated customer-portal example covering project management, discovery, UX, development, content, testing, and launch.
How to create a work breakdown structure in Excel
Confirm the project outcome
Start with the approved scope, objectives, success criteria, constraints, and major deliverables. The WBS should represent the whole project—not only the work that is currently visible.
Define major control accounts
Create level 2 branches for meaningful deliverables, phases, products, locations, systems, or responsibility areas. Each branch should be complete without overlapping another branch.
Decompose into work packages
Break each branch into level 3 work packages that are small enough to estimate, assign, schedule, monitor, and accept—but not so small that the WBS becomes a daily checklist.
Add owners, estimates, and dates
Assign one accountable owner, then enter planned hours, start date, due date, priority, and initial status. The workbook calculates duration, remaining days, earned hours, and schedule flags.
Complete the WBS dictionary
For each important package, document the output, acceptance criteria, inputs, assumptions, exclusions, dependencies, and approver. This is where the structure becomes usable scope control.
Baseline and review the WBS
Validate the hierarchy with the team, confirm the 100% rule, approve the scope baseline, and use the dashboard during reviews to monitor progress and exceptions.
Work breakdown structure example
The included customer-portal example shows how a project can be decomposed from major control accounts into assignable work packages. WBS codes preserve the parent-child relationship and make each package easy to reference in schedules, budgets, risks, and reports. Once sequencing matters, a Gantt chart can turn those work packages into a time-based plan.
| WBS ID | Hierarchy Element | Owner | Type | Planned Hours | Progress |
|---|---|---|---|---|---|
| 1 | Customer Portal Launch | Daniel Brooks | Project | 3,060 | 38% |
| 1.3 | UX & Design | Aisha Khan | Control Account | 404 | 74% |
| 1.3.2 | Responsive wireframes | Aisha Khan | Work Package | 120 | 100% |
| 1.4 | Development | Marcus Lee | Control Account | 996 | 39% |
| 1.4.2 | Authentication and profile | Sofia Patel | Work Package | 220 | 55% |
| 1.7.3 | Production launch | Daniel Brooks | Milestone | 40 | 0% |
A real WBS can have more or fewer levels. Use only the detail required to estimate, assign, control, and accept the work. If a package still has multiple owners, unclear output, or an estimate that is too uncertain to manage, it may need further decomposition.
Automatic WBS formulas included
The spreadsheet keeps its calculations visible and editable. Update planned hours, actual hours, progress, dates, status, and deliverables; the summary metrics and charts recalculate from the source worksheets.
Parent relationship → Level 1, 2, or 3Due Date − Start Date + 1Due Date − Reporting DatePlanned Hours × % CompleteTotal Earned Hours ÷ Total Planned HoursComplete, Overdue, Due Soon, or On TrackControl-account estimates and progress roll up from direct child work packages. The project dashboard excludes summary rows from effort totals, which prevents double counting across the hierarchy.
WBS levels and common structures
There is no universal number of WBS levels. A small project may need only three, while a complex program may use additional levels for products, sites, systems, releases, control accounts, and work packages.
The workbook uses a hybrid, deliverable-oriented example. You can rename the level 2 branches to fit construction, marketing, software, operations, consulting, events, compliance, product development, or internal improvement projects.
Work breakdown structure best practices
WBS in Excel vs. a task list or project software
A WBS, task list, and project schedule are related but different. Our guide to resource scheduling vs. project scheduling explains another important distinction once people and availability enter the plan. The WBS organizes the full project scope. A task list captures actions. A schedule adds sequence, dependencies, resources, and dates. Excel is useful for designing and agreeing on the hierarchy before moving into more connected execution. Teams that begin coordinating assignments across the WBS may also need project resource planning.
| Project need | Excel WBS template | Project management software |
|---|---|---|
| Design and review a scope hierarchy | Excellent fit | Good fit |
| Document work-package boundaries | WBS dictionary worksheet | Custom fields or documents |
| Build task dependencies and critical path | Manual or separate Gantt | Connected scheduling |
| Assign live work and collect updates | Manual workbook updates | Team workflows and notifications |
| Connect time, cost, risk, and resources | Separate worksheets or files | Integrated project data |
| Roll up multiple projects | Difficult to maintain | Portfolio dashboards |
KolApp becomes useful when the agreed WBS must connect to tasks, Gantt dependencies, resource capacity, availability, budgets, automation, dashboards, and portfolio reporting. The spreadsheet remains a practical starting point and an exportable scope reference. When several projects compete for the same people, multi-project resource management adds cross-project capacity and workload visibility.
How a WBS connects to resource and capacity planning
A work breakdown structure defines the scope, but it does not by itself prove that the delivery plan is achievable. After work packages have owners, estimates, and dates, teams should compare that demand with actual availability and capacity.
This is where resource scheduling becomes useful. A WBS package may require 80 hours of design work in a particular period, but the plan only works if the assigned designer has enough available capacity after other projects, meetings, and time off are considered.
For a quick capacity check, use the resource capacity calculator. Teams planning several projects at once can also use team capacity planning to compare available hours with the work represented by project plans and WBS packages.
Frequently asked questions
Is this work breakdown structure template for Excel free?
Yes. The .xlsx workbook is free to download and includes seven worksheets, sample data, formulas, dropdowns, conditional formatting, two dashboard charts, a WBS dictionary, a deliverables log, and a formula-driven hierarchy view.
What is a work breakdown structure?
A work breakdown structure is a hierarchical decomposition of the complete project scope. It organizes the project into progressively smaller elements until the team reaches manageable work packages that can be estimated, assigned, scheduled, monitored, and accepted.
What is the 100% rule in a WBS?
The 100% rule means that the WBS contains all work required to complete the parent scope. The child elements under a branch should collectively represent 100% of that parent without adding unrelated work or counting the same scope twice.
What is a WBS dictionary?
A WBS dictionary explains each WBS element beyond its short title. It can include scope description, owner, inputs, outputs, assumptions, exclusions, dependencies, estimates, acceptance criteria, approver, and other details needed to control the work.
What is the difference between a WBS and a project plan?
The WBS organizes what is included in the project scope. A project plan is broader and explains how the project will be delivered, including schedule, resources, budget, risk, communications, governance, quality, procurement, and change control.
How detailed should a WBS be?
Decompose until each work package has a clear output and owner and can be estimated, scheduled, monitored, and accepted. Avoid turning the WBS into a list of every daily action. The correct level depends on risk, complexity, duration, cost, and reporting needs.
Can I use this WBS template in Google Sheets?
You can upload the .xlsx file to Google Drive and open it in Google Sheets. Review formulas, tables, charts, dropdowns, and conditional formatting after conversion because spreadsheet applications can render some features differently.