Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) is a hierarchical decomposition of a contract's total scope of work into progressively smaller, manageable components, elements, subsystems, work packages, and planning packages, that together represent 100% of the work required to complete the contract.

What is a Work Breakdown Structure?

The WBS is the foundational organizing structure for program planning, scheduling, cost estimating, and performance reporting on government contracts. MIL-STD-881 (for defense programs) and commercial project management standards define how WBSs should be structured for different program types. The WBS organizes work by product, deliverable, or functional area, not by organization or time period.

A typical WBS for a defense system program might decompose at the first level into major system elements (e.g., System Integration, Hardware, Software, Training, Systems Engineering), then further decompose each element into subsystems, components, and ultimately work packages, the lowest level at which cost and schedule are planned and tracked. Work packages have discrete start and end points, clear deliverables, and responsible control account managers (CAMs).

On contracts requiring an Earned Value Management System (EVMS), the WBS is the organizing structure for the Performance Measurement Baseline (PMB). Every dollar of contract budget is allocated to a WBS element, and earned value is reported at the control account level of the WBS. Contractors must submit WBS-aligned cost and schedule reports (the Cost/Schedule Status Report, CSSR, or the Integrated Program Management Data Item Description, IPMDAR) to the government on a periodic basis.

Why the WBS matters for government contractors

A well-structured WBS prevents scope gaps, enables accurate cost estimating at the proposal stage, and provides the framework for tracking actual performance against plan throughout contract execution. Poor WBS structure is a leading cause of cost variance and scope disputes on government contracts.

Example

A prime contractor developing a new military communications satellite builds a WBS with three top-level elements: Space Segment, Ground Segment, and Program Management. The Space Segment decomposes into Payload, Bus, and Integration and Test. Each subsystem decomposes into components, and components decompose into work packages assigned to individual engineers or teams. The WBS becomes the backbone of the Integrated Master Schedule and the cost accounting structure for EVMS reporting.

Frequently Asked Questions

What is the difference between a WBS and a project schedule?

The WBS defines what work will be done, the total scope decomposed into elements. The schedule defines when each element will be performed and in what sequence. The Integrated Master Schedule uses the WBS as its organizing structure, assigning calendar dates to each work package.

Is a WBS required on all government contracts?

WBSs are required on DoD contracts requiring EVMS and are strongly recommended by program management standards for any complex program. Fixed-price commercial contracts may not require a formal WBS, though most professional program managers develop one internally for planning and control purposes.

Who owns the WBS on a government contract?

The WBS is typically developed by the contractor and approved by the government. For defense programs, MIL-STD-881 provides a standard WBS template for each major system category (aircraft, ship, missile, space system, etc.) that contractors are expected to follow unless a tailored WBS is specifically approved.

What is a WBS dictionary?

A WBS dictionary is a companion document to the WBS that provides a narrative description of each WBS element, what work is included, what deliverables are produced, what is explicitly excluded, and what the boundaries are between adjacent elements. A well-written WBS dictionary prevents scope ambiguity and disputes over who is responsible for specific work.