b2KIT

Work Breakdown Structure Builder

Build hierarchical WBS with task decomposition, cost roll-up, and responsibility assignment in tree diagram format.

Tested tool guide Tested browser tools Checked August 16, 2026

What Work Breakdown Structure Builder does, with a checked example

This tool builds a project's task hierarchy as an editable tree: you add phases, break each into work packages, and break those into leaf-level tasks, each optionally tagged with a cost and an owner. It assigns decimal WBS codes (1, 1.1, 1.2, 2, 2.1...) automatically as you nest items, and sums cost upward so every parent shows the total of its children. The most common surprise is entering a cost on a task that also has children - decompose fully before pricing, since the roll-up is built from leaf values, not whatever you type at a parent level.

Worked example

A concrete input and expected output from the current implementation.

Input

Website Launch
1 Design
  1.1 Wireframes - $800
  1.2 Visual Design - $1200
2 Development
  2.1 Frontend - $3000
  2.2 Backend - $4000
3 Testing - $1500

Expected output

1 Design = $2,000 (1.1 $800 + 1.2 $1,200)
2 Development = $7,000 (2.1 $3,000 + 2.2 $4,000)
3 Testing = $1,500
Project total = $10,500

Each parent's cost is the sum of its own leaf children ($800+$1,200=$2,000 for Design; $3,000+$4,000=$7,000 for Development), and the project total is the sum of all top-level nodes: $2,000 + $7,000 + $1,500 = $10,500.

How the result is produced

1

Decimal WBS numbering

Every node you create gets a code based on its position: top-level items are 1, 2, 3; a child of item 2 becomes 2.1, 2.2, and so on for deeper levels. Codes update automatically when you add, delete, or drag-reorder items, so a task's number reflects its current position in the tree, not when it was created.

2

Cost and ownership roll-up

Cost and a responsible-party field are entered at the leaf (lowest) level of each branch. The tool sums leaf costs up through every ancestor to the project root, so a mid-level work package shows the combined cost of everything beneath it without you re-entering totals by hand as the tree changes.

Good uses

  • Breaking a fixed-price client project into numbered work packages before writing a cost-based statement of work
  • Structuring a renovation or build-out into phases and tasks so each contractor's portion rolls up to a checkable subtotal
  • Preparing a numbered task hierarchy with named owners for a grant deliverable or internal PMO report that requires WBS codes

Limits and checks

  • If you put a cost on a parent node that also has priced children, that parent figure is not part of the automatic roll-up logic - only leaf costs are summed, so a parent-level number can be misleading if left in place
  • WBS codes are positional and shift when you reorder or delete items, so any external document (contract, invoice) that cites a specific code like 2.1 needs to be re-checked after edits, not assumed stable
  • The tree models structure, cost, and responsibility only - it does not schedule dates, sequence dependencies, or compute a critical path, so it cannot substitute for a Gantt or project-scheduling tool

Common questions

Can a task have more than one owner?

Not confirmed - the responsibility field in this style of WBS builder is typically a single value per leaf task. If you need shared ownership, the common workaround is splitting the task into separate leaf items, one per owner, so each keeps its own cost and assignment.

Does this calculate the project schedule or timeline?

No. This tool builds the task hierarchy with cost roll-up and responsibility assignment only - it does not assign start/end dates, sequence tasks, or compute a critical path. You would need a separate scheduling tool for that.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools