CIVIL_SYSTEMS
Tools · Project scope

WBS Builder & Checker

Work breakdown structure · 100% rule · WBS dictionary · Rollups

Reviewed November 2026 · Civil Systems LLC

Break a project into the things it has to deliver, then check that the pieces add up to the whole job.

Type an outline, one deliverable per line, and indent with Tab, or drag boxes around the tree. Codes and totals update as you go, and a coach points out what usually goes wrong. Start with the small picnic table example, then try the practice modes.

What is a WBS, in one minute?

A work breakdown structure is a family tree of everything the project has to produce. The project sits at the top. Under it go the main pieces, and under those, smaller pieces, until each one is small enough that one person can estimate it and own it. Those smallest pieces are called work packages.

A picnic table, for example, breaks into a tabletop, bench seats, a leg frame, and a finish. Each is something you can point to and say “done.”

Why not just make a to-do list?

A to-do list says what to do; a WBS says what you will have when you are done. Naming results instead of actions makes it easier to see what is missing, to agree on what “finished” means, and to price each piece. The actions come later, in the schedule, under each work package.

What makes a WBS good?

Three habits cover most of it. The pieces under each box add up to all of that box’s work, no more and no less (the 100% rule). No two pieces overlap. And each name is a thing, not an action: “Concrete footings,” not “Pour the footings.” The checks on this page look for exactly these.

What happens after the WBS?

It becomes the backbone of the plan. Each work package gets activities and a duration in the schedule, a cost estimate, and its risks, which you can run through the Monte Carlo calculator. When the scope changes later, the WBS shows which pieces the change touches.

01 / Build and practice

One tree, five ways to work it

Example projects9 to try, from simple to detailed. Pick one to load it.

Tree canvas Drag any box onto another to move it, or into the parking lot · Click a box to edit or add children
Click any box in the tree to edit its name, hours, or cost, add child boxes, or move it. You can also drag boxes directly onto each other.

Parking lot

