Work Breakdown Structure Template Permalink

Q: What is a work breakdown structure?

A work breakdown structure, or WBS, is a hierarchical split of a project's total scope into smaller and smaller pieces, until every piece at the bottom is small enough for one person to own, estimate and deliver. The top level holds the major deliverables or areas of the project, the middle levels break each one into components, and the bottom level holds the work packages that actually get scheduled, costed and assigned. Every item carries a number such as 1.2.3 that shows exactly where it sits in the tree. A WBS describes what has to be produced, not when, so it comes before the schedule rather than replacing it. Once the breakdown is agreed, the estimates on the leaves add up to the project budget and the leaves themselves become the tasks on the plan.

Q: What are the three levels of a work breakdown structure?

Level 1 is the major areas or deliverables of the project, such as Internal, Foundation and External on a building fit-out. Level 2 splits each area into components, such as Electrical and Plumbing under Internal. Level 3 holds the work packages, the smallest items that are still meaningful to estimate and assign, such as Rough-in electrical or Install the terminal. Larger projects sometimes go a level or two deeper, but three is enough for most teams, and a fourth level is often a schedule of steps rather than a breakdown of scope. In the Quire template, level 1 is a section, level 2 is a root task, and level 3 is a subtask, numbered 1.1.1 through 3.2.5 so the position of every item is visible in its name.

Q: What is the 100 percent rule in a WBS?

The 100 percent rule says that the work packages under any item must add up to exactly 100 percent of that item's scope, no more and no less. Nothing outside the scope should appear in the breakdown, and nothing inside the scope should be missing from it. The rule applies at every level: the level 2 components under Internal must cover all of Internal, and the level 3 work packages under Plumbing must cover all of Plumbing. In practice it is a review check rather than a formula. Walk each parent and ask whether finishing every child would finish the parent. If the answer is no, a work package is missing. If finishing the children would also produce something the parent never asked for, the extra item belongs somewhere else or nowhere.

Q: How do I create a work breakdown structure in Quire?

Create a section for each level 1 area, add a root task under it for each level 2 component, and add subtasks under each root task for the level 3 work packages. Put the WBS number at the start of every name, such as 1.2.1 Rough-in plumbing, so the hierarchy reads in any view. Then add custom fields for the numbers you estimate. The Quire template uses a Money field called Budget, a percentage Number field called Effort, a Select field called Milestone and a Formula field called Risk. Fill in the estimates on the work packages only, link the order of the work with task dependencies, and switch to Table view to see every item with its numbers in one grid. The ready-made template has all of this set up with a building fit-out as the sample.

Q: How deep should a work breakdown structure go?

Stop breaking an item down once it has one owner and one estimate. That is the point at which the item is a work package: one person can be accountable for it, and one budget figure and one effort figure describe it honestly. Splitting further usually produces a list of steps with dates attached, which is a schedule, not a breakdown, and it multiplies the number of rows to estimate without making any estimate more accurate. Splitting less leaves items too large to cost with confidence or to assign to a single person. Three levels suit most projects. Go deeper only where a work package is still too big for one owner, and do it locally rather than adding a level to the whole tree.

Q: How do I track WBS budget and effort in Quire?

Add a Money custom field for Budget and a percentage Number field for Effort, then fill both in on the level 3 work packages only. Parent rows are containers, so leave them empty rather than typing a total that will drift out of date. Switch to Table view to see every work package with its numbers beside it, and turn on Sum under the Budget column so the bottom of the table shows the total project budget. Give Effort conditional colors, such as green up to 30 percent and red above 80, so overloaded items stand out without reading the numbers. If you also want subtotals on the level 2 rows, add a Formula field such as SUM(descendants.{Budget}) and each parent will add up everything beneath it.

Q: How does the Risk formula in the template work?

Risk is a Formula field that reads the Budget field on the same task and returns a label. The formula is Budget >= 200 ? "High 🔴" : "Low 🟢", so any work package with a budget of 200 or more is flagged High and everything below it is Low. Nobody types a value into Risk. It recalculates the moment Budget changes, which means the flag can never fall out of step with the estimate. The threshold of 200 suits the small sample figures in the template. For a real project, edit the formula on the field and raise the threshold to whatever amount your team treats as needing a closer look, and every row re-scores at once. Sort or filter by Risk before a budget review to start with the items that carry the most money.

Q: Is there a ready-made work breakdown structure template in Quire?

Yes. Quire provides a ready-made Work Breakdown Structure project at quire.io/w/Quire_Work_Breakdown_Structure that you can duplicate into your own workspace. It breaks a building fit-out into three sections, six level 2 components and twenty level 3 work packages, numbered 1.1.1 through 3.2.5. It comes with four custom fields: Budget, Effort, Milestone and a Risk formula that flags any work package at 200 or more. Work packages carry dependencies, approval states and assignees, two sublists collect the high-risk items and the turnover checklist, and a How to use this template document explains each part. Rename the sections to your own level 1 areas, replace the work packages, fill in the estimates, and the formula and table totals do the rest.

