Work Breakdown Structure: 100% Rule, Dictionary, Examples
A work breakdown structure (WBS) is a hierarchy that divides a project’s total scope into deliverables and then into work packages small enough to estimate, assign and track. Its governing test is the 100% rule: every element is the sum of its children, nothing in scope is missing, and nothing outside scope appears. Each element is then defined in a companion WBS dictionary, and the lowest elements (work packages) feed the schedule, the budget and status reporting.
| Question | Short answer | Where it comes from |
|---|---|---|
| What goes in a WBS? | All of the approved scope and none of anything else | NASA: the WBS “should encompass the entire project’s approved scope of work” |
| How do I check completeness? | The children of each element must sum to exactly that element | GAO: “the sum of a parent’s children must equal the parent” |
| What is the lowest level? | The work package, where work is planned and progress measured | NASA handbook glossary |
| How small is a work package? | Neither NASA nor GAO fixes a size. 8 to 80 hours is a common heuristic; GAO’s earned-value chapter says typically 4 to 6 weeks | Deltek (heuristic); GAO Cost Guide |
| How many levels? | At least three; NASA caps cost capture at seven | GAO-20-195G; NASA handbook |
| What defines each element? | A WBS dictionary | NASA and GAO guidance |
The 100% rule
In project-management writing the rule is usually cited to the Project Management Institute’s Practice Standard for Work Breakdown Structures (second edition, October 2006), which both the NASA handbook and the GAO cost guide list as a reference. The working form is a pair of checks applied at every level of the hierarchy. Looking down, the child elements must account for all of the parent’s scope, so a gap shows up as work that belongs to no child. Looking up, every child must belong to its parent, so work that does not trace to the approved scope shows up as an extra element.
Government guidance states the same test in accounting terms. The US Government Accountability Office puts it plainly in its Cost Estimating and Assessment Guide (GAO-20-195G, March 2020): “In a WBS, the sum of a parent’s children must equal the parent.” Its example is a house-construction WBS in which framing, exterior finishes, interior rough-in and interior finishes must together equal the parent “house construction”, so “each element is defined and related to only one work effort.” NASA’s handbook adds the aggregation consequence: a properly structured WBS allows “complete aggregation of cost, schedule, and performance data from lower elements up to the project or program level without allocation of a single element of work scope to two or more WBS elements.”
The GAO guide also shows what happens when the structure is missing. Its Case Study 8 describes the Department of Energy’s Plutonium Disposition program, where WBSs existed for the individual projects but the National Nuclear Security Administration had not formalized a program-level one. Without it, GAO found, the agency “could not ensure that its life cycle cost estimate captured all relevant costs, which could lead to cost overruns” (GAO-14-231, February 2014).
Two practical tests
- Requirements cross-reference. The NASA handbook recommends a matrix with source requirements on one axis and proposed WBS elements on the other, with an X wherever they meet. A WBS element with no X “would indicate work that is not a part of the required scope and should be removed or formally added to the requirements.” A requirement with no X is scope the WBS has missed.
- Nouns, not verbs. An element names a result (“Help-center articles”), not an activity (“Write articles”). Activities belong to the schedule, which is why critical path scheduling starts only after the work packages are defined.
Product-oriented, not function-oriented
Both major government sources call for the upper levels to be organized by what is produced. NASA defines a WBS as “a product-oriented hierarchical division of the hardware, software, services, and data required to produce the program’s or project’s end product(s)” and states that it is “not an organizational structure.” GAO gives the reason with its house example. An overrun on framing might lead management to change a specification, shift funds or modify the design, but if the WBS were organized by carpenters instead of framing, “management would not have the right information to get to the root cause of the problem.”
GAO lists things that are not products and so should not be second- or third-level elements: functional engineering efforts such as design engineering, requirements analysis, logistics, risk, quality assurance and test engineering; the program schedule; the organizational structure of the program office or contractor; meetings, travel and computer support (which belong inside the elements they serve); and generic labels.
The common project-management shortcut is a phase-based WBS (Requirements, Design, Build, Test). Deltek’s guide lists it among several WBS types and shows a construction project broken into phases at level 2. NASA’s handbook marks a phase-oriented Level 2 “not recommended” (its Figure 3-15) because it gives no clarity on scope or on the products to be developed, and it rules out “Phase A” as an element because “Phase A is a time frame.” A deliverable-based structure keeps scope visible when the schedule changes, and the phases appear later as schedule logic.
What the government standards add
Two public government references show what a WBS looks like at scale. Both give management and support work their own elements, which GAO says a WBS should include “to ensure that all effort is identified at the outset.”
| NASA WBS Handbook | MIL-STD-881 (DoD) | |
|---|---|---|
| Issuer and edition | NASA; NASA/SP-20210023927, revision D, November 2021 (first issued January 2010) | US Department of Defense standard practice for defense materiel items; revision F, 13 May 2022 |
| Standard top levels | Level 1 is the whole project; Level 2 elements come from standard templates in NPR 7120.5, 7120.7 and 7120.8 | WBS definitions by commodity in Appendices A to J (aircraft, electronic, missile/ordnance, sea, space, ground vehicle and others); common elements in Appendix K |
| Project freedom | Levels 3 and lower “are developed and should be controlled by project management” | A clear starting point down to and including level four, with flexibility below it, per Tensix’s summary |
| Depth | Seven levels at most, because NASA’s Core Financial System captures costs to a maximum of seven | Extended by contractors in a contract WBS; in GAO’s example, a subcontractor’s breakdown of a level-4 element shows effort down to level 8 |
| Numbering | NASA Structure Management scheme, matching the financial accounting structure through level seven | A WBS code and description for every element, per appendix |
| Dictionary | Controlled baseline document with a required content list | The appendix definitions, which Tensix suggests as a starting point for a dictionary |
NASA: standard Level 2 and a controlled dictionary
NASA’s Work Breakdown Structure Handbook fixes the top of the tree for space flight projects. The Appendix C dictionary lists eleven Level 2 elements: Project Management, Systems Engineering, Safety and Mission Assurance, Science/Technology, Payload, Spacecraft, Mission Operations System, Launch Vehicle/Services, Ground System(s), Systems Integration and Testing, and Education and Public Outreach. Elements that do not apply, such as a payload or a launch vehicle, “may be deleted.”
Several of those are not things a customer receives. Project management, systems engineering, and safety and mission assurance each get a Level 2 element of their own, so that work is named in the structure instead of being spread across the others. The dictionary entry for Project Management “includes project reviews and documentation… and project reserves,” and excludes the costs of technical planning and management and of delivering engineering, hardware and software, which writes the boundaries between elements down.
MIL-STD-881: families of standard structures
The Department of Defense standard’s current revision is MIL-STD-881F, dated 13 May 2022, which the Defense Department’s ASSIST-QuickSearch record listed as active as of November 2026. It provides WBS definitions for defense materiel commodity systems in Appendices A to J, and Appendix K covers the elements common to all of them. Tensix’s summary describes the standard as a clear starting point down to and including level four, with flexibility for program managers below it. The GAO guide reproduces tables from the 2018 revision (MIL-STD-881D, April 9, 2018). For an aircraft system the Level 2 elements include the air vehicle, with Level 3 elements for airframe, propulsion, vehicle subsystems, avionics, armament/weapons delivery and auxiliary equipment, beside common elements such as integration, assembly, test and checkout; systems engineering; program management; training; data; system test and evaluation; and support equipment. GAO states that “every WBS includes program management as a level 2 element,” and that standardizing only at a high level, such as level 3, lets lower levels “be customized to reflect how the specific program’s work will be managed.”
Standard structures exist so that costs can be compared. GAO notes that not standardizing WBSs “causes difficulty in comparing costs from one contractor or program to another.” For a team inside one company, the same logic applies to a reusable template: the third project’s WBS should start from the second project’s.
The WBS dictionary
The WBS gives titles; the dictionary gives meaning. NASA says the dictionary “is prepared by the project team for the purposes of ensuring that all work scope has been identified and to eliminate duplication and overlap of work assignments,” and that the lower the element, the more descriptive detail it needs. GAO’s Schedule Assessment Guide adds a diagnostic: “Activities that are not assigned to WBS elements or are assigned to undefined WBS elements reflect unassigned or undefined scope.”
NASA’s required content for each element is a title, a code, a content description (including quantities and relevant associated work), the WBS index, the scope definition paragraph number, an associated specification where applicable, the date, revision number and revision authorization with approved changes, and a budget and reporting number. The handbook also says the dictionary “should be a controlled document,” maintained as a baseline and revised under the project’s configuration control for the life of the project.
A practical dictionary entry for a smaller project uses these fields:
| Field | What it holds |
|---|---|
| WBS ID and title | Number and a noun phrase |
| Scope included | The result, with quantities |
| Scope excluded | What a reader might assume is here but is elsewhere |
| Owner | One accountable role |
| Acceptance criteria | The check that shows the result exists |
| Estimate basis and assumptions | How the effort was derived and what must be true |
| Dependencies | Other WBS IDs it relies on |
| Revision | Date and approver of each change |
Worked example: a help center launch
The project: launch a customer help center with articles, search, a launch page and staff training. The table is illustrative; the hours are invented to show the checks, not drawn from any real project.
| WBS ID | Element | Included | Excluded | Illustrative hours |
|---|---|---|---|---|
| 1 | Help center launch | Everything below | Translation, video | 252 |
| 1.1 | Help articles | 12 topics, reviewed and published | Translation, video production | 126 |
| 1.1.1 | Articles 1 to 6, accepted | Draft, specialist review, revision | Screenshots | 54 |
| 1.1.2 | Articles 7 to 12, accepted | Draft, specialist review, revision | Screenshots | 54 |
| 1.1.3 | Screenshots, all articles | Capture and annotation | Product changes | 18 |
| 1.2 | Search configuration | Index, synonyms, relevance test | Site redesign | 40 |
| 1.3 | Launch page | Page, redirects from old URLs, accessibility check | Marketing campaign | 36 |
| 1.4 | Staff training | Materials and one live session | Ongoing coaching | 30 |
| 1.5 | Project management | Plan, status reports, reviews, reserve | Delivery work in 1.1 to 1.4 | 20 |
The checks:
- 100% rule. 54 + 54 + 18 = 126, matching 1.1. Then 126 + 40 + 36 + 30 + 20 = 252, matching element 1. If the parent had been estimated separately at 264, the 12-hour gap would be work that no child element defines.
- Double counting. Screenshots appear once, in 1.1.3, and are excluded from 1.1.1 and 1.1.2. Redirects and the accessibility check have a home in 1.3, rather than falling between the article and launch work.
- Visible project management. Element 1.5 follows the NASA and GAO pattern of giving management its own element.
- Size. All seven lowest-level packages fall between 8 and 80 hours. The 12 individual articles come to about 9 hours each (54 over 6), so they are grouped in sixes; one package per article would leave twelve small items to track.
How small should a work package be?
Neither NASA nor GAO sets one numeric size. NASA defines the work package as the point “at which work is planned, progress is measured, and earned value is computed,” and GAO describes work packages in earned value management as “detailed tasks typically 4 to 6 weeks in duration” that reflect near-term effort.
The widely quoted 8/80 rule says a work package should take between 8 and 80 hours of effort. Deltek’s WBS guide describes it as a guideline under which packages should be completed “within 8 hours of 1 day to 80 hours in 10 days.” It is a heuristic of the field rather than a requirement of the standards above. Treat it as a way to reach a consistent size across a team, not a fact about projects. The same guide offers a second sizing test: a package should ideally be shorter than the project’s reporting period.
A decomposition can stop when each package is estimable, has one owner, and has an acceptance check. If the estimate range is too wide to be useful, or two people would need to agree on who owns it, go one level deeper. If tracking the package costs more than doing it, merge siblings.
From WBS to schedule, budget and backlog
NASA states the sequence: once WBS elements are defined in the dictionary, “it is then possible for the project team to determine the tasks (activities) and events (milestones) that are required,” identified “for the effort contained in each lowest-level WBS element.” GAO’s schedule guide sets the traceability rule: every schedule activity should trace to a WBS element, and every WBS element must have at least one activity. It also says there “should be only one WBS for each program” that matches the one used for the cost estimate and schedule.
For that reason the WBS identifier should appear in the task list, the cost records and the status report. The milestone plan then marks completion of selected elements, and resource planning assigns people to the packages. The risk register can carry the WBS ID of the element each risk affects, so that a risk is tied to a named piece of scope.
In agile work a team can keep the WBS as a scope map and the backlog as the working list. The WBS changes as the work does: GAO says it “should be developed early” and, as the program matures, “should be considered a living document.” NASA requires formal documentation, including the change rationale and project manager approval, whenever the baseline WBS is revised.
Sources
- NASA Work Breakdown Structure (WBS) Handbook, NASA/SP-20210023927, November 2021: definitions, Level 2 templates, dictionary content, seven-level limit, phase-oriented WBS as a common error.
- GAO-20-195G, Cost Estimating and Assessment Guide (March 2020): parent-child sum rule, product orientation, common elements, contract WBS levels, work package duration, MIL-STD-881D tables.
- GAO-16-89G, Schedule Assessment Guide: WBS and schedule traceability, dictionary and undefined scope.
- ASSIST-QuickSearch record for MIL-STD-881: revision F of 13 May 2022, active status, appendix scope, revision history.
- Tensix summary of MIL-STD-881F: appendix files and level-four starting point.
- Deltek, Work Breakdown Structure: 8/80 guideline, work package sizing, phase-based WBS type.