Skip to content
Kairos OneBook a demo
Menu
Foundation · 2 min read

Structure WBS and activity codes in P6

Create a scope hierarchy and controlled coding system that supports planning, responsibility, reporting, and exchange.

Working definition

The WBS answers where scope belongs; activity codes answer how the same work should be sliced for phase, area, contractor, responsibility, bid item, change, or reporting. A professional schedule uses both. Overloading the WBS with every reporting dimension produces an unstable hierarchy, while uncontrolled codes create inconsistent portfolio data.

Version scope

Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.

Key takeaways

  • Use WBS for hierarchical scope and codes for cross-cutting reporting dimensions.
  • Govern activity-code level, values, descriptions, ownership, and required use.
  • Reconcile WBS and codes with scope, cost, responsibility, and reporting structures.
01

WBS follows deliverables and control

Build the WBS from the approved scope and responsibility model. Each activity should trace to one appropriate WBS element, while cross-cutting classifications belong in governed activity codes.

02

Code dictionaries are data contracts

Define code level, owner, values, descriptions, required population, and exchange behavior. Project-level codes are easier to contain; global or EPS-level codes require enterprise governance.

Build a controlled WBS and coding dictionary

Complete the scope hierarchy before loading large volumes of activities.

Menu path: Project > WBS; Enterprise > Activity Codes

Before you start

  • Approved scope or cost WBS
  • Responsibility matrix
  • Reporting and contract-code requirements

  1. Create the WBS hierarchy

    Open Project > WBS and add elements using the governed ID and name convention.

    Verify: Every required deliverable and phase maps to a manageable branch without duplicate scope.

  2. Assign responsibility

    Set responsible managers or owners at the appropriate WBS level.

    Verify: Ownership aligns with security and reporting expectations.

  3. Define code levels

    Open Enterprise > Activity Codes and choose project, EPS, or global scope deliberately.

    Verify: Code scope matches intended reuse and governance.

  4. Create the dictionary

    Add controlled values and descriptions for area, phase, responsibility, contract package, change, or other required dimensions.

    Verify: Values are unique, understandable, and reconciled to source registers.

  5. Populate and test

    Assign codes to a pilot group of activities and build a grouped layout.

    Verify: The layout answers the intended reporting question without changing the WBS.

    Field-ready control

    WBS and code governance check

    • WBS reconciles to approved scope.
    • No duplicate or orphan scope branches.
    • Code level is deliberate.
    • Values have owners and definitions.
    • Required codes are populated.
    • Grouped layouts reconcile to source registers.

    Common questions

    Should location be another WBS level?

    Only when location is part of the primary hierarchical control structure. If the same scope must also be reported by phase, responsibility, or package, those dimensions are usually better handled as codes.

    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.

    Primavera P6 Professional User Guide, Version 26Oracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01