Drag a box here to set it aside while you think, or park a new idea. Drag a parked piece onto any box to place it.

      Coach’s notes

      Build your own

      Pick an example above or start from a blank outline. Type in the outline, or drag boxes on the canvas: drop one onto another to move it there, or into the parking lot to set it aside. Try dragging “Leg Frame” onto “Tabletop” and watch what the coach says. Zoom with the − and + buttons (or Ctrl and the mouse wheel), and drag the empty background to pan.

      WBS dictionaryOwners, descriptions, and acceptance criteria

      The detail behind each work package. Owners and acceptance criteria are what turn a box into a commitment. Criteria are checked for vague words as you type. Entries are saved on this device.

      CodeWork packageOwnerDescription of workAcceptance criteria
      02 / Export

      Take it with you

      Exports use the outline in Build or Fix mode. Everything is created in this browser; nothing is uploaded.

      Export optionsAI review, dictionary, picture, Monte Carlo, data

      Ask an AI to review it

      Rules cannot judge meaning. Copy the outline, dictionary, and check results as Markdown and paste them into the assistant of your choice. The site does not send it anywhere. Remove anything confidential first.

      WBS dictionary

      One row per work package: code, name, parent, hours, cost, owner, description, and acceptance criteria.

      Tree picture

      The tree as drawn, on a white background, for a report or slide.

      Send work packages to Monte Carlo

      A file for the Monte Carlo Risk Calculator: one line per estimated work package, with your estimate as the most likely value. The range is a placeholder to replace with your own.

      WBS data

      A structured file with codes, parents, estimates, rollups, and dictionary entries, for later planning steps or your own tools.

      03 / Final review

      What the rules cannot check

      The checks above read structure and wording. They cannot tell whether two elements mean the same thing, whether the scope is complete, or whether a criterion can really be tested. Before you baseline the WBS, walk it with the people who will do the work and tick each item.

      04 / Understand

      What the checks are based on

      Most checks come from PMI’s Practice Standard for Work Breakdown Structures, Third Edition. A few are rules of thumb or limits of this tool, and they are labeled that way. Errors are for structure only; everything else is coaching you can choose to override.

      How the checks work15 checks, what each is based on, and how the score is counted
      CheckTypeBasis
      One top elementErrorThe project is the single element at level 1 (PMI 2.2.1).
      Levels in orderErrorEach element sits one level below its parent. A line indented two steps has no parent.
      No single childrenError“When a parent results in only one child, that parent should not be decomposed further” (PMI 2.3.1.1). This is its own guideline, separate from the 100% rule.
      Every element namedErrorA line with only an estimate cannot be assigned or accepted.
      Deliverable namesCoachingA quality WBS uses “nouns and adjectives, not verbs” (PMI 4.2.1). PMI also lists action- and phase-oriented WBSs, so single words such as “Design” and names such as “Design Package” are not flagged.
      Estimates on work packagesCoaching“WBS elements do not contain costs” (PMI 2.3.1.1). Estimates belong to work packages and the WBS dictionary; parents roll up, so a number typed on a parent is not added.
      No overlapping elementsCoachingElements are mutually exclusive (PMI 2.3.1.1). The tool catches the same name or a near match, such as “Panels” and “Panel Install”. Overlap in meaning is on the final review list.
      Project management includedCoachingA quality WBS captures deliverables “including project management” (PMI 4.2.1). Checked by whole words at level 2, so “Equipment” does not count as “PM”.
      Every work package estimatedCoachingOnce any work package has an estimate, a blank one makes every total above it low.
      Work package size (8/80)CoachingA rule of thumb, not a PMI rule: about 8 to 80 hours is easy to estimate and track.
      Four levels or fewerCoachingA limit of this tool, to keep the tree readable. PMI sets no limit on levels.
      Readable estimatesCoachingHours as 40h, costs as $12000 or $12k, so they roll up.
      Measurable acceptance criteriaCoachingAcceptance criteria are part of the WBS dictionary (PMI 2.4.5). Words like “complete”, “good”, or “as needed” cannot be accepted or rejected.
      Short namesCoachingA limit of this tool: 45 characters. Put the detail in the WBS dictionary.
      What’s usually here?QuestionCompares level-2 and lower names with branches that most projects of the same type include. A question, never a score penalty: leaving something out may be the right call.

      The health score starts at 100 and loses points once for each check that fails, however many elements fail it, so one repeated habit does not sink the score. It never goes below 0.

      Common questions
      What is a work breakdown structure (WBS)?

      A WBS divides the whole scope of a project into smaller deliverables, level by level, until each piece is small enough to estimate, assign, and track. The project is the single element at the top. The lowest elements are work packages. PMI calls it a hierarchical decomposition of the total scope of work to be carried out by the project team.

      What is the 100% rule?

      The work at each level adds up to all of the work of its parent, and the whole WBS covers all of the agreed scope, including project management. Nothing in the scope is left out, and nothing outside it is added. It is why parent totals in this tool are always the sum of their work packages.

      Should WBS elements be nouns or verbs?

      In a deliverable-oriented WBS, use nouns and adjectives that name the result, such as Concrete pier footings rather than Pour the footings. The actions that produce each work package belong in the schedule as activities. PMI also describes action-oriented and phase-oriented WBSs, so this tool treats verb-led names as coaching, not as errors.

      How big should a work package be?

      Small enough to estimate with confidence and assign to one owner, and large enough that it is not a to-do item. A common rule of thumb, the 8/80 rule, suggests roughly 8 to 80 hours of effort. It is not a PMI rule, and the right size depends on how often you report progress.

      What goes in a WBS dictionary?

      The detail behind each element: a description of the work, the responsible person or team, assumptions and constraints, milestones, cost and effort estimates, quality requirements, and acceptance criteria. PMI notes that WBS elements themselves do not contain costs; the estimates live with the work packages and the dictionary.

      Is my WBS sent anywhere?

      No. The outline and dictionary stay in your browser, saved on this device only. The AI review export is a block of text you copy or download and paste into an assistant of your choice; the site does not send it anywhere.

      Can I send my work packages to the Monte Carlo calculator?

      Yes. Download the Monte Carlo file and open it in the Monte Carlo Risk Calculator. Each estimated work package becomes one line, with your estimate as the most likely value and a placeholder range around it that you should replace with your own.

      Model assumptions. One element per line, indented with tabs or consistent spaces; a pasted outline with codes such as 1.2.1 is read by its codes. The project is numbered 1 and its children 1.1, 1.2, and so on. Up to 60 elements, 4 levels, and 45 characters per name; longer input is clipped, and shared links are checked and size-limited before anything is read. Parent totals are the sum of their work packages; an estimate typed on a parent is reported and not added. Hours and cost are whatever you enter, in one currency. Checks are deterministic rules, not a language model, so they catch patterns, not meaning. Terms follow PMI’s Practice Standard for Work Breakdown Structures, Third Edition (sections 2.2.1, 2.2.5, 2.3.1, 2.4.5, and 4.2.1). In PMI’s description, level 2 holds phases or major deliverables, and control accounts and work packages sit at level 3 and below; the 8/80 guideline is a rule of thumb and the 4-level cap is this tool’s, not PMI’s.