Use this template to break a project down into numbered levels in Quire, from the major areas at the top to work packages small enough for one person to own and estimate. The project opens in Table view, where every work package shows its budget, effort and milestone, and a formula flags the expensive ones.

the work breakdown structure template in quire table view, with numbered sections, components and work packages and their budget, risk, effort and milestone

You can visit the Work Breakdown Structure project and duplicate it to your workspace, so you don’t need to build everything from scratch.

You can also explore more ready-to-use templates to speed up your workflow.

Understand a Work Breakdown Structure

A work breakdown structure (WBS) splits the whole scope of a project into levels. The top level names the major areas, the middle level names the components inside each area, and the bottom level holds the work packages that get estimated, assigned and scheduled. Each item carries a number such as 1.2.3, which tells a reader exactly where it sits in the tree.

A WBS answers “what has to be produced”, not “when”. It comes before the schedule, and the schedule is built from its bottom row.

The 100 Percent Rule

The children of any item must cover all of that item’s scope, and nothing beyond it. Finish every work package under 1.2 Plumbing and plumbing is done. If something would still be missing, a work package is missing. If finishing them would also produce something plumbing never asked for, that item belongs elsewhere.

Lay Out the Breakdown

The sample is a building fit-out in three levels, and each level maps to a different Quire structure.

Level	Quire structure	Example
1. Area	Section	1. Internal, 2. Foundation, 3. External
2. Component	Root task	1.1 Electrical, 1.2 Plumbing, 2.1 Excavate
3. Work package	Subtask	1.1.1 Rough-in electrical, 1.2.3 Test and clean

Three sections hold six components and twenty work packages between them, numbered 1.1.1 through 3.2.5.

the three levels of the work breakdown structure template in quire list view, with numbered sections, components and work packages

Collapse the components to read the breakdown at level 2, or expand them all to check level 3.

Numbering

The WBS number is part of each task name, so the hierarchy reads the same in List, Table, Board and Timeline view, in search results, and in an export. When you restructure, renumber. The numbers are the only thing that tells a reader how the pieces relate once a task is seen outside its tree.

Estimate in Table View

Table view is only available in the Professional, Premium, Enterprise plans. More information can be found on our pricing page.

Four custom fields carry the estimates, and Table view puts them beside every work package.

the work breakdown structure in quire table view with budget, effort, milestone and risk columns

Field	Type	What it holds
Budget	Money	The cost estimate for one work package
Effort	Number (percent)	How loaded the work package is, from 0 to 100 percent
Milestone	Select	The gate the work package belongs to: Design, Construction, Inspection or Turnover
Risk	Formula	🔴 High or 🟢 Low, calculated from Budget

Estimate on the level 3 work packages only. Level 1 and level 2 rows are containers, so their figures come from what sits beneath them, never from a number typed on top.

Effort answers “how loaded is this”, not “how many hours”. It carries conditional colors: green up to 30 percent, amber to 50, orange to 80, and red above that, so an overloaded work package shows up before anyone reads the figure.

Note: The Milestone column is a Select field that labels which gate a work package belongs to. It is separate from Quire’s built-in milestones, which mark dates on the timeline. Use the field to group and filter the breakdown, and add real milestones if you also want the gates drawn on the schedule.

The Risk Formula

Risk is one line, and nobody types into it.

Budget >= 200 ? "High 🔴" : "Low 🟢"

A work package with a budget of 200 or more is High, everything else is Low. The formula recalculates as soon as Budget changes, so the flag cannot drift away from the estimate. In the sample, nine of the twenty work packages are flagged, led by 3.1.3 Install tile at $752.

The threshold of 200 suits the small sample figures. For a real project, edit the formula on the field and set the amount your team treats as worth a second look. Every row re-scores at once.

Totals

Switch on Sum under the Budget column by hovering over the bottom row of the table, and that row becomes the total project budget. Group the table by Milestone to see what each gate costs, since every group gets its own total. Learn more about column calculations.

Tip: Want subtotals on the level 2 rows as well? Add a Formula field with SUM(descendants.{Budget}). Each component then adds up every work package beneath it, and the figure updates whenever a leaf changes. See commonly used formulas for more.

Sequence the Work

Task dependency is only available in Professional, Premium, Enterprise plan. More information can be found at our pricing page.

The breakdown says what, and task dependencies say in what order. In the sample, 1.1.1 Rough-in electrical comes before both plumbing rough-in and fixtures, and 1.2.2 Set plumbing fixtures comes before 2.1.1 Pour concrete, which comes before 2.1.2 Cure & strip forms.

Set a predecessor from the task’s detail panel, then switch to Timeline view to check that the chain reads in the order the work actually happens.

