WBS: How to Break a Project into Work Packages

A work breakdown structure (WBS) solves a practical problem: the many small tasks in a project can obscure deadlines, budgets, and oversight. While work lives in a site manager's memory and messenger chats, it may seem manageable. Add crews, deliveries, advance payments, and client changes, and the project starts to drift.

A WBS provides a framework for what must be delivered, how far to break it down, and where one result ends and another begins. It then becomes easier to build a schedule, estimate, purchasing list, milestones, and reports.

Here is how to build a WBS that people can use on site and during approvals, rather than file away as paperwork.

What is a WBS, and how does it differ from a schedule?

A WBS is a tree describing the entire project scope through deliverables and work components. The project goal—what you will hand over—sits at the top. Below it are major components, then work packages that you can estimate by time and cost, assign to someone, and accept against clear completion criteria.

Consider a bathroom renovation. “The bathroom is finished” sounds like one outcome, but it includes waterproofing, utility runs, an in-wall toilet frame, tiling, grout, sealants, plumbing fixtures, leak checks, and photos of concealed work. Without a breakdown, the schedule and budget are guesswork.

Do not confuse a WBS with an organizational structure. A WBS defines project scope; an organizational structure defines team roles and decision rights. For responsibilities, see 101's project management structure guide (in Russian).

When does a WBS help?

A WBS helps when a project becomes a chain of dependencies, approvals, and costs rather than one task. Its value appears at specific points of control.

For example, halfway through a project the client replaces the chosen tile with “something similar.” Without a WBS, the discussion becomes subjective: “a minor change,” “rework,” or “included in the price.” With a WBS, you can identify the affected component, changed work, materials to return, and effect on time.

• When preparing an estimate and showing its exact scope instead of vague descriptions.
• When building a schedule and finding dependencies between tasks.
• When hiring subcontractors and dividing responsibility by measurable deliverables.
• When controlling quality through acceptance against a list.
• When recording changes to scope, cost, and time.

For broader context, see 101's project management basics (in Russian) and overview of project management tools (in Russian).

How do you build a WBS?

Start with a deliverable you can accept, rather than listing every action. Break it into smaller outcomes until each one can be estimated and assigned. This process works for construction, renovation, manufacturing, and project services.

1. Describe the final deliverable in one sentence: what you will hand over, its scope, and constraints such as rooms, engineering systems, finish level, and included equipment.
2. Divide the project into 5–12 major components based on outcomes: preparation, demolition, rough work, engineering systems, finish work, fittings, and handover.
3. For each component, describe intermediate outcomes that can be accepted, such as “screed completed,” “electrical panel assembled,” “utility runs installed,” or “ventilation ducts fitted.”
4. Break those outcomes into work packages. For each, identify quantity, duration, materials, and contractor.
5. Set completion criteria, such as measurements, records of concealed work, photos, pressure tests, residual-current device tests, joints, or alignment.
6. Check completeness with the 100% rule. Include everything needed for the result, including meetings, approvals, purchasing, inspections, and as-built documentation.
7. Assign WBS codes such as 1.0, 1.1, and 1.1.1, and reuse them in estimates, schedules, purchasing, and reports.

How detailed should the breakdown be?

A common mistake is breaking work down to “each pass with a putty knife.” The WBS then becomes an endless list that nobody updates.

Stop at an element you can estimate in time and cost, assign to someone, and accept against a criterion. If it cannot be estimated, it may still be too broad. If it cannot be accepted, it may describe an activity without an outcome.

Check whether the structure works on site:

• Each element has a measurable deliverable, ideally expressed as a noun rather than a verb.
• One person is accountable for handing over the result.
• The materials and documents needed are clear.
• Elements do not overlap: the same work does not appear in two branches.

For example, electrical work often appears under rough work, finishing, and fittings. Nobody then owns the overall result, while time and cost move between branches. A clearer approach is one “Electrical work” branch, divided into stages and then deliverables.

Common WBS mistakes

Mistakes often become visible only after a dispute starts: the client thinks something was included, while the contractor thinks it was extra. A structure drawn up as a formality offers little help then.

• Mixing outcomes and activities: “do,” “check,” or “approve” without stating what the result will be.
• Duplicating work across branches, counting the same scope twice in cost or time.
• Leaving out management work: purchasing, logistics, approvals, acceptance, quality control, and as-built documentation.
• Using uneven levels of detail: tiny steps in one branch and three broad items in another.
• Creating the WBS once and forgetting it. Update the tree when site conditions change so it remains a reliable record of scope.

Connecting a WBS to estimates, schedules, and money in construction and renovation

Connect the project structure to three working documents: an estimate, a schedule, and cost tracking. Otherwise, the tree remains a diagram with little value on site.

1) WBS → estimate. Lower-level elements become calculation items with clear quantities, units, prices, and materials. A consistent digital price list organized along WBS lines reduces ambiguity and helps explain the scope.

2) WBS → schedule. Components and outcomes become stages with dates and dependencies. Site managers and crew leads see milestones rather than one overall deadline.

3) WBS → change control. Attach a client change to a WBS branch, then recalculate the elements added or removed and their effect on time and budget.

In the 101 app, you can support a WBS with price lists and estimates: organize work in a price list, then build estimates for each site. See 101's articles on the estimate builder (in Russian), online estimates (in Russian), preparing an estimate yourself (in Russian), and price-list updates (in Russian).

Consider a client who asks for underfloor heating and moves electrical outlets halfway through finishing. With a structured WBS and price list, you can connect the recalculation to specific estimate and schedule changes. The “Electrical work” and “Floors” branches change, the estimate is rebuilt, dependencies are added for wet work, and the costs do not disappear into “miscellaneous expenses.”

If you want to organize your work and connect it with estimates and cost tracking, a presentation of the 101 app can show which figures should agree across the work structure, calculations, and actual costs.

A WBS helps everyone agree on project scope before disputes arise. Clear deliverables and boundaries make deadlines, acceptance, and finances easier to manage.