Key takeaways
- A WBS decomposes deliverables and scope, not the org chart and not the payment schedule.
- Roll-ups follow the tree.
What a WBS is — and is not
A WBS decomposes deliverables and scope, not the org chart and not the payment schedule. "Concourse B — structural steel — sequence 3" is a WBS node; "Subcontractor invoices" is not. Activity codes (phase, area, responsibility, bid package) complement the WBS by letting you slice the same activities along other dimensions without distorting the tree.
Why the structure quietly shapes oversight
Roll-ups follow the tree. If the WBS does not isolate the central plant, no report will ever show the central plant slipping — the variance will smear across a parent node. Earned value, progress curves, and area-level dashboards are all only as sharp as the structure underneath them. Reviewing the WBS at baseline is cheap; discovering at month eighteen that the schedule cannot answer the board’s question is not.
Sources and scope
Follow the reference trail.
This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.
10S-90: Cost Engineering TerminologyAACE International · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01DoD Earned Value Management System Interpretation GuideU.S. Department of Defense · checked 2026-08-01