WBS and hierarchy: build the outline, roll it up and publish it to field tasks
Build a work breakdown structure in the Planner, place each activity under a WBS summary, read and edit the outline in the WBS window, group the grid and Gantt by WBS, and publish summaries and parent changes to field tasks after a review.
On this page
The work breakdown structure (WBS) is the outline your schedule hangs on: phases, buildings, floors or trades, nested as deep as you need. In the Planner you build it as WBS summaries, point each activity at one, and then read the plan by WBS in the grid, the Gantt and the WBS window. Open Project Tools › Schedule › Planner. You need Schedule admin.
The WBS is part of the saved plan. Editing it changes the draft, and saving calculates a new version. It never changes field tasks by itself: summaries and parent changes reach the field schedule only through the reviewed hierarchy publication.
Build the outline
The Work breakdown structure section of the Planner lists the plan’s summaries, with a count, a search box and 50 summaries a page.
- Load the history first on a saved plan. Choose Load saved summary history. This reads the plan’s saved versions so a new summary never reuses the ID of one that was removed earlier. On a new plan with no saved version, you can add summaries straight away.
- Choose Add WBS summary. A summary called New summary is added to the draft with the next unused WBS ID. WBS IDs are assigned for you and can’t be edited.
- Name it and choose its Parent summary. Leave the parent empty to put it at the top level. The parent list leaves out the summary itself and everything under it, so you can’t create a loop. Search finds summaries by name or exact ID.
- Repeat for each level of the outline.
- Save and calculate. Before calculating, the engine checks that the outline is valid: unique IDs, parents that exist and no cycles.
Put activities under a summary
Select an activity and use Activity summary in the activity form to place it under a summary or at the project root. The General tab of Activity Details shows the same WBS. Changing an activity’s summary, or any summary’s parent, turns on the hierarchy publication review for the plan, so the field parent changes are reviewed before anyone sees them.
Remove or restore a summary
- Remove summary from plan works only on an empty summary. Move or remove its child summaries and activities first; the form lists what still points at it. Confirm with Confirm summary removal, then save. Its field task, if it has one, still needs a separate retain or retire decision when you publish.
- Restore a saved summary brings back a removed summary with its exact ID and the metadata it was saved with, including fields this form doesn’t show. Find it by name, restore its parent first if that was removed too, and add activities under it before you publish: an empty summary can’t be published.
Read the plan by WBS
- Group & Sort. Default (WBS) groups the grid and the Gantt by WBS in one click, with group totals and a summary bar for every band. To Level cuts the outline at a depth. See Group and Sort.
- WBS outline. Grouping by WBS assignment in the activity grid opens a nested outline. Each summary shows the earliest calculated start, latest calculated finish, smallest known float and whether any activity under it is critical, with counts of the activities that have dates, float and criticality. Collapsing a summary hides its activities in the outline and the Gantt, and the Gantt draws a bracket for each summary.
- WBS window. Choose WBS as the display mode for P6’s WBS window: one row per node with dates, durations, float, % complete, costs and units rolled up from everything beneath it, a project total and a WBS Gantt. Select a node to change its WBS Name or WBS Code, Move up, Move down or Move under another node, or set its earned value settings. See WBS window.
Earned value settings by WBS
A WBS node can carry its own Earned value technique, Custom percent complete, ETC technique and Performance factor. Each field shows what it inherits from the parent WBS or the project until you set it. Activities use their nearest WBS’s setting, then the project’s. On export, a field left on inherit is written as the value it inherits, because P6 has no inheritance. See Earned value techniques.
WBS from files and templates
- Import. P6 XER and P6 XML files bring their WBS (code, name, parent and order) into the plan, and it goes back out on export. When you update the current plan from a file, WBS nodes match by their P6 GUID, else by their code path, and Add into WBS node adds a whole file under one node of your choosing.
- Templates. A company template fragment can be one or more WBS branches with everything under them, inserted into another plan as a new version.
- EPS. P6’s enterprise project structure (EPS) isn’t modelled: there’s no EPS tree to import or edit. Activity code types with EPS scope are kept and written back on export. To look across projects, use Portfolio and programs.
Publish the hierarchy to field tasks
Field tasks are the published task list that the List, 3-Week Lookahead, Calendar and Gantt views read. For a plan you built in the Planner, the hierarchy review creates field tasks for new summaries and activities and moves existing tasks to their new parents. A plan adopted from an imported file uses Update linked task dates instead; see Schedule.
- Save and calculate the plan. Unsaved edits invalidate any review.
- Tick Review hierarchy publication, including WBS summaries and parent changes if it isn’t already on, then choose Load hierarchy inventory. It lists the plan’s nodes and the existing field tasks, 50 a page, with any blockers.
- Choose an operation for each new node: Create field task, Bind existing task or Restore reserved task. New summaries are private, unassigned and visible only to administrators. For a new activity, choose privacy, an assignee from the active project members, and whether to Use initial calculated dates as its baseline or Leave baseline empty. Progress starts at 0% with no actual dates.
- Confirm parent moves with Confirm parent move, and choose Retain or Retire for each remaining field task. Tasks already bound to the plan are updated automatically.
- Preview hierarchy publication, read every before and after value under Review field changes, tick I reviewed the complete field changes and creation policies. and choose Apply reviewed hierarchy.
Publishing requires admin access to Schedule, Submittals and CRM, with all three tools enabled, because it checks links across those records. Changing any choice clears the preview. If the plan or the tasks changed since you loaded them, the apply is refused, your confirmed choices are kept and you review again. For work that has already started, use the progress publication review, which adds percentages and actual dates; see Schedule.
Mistake: Adding summaries to a saved plan without loading history
In the app: Choose Load saved summary history first, so a new summary never reuses a removed one’s ID.
Mistake: Removing a summary that still has children
In the app: Move its child summaries and activities first. Removal is blocked until it’s empty.
Mistake: Expecting a WBS change to show in field tasks after Save
In the app: Saving changes the plan only. Review and apply the hierarchy publication to change field parents.
Mistake: Publishing an empty restored summary
In the app: Put activities under it first. Empty summaries can’t be published.
Limits
- WBS IDs are assigned automatically and can’t be changed in the editor. Use the WBS window to change a node’s code.
- The WBS editor and outline show 50 rows a page; the parent picker shows up to 100 matches plus the current parent.
- Saved-history scans have size and time limits. If a scan can’t finish, adding or restoring is blocked rather than risking a reused ID.
- Hierarchy publication doesn’t apply to plans adopted from an imported file, or to started work; those use the linked-dates and progress reviews.
Related
Keep exploring
Related across os.construction
- DocsViews and layouts: filters, Group & Sort, columns, Network and Trace LogicOpen and save P6-style layouts for yourself, the project or the company, export and import them as files, build filters with nested All/Any criteria and highlight mode, group and sort to five levels with totals, choose from 45 core columns plus baseline, cost, units and earned value columns, draw a progress line, read the logic in the Activity Network, Trace Logic and Assignments views, and roll the plan up in the WBS window.
- DocsP6 compatibility: settings, import, export and what round-tripsHow closely os.construction matches Primavera P6. Which scheduling settings the engine honours, which P6 calculated fields it works out, what crosses an XER or P6 XML file in both directions, the measured agreement with P6's own dates and costs, and the limits that remain.
- GlossaryWork Breakdown StructureA hierarchy that breaks the whole scope of a project into smaller, manageable pieces of work, used to organize the schedule, the budget and progress reporting.
- BlogHow to create a work breakdown structure for a construction projectA work breakdown structure splits the whole scope of a job into pieces you can schedule, budget and measure. Choose the split that matches how the job will be built, decompose to work packages one party can own, check the 100% rule, write a WBS dictionary, then tie the WBS to cost codes and schedule activities. Here is the method and a worked example for a three-story office building.
- GlossaryEarned Value TechniqueThe rule that decides how much of an activity's budget counts as earned at a given point of progress, such as percent complete, 0/100 or 50/50.
- Free toolConstruction schedule (Gantt) templateFree construction schedule template for Excel.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →