Project Management

Work Breakdown Structure

Also known as: WBS

A hierarchical decomposition of a project into deliverables and work packages used for estimating and scheduling.

A Work Breakdown Structure is the hierarchical breakdown of a project into progressively smaller deliverables and work packages, ending at the level where each package can be estimated, scheduled, and assigned to a single party. The top of the hierarchy is the project itself; intermediate levels group related scope (sitework, structure, envelope, MEP, finishes); the bottom level is the work package, the unit at which budgets and schedules are managed. WBS structure typically follows CSI MasterFormat divisions or a project-specific custom hierarchy.

WBS is the foundation for both estimating and scheduling. The estimator builds the cost estimate by pricing each work package. The scheduler builds the CPM schedule by sequencing the same work packages with durations and logic. The contract's schedule of values mirrors the WBS so that pay applications track to the same structure used for budgeting and execution. Inconsistent WBS across estimating, scheduling, and billing is one of the most common reasons project tracking falls apart on commercial work.

Frequently asked questions

How granular should a WBS be?+

Each work package should be small enough to estimate, schedule, and assign to a single party (typically 40 to 200 hours of work or $5K to $100K in cost). Too granular wastes management overhead; too coarse hides variance. CSI MasterFormat-aligned WBS typically runs 50 to 200 work packages on a mid-size commercial project.

What is the difference between WBS and schedule of values?+

WBS is the hierarchical breakdown of project scope. Schedule of Values is the financial breakdown used for progress billing, derived from the WBS. Most commercial contracts require the SOV to mirror the WBS so estimating, scheduling, and billing all track to the same structure.

How does WBS connect to CSI MasterFormat?+

CSI MasterFormat is one common organizing principle for WBS. The project-level groupings often follow MasterFormat divisions; the work-package level adds project-specific detail. Some contractors use UniFormat (system-based) instead, especially on early-design estimating where MasterFormat detail isn't available yet.

Related terms