plumbing and foundation work packages in quire timeline view at the month scale, linked by dependency lines

Only the work packages under 1. Internal and 2.1 Excavate carry dates in the sample. The rest are estimated but not yet scheduled, which is how a WBS usually looks before the schedule is built from it.

Sign Off the Estimates

The Approval feature is only available in Premium and Enterprise plan. More information can be found at our pricing page.

Work packages carry approval states, so an estimate can be awaiting, approved, changes requested or rejected while the work itself is still To-do. Approval is sign-off on the estimate. Status is the progress of the work. Keeping them apart means a rejected budget never gets mistaken for unfinished work.

In the sample, 2.1.1 Pour concrete has been rejected, and 1.2.1 Rough-in plumbing has changes requested on its $350 estimate. Filter by approval state before a review to see what still needs a decision.

the work breakdown structure in quire table view filtered to request changes and rejected approval states, showing only the estimates that still need a decision

Pull Cross-Cuts with Sublists

The tree groups work by area. Two sublists cut across it.

Sublist	Collects	Use it for
🔴 High risk	Every work package the Risk formula flags	The list to read before a budget review
🏁 Turnover gate	Everything set to the Turnover milestone	The handover checklist

Both ship as fixed lists. To keep them up to date on their own, right-click each sublist, select Edit tasks, and set pre-set filter conditions: Risk is High 🔴 for the first, Milestone is Turnover for the second. New work packages that match are then added automatically.

Keep the Breakdown Honest

Two habits keep a WBS useful after the first week.

Break down until a work package has one owner and one number, then stop. A fourth level is usually a schedule pretending to be a breakdown.
Renumber when you restructure. A task called 1.2.3 that now lives under 2.1 misleads everyone who reads it.

When you adapt the template:

Different kind of project? Rename the three sections to your own level 1 areas, such as Design, Build and Launch for a product, or the deliverables of a client engagement
Phase-based instead of deliverable-based? Use the phases as level 1 and keep the Milestone field for the gates within each phase
Need hours rather than load? Add a Number field for estimated hours next to Effort, and keep Effort for the at-a-glance color

Start Your Breakdown

Everything on this page can be built by hand. The template is the same thing already assembled: three sections, six components, twenty work packages, four custom fields including the Risk formula, dependencies, approvals, two sublists and the how-to document.

Duplicate the Work Breakdown Structure project into your workspace, then:

Rename the three sections to your own level 1 areas.
Replace the components and work packages with your own, numbering each one as you go.
Fill in Budget and Effort on every work package.
Set Milestone on each work package to the gate it belongs to.
Link the order of the work with dependencies, then check the chain in Timeline view.
Raise the Risk threshold in the formula to suit your project’s figures.

the fields table in the how to use this template document of the work breakdown structure template

Point your team at the How to use this template document. It keeps the field definitions and the two habits inside the project, for anyone who does not read this guide.

If the project still needs a charter before it is broken down, start with the Project Charter template. To track what could go wrong on the expensive work packages, pair the breakdown with the Risk Register template.

Frequently Asked Questions

What is a work breakdown structure?

A work breakdown structure (WBS) splits a project’s whole scope into numbered levels, until each item at the bottom is small enough for one person to own and estimate. It describes what has to be produced, and the schedule is built from its bottom level.

What are the three levels of a work breakdown structure?

Level 1 is the major areas, level 2 the components inside each area, and level 3 the work packages that get estimated and assigned. In the Quire template these are sections, root tasks and subtasks, numbered 1.1.1 through 3.2.5.

What is the 100 percent rule in a WBS?

The children of any item must cover all of its scope and nothing beyond it. If finishing every work package under a component would still leave something undone, a work package is missing.

How do I create a work breakdown structure in Quire?

Use a section for each level 1 area, a root task for each level 2 component, and subtasks for the level 3 work packages, with the WBS number at the start of each name. Add custom fields for Budget and Effort and fill them in on the work packages.

How deep should a work breakdown structure go?

Stop once an item has one owner and one estimate. Three levels suit most projects, and a fourth level is usually a list of scheduled steps rather than a breakdown of scope.

How do I track WBS budget and effort in Quire?

Fill in a Money field for Budget and a percentage field for Effort on the work packages only, then turn on Sum under the Budget column in Table view for the project total. A SUM(descendants.{Budget}) formula adds subtotals to the parent rows.

How does the Risk formula in the template work?

It reads Budget and returns High 🔴 for 200 or more and Low 🟢 for anything less. It recalculates whenever Budget changes, and you can raise the threshold by editing the formula on the field.

Is there a ready-made work breakdown structure template in Quire?

Yes. Visit the Work Breakdown Structure project and duplicate it to your workspace to get the three levels, twenty sample work packages, four custom fields including the Risk formula, dependencies, approvals and two sublists.

Please contact us if you need more assistance.