How to Create a Work Breakdown Structure (WBS) With Examples

Every project plan starts with the same question: what actually has to get done? A work breakdown structure (WBS) is the tool that answers it. Instead of starting with dates and a blank Gantt chart, you start by breaking the whole project into smaller pieces of work until each piece is clear enough to assign, estimate and track.

This guide walks through what a WBS is, how to build one step by step, and how it looks in practice for a construction job, a healthcare operations project and a small business launch. At the end there is a checklist you can use before you turn your WBS into a schedule.

What is a work breakdown structure?

A work breakdown structure is a hierarchical list of everything a project has to deliver. The project sits at the top. Underneath it are the major deliverables or phases, and under each of those are smaller pieces of work, all the way down to tasks that one person or team can own.

Two ideas make a WBS useful:

• It is about deliverables, not activities alone. The upper levels describe outcomes ("Foundation", "Staff training", "Online store"), and the lower levels describe the work that produces them.
• The 100% rule. The children of any item should add up to all of the work in that item, no more and no less. If something is not in the WBS, it is not in the project.

The smallest pieces at the bottom of a WBS are usually called work packages. A good work package is small enough that you can estimate its duration and cost with reasonable confidence, and give it one clear owner.

Why build a WBS before the schedule?

It is tempting to open a scheduling tool and start drawing bars. The problem is that a schedule built that way tends to miss work. A WBS forces you to think through scope first, which pays off in several ways:

• Fewer forgotten tasks. Breaking each deliverable down makes gaps visible, such as permits, approvals, testing or handover.
• Better estimates. It is much easier to estimate "install kitchen cabinets" than "finish the renovation".
• Clear ownership. Each work package can be assigned to a person or team, so nothing sits in a grey zone.
• A cleaner schedule. Once the work is listed, adding dates, dependencies and milestones becomes a sequencing exercise rather than a guessing game.
• Easier scope conversations. When a client or manager asks for something new, you can point to the WBS and discuss what is being added.

How to create a work breakdown structure in 6 steps

1. Define the final outcome

Write one sentence that describes what "done" means for the project. For example: "A renovated two-bathroom apartment, inspected and handed over to the owner." This sentence becomes the top level of your WBS and keeps the breakdown anchored to a real result.

2. Choose how to split the first level

There are two common ways to organise level one:

• By deliverable: the main things you hand over (structure, electrical, plumbing, finishes).
• By phase: the stages of the project (planning, preparation, execution, close-out).

Either works. Pick the one your team already thinks in. Field teams often prefer deliverables or trade packages, while office projects often read better by phase. Just avoid mixing both styles on the same level, because that is where overlaps and gaps creep in.

3. Break each item down until it is manageable

Take each level-one item and ask, "What has to happen for this to be complete?" Write the answers as the next level. Repeat until the pieces are small enough to estimate and assign. A practical stopping point is a piece of work that:

• has one owner (a person or a team),
• produces something you can check, and
• fits within your normal reporting cycle, for example a few days to two weeks.

Most projects need only three or four levels. If you are going deeper than that, you may be turning the WBS into a to-do list, which is better handled with subtasks during execution.

4. Name items clearly

Use nouns for deliverables and short verb phrases for work packages: "Bathroom 1 tiling" or "Install floor tiles, bathroom 1". Avoid vague labels like "Misc" or "Other". If an item cannot be named clearly, it usually means the scope is not clear yet, and that is worth a conversation before work starts.

5. Check it with the 100% rule

Walk through each branch and ask two questions. Does the work below this item cover everything this item requires? Is anything listed here that is actually outside the project? This is a good moment to involve the people doing the work. They will spot missing steps such as site cleanup, test runs, documentation or training far faster than a planner working alone.

6. Add owners, estimates and a numbering scheme

Give each work package an owner and a rough duration. Many teams also number the items (1, 1.1, 1.1.1) so they can be referenced easily in meetings and reports. Some teams keep a short WBS dictionary as well: a line or two per work package describing what is included, what is excluded and how completion is checked.

Work breakdown structure examples

The examples below are illustrative outlines, not templates from a real project. Use them as a starting point and adapt them to your own scope.

Construction: small commercial fit-out

• 1. Pre-construction: site survey, drawings approval, permits, material orders
• 2. Demolition and preparation: strip-out, waste removal, protection of existing finishes
• 3. Building services: electrical first fix, plumbing first fix, HVAC ductwork
• 4. Partitions and ceilings: stud walls, boarding, suspended ceiling grid
• 5. Finishes: painting, flooring, joinery, second fix electrical and plumbing
• 6. Handover: snagging, cleaning, inspections, documentation for the client

Notice that inspections and handover documents get their own branch. Those are the items that most often go missing when a schedule is drawn straight from memory.

Healthcare operations: opening a new outpatient clinic room

• 1. Space readiness: room layout, furniture, cleaning and signage
• 2. Equipment: procurement, delivery, installation, functional checks
• 3. Staffing: rota planning, role assignments, onboarding sessions
• 4. Processes: patient flow, booking setup, supply restocking routine
• 5. Go-live: walkthrough, first-week review, open issues list

For an operations project like this, the WBS also helps different departments see exactly which parts they own, which makes handoffs between facilities, procurement and clinical teams easier to plan.

Small business: launching an online store

• 1. Product catalogue: product list, photos, descriptions, pricing
• 2. Store setup: platform choice, theme, payment and shipping settings
• 3. Operations: packaging, returns policy, stock tracking
• 4. Marketing: launch email, social posts, launch offer
• 5. Launch and review: test orders, go-live, first-month review

From WBS to Gantt chart

Once your WBS is agreed, turning it into a schedule is straightforward:

• Top-level items become tasks or phases in your plan, and work packages become subtasks underneath them.
• Add start and due dates using the estimates you gathered.
• Link the work with dependencies. Use Finish-to-Start when one piece cannot begin until another ends, Start-to-Start when two pieces can begin together, and Finish-to-Finish when two pieces need to wrap up together.
• Mark milestones for key moments such as permit approval, equipment delivery or go-live.
• Assign owners so each person sees what is theirs.

This is also the right time to look at risk and budget. Each branch of the WBS is a natural place to ask what could go wrong and how much it will cost, which makes your risk register and budget line items line up with the actual work.

Common WBS mistakes to avoid

• Going too deep. A WBS with hundreds of tiny items is hard to maintain. Stop at work packages and handle the fine detail as subtasks or daily tasks.
• Listing people or departments instead of work. "Electrician" is not a deliverable. "Electrical first fix" is.
• Forgetting project management work. Meetings, reporting, approvals and handover take real time and belong in the plan.
• Building it alone. The people who do the work know the steps. A short review session with them usually catches the biggest gaps.
• Never updating it. When scope changes, update the WBS first, then the schedule, so the two stay in sync.

WBS checklist

• The top level describes a clear, finished outcome.
• Level one is split consistently, either by deliverable or by phase.
• Every branch passes the 100% rule.
• Each work package has one owner and a rough duration.
• Inspections, approvals, testing and handover are included.
• Items are clearly named and numbered.
• The team doing the work has reviewed it.
• It is ready to become tasks, subtasks, dependencies and milestones in your schedule.

A work breakdown structure takes a little time up front, but it gives you a plan you can trust: one where the schedule, the budget and the risks all trace back to the same list of work.