Question 1

What is a WBS and why do I need one before building a schedule?

Accepted Answer

A Work Breakdown Structure (WBS) is a deliverable-oriented decomposition of all the work required to complete a project. It answers "what must we produce?" before you ask "when will we do it?" Building a WBS before a schedule prevents the common mistake of creating a timeline with missing work packages. The WBS sheet uses hierarchical WBS Codes (1.0, 1.1, 1.1.1) to show parent-child relationships between phases, deliverables, and work packages.

Question 2

What is the 100% rule and how do I apply it?

Accepted Answer

The 100% rule states that your WBS must capture 100% of the project scope — all deliverables, all work, all outcomes. Nothing outside the WBS should be needed to complete the project, and nothing inside the WBS should be unnecessary. On the WBS sheet, review your decomposition from bottom up: if you completed every work package (Level 3 items), would the project be done? If the answer is no, you have missed something. The Help sheet includes a 100% rule checklist.

Question 3

How deep should I decompose my WBS? How many levels?

Accepted Answer

Decompose until you reach work packages that are: (1) estimable — you can confidently estimate hours and cost, (2) assignable — one person or small team can own it, (3) measurable — you can tell when it is done. This is typically 3-4 levels. The WBS sheet supports 50 rows, so plan your depth accordingly. Avoid over-decomposing — tracking 150 work packages across 5 levels creates administrative burden without adding planning accuracy.

Question 4

How do the WBS Codes create the hierarchical structure?

Accepted Answer

The WBS Code column uses dotted decimal notation: 1.0 is a top-level phase, 1.1 is a child deliverable under 1.0, 1.1.1 is a work package under 1.1. This numbering system makes parent-child relationships immediately visible — even without indentation, you can read the codes and understand the hierarchy. When presenting the WBS, you can group or filter by code prefix (e.g., everything starting with "1." is Phase 1).

Question 5

How does the WBS connect to cost estimation and budgeting?

Accepted Answer

The Estimated Hours and Estimated Cost columns on the WBS sheet are designed for bottom-up estimating. Estimate each work package (the lowest level of decomposition), then sum upward — work package estimates roll up to sub-deliverables, which roll up to phases, giving you a total project estimate grounded in actual work decomposition. This is far more accurate than top-down estimating, which often misses hidden work.

Question 6

Can I link this WBS to a Gantt chart?

Accepted Answer

Yes — the WBS is designed as the precursor to scheduling. After completing your WBS sheet, each work package (Level 3 row) becomes a task on your Gantt chart. Copy the WBS Code, Task Name, Owner, Start Date, End Date, and Estimated Hours columns into the PlanoraNest Gantt Chart template or any scheduling tool. This workflow — WBS first, schedule second — is the professional standard for project planning and dramatically reduces the risk of missed work.

Sheet	What it does
Start Here	Quick-start guide explaining the WBS concept, how to structure your decomposition (phases > deliverables > work packages), and tips for running a WBS session with your team.
WBS	The core WBS sheet with 9 columns and 50 task rows. Columns include: WBS Code (hierarchical numbering like 1.0, 1.1, 1.1.1), Task/Deliverable Name, Description, Assigned To/Owner, Estimated Hours, Estimated Cost, Start Date, End Date, and Status. A Project Start date field anchors the timeline. The hierarchical WBS Code structure creates visual parent-child relationships — main phases (1.0, 2.0, 3.0), sub-deliverables (1.1, 1.2), and work packages (1.1.1, 1.1.2). Use the built-in indentation and grouping to see your project structure unfold.
Help	31-row reference sheet covering WBS best practices, the 100% rule (your WBS must capture 100% of project scope), how deep to decompose, and how to estimate hours and costs at the work package level.
About	Template credits, version info, and terms of use.

Work Breakdown Structure Spreadsheet Excel Template

Who it's for

What's included — sheet-by-sheet

Preview

Preview 1

Preview 3

Preview 4

How to use this template

Works with

Frequently asked questions

How it works

Customer reviews