← LibraryWork Breakdown Structure (WBS) Template & ExampleTemplates & Examples · Project TemplatesLesson 10/23← PrevNext →
TemplatePublished 10 Jul 2026Updated 14 Jul 20264 min readBy Kevin Joginscope managementwbswork breakdown structureproject planning
KEVOS®
Templates & Examples · Project Templates
Templates & Examples / Project Templates

Work Breakdown Structure

Hierarchically decompose your project into Major Deliverables and Work Packages to establish a definitive framework for planning and control.

4 min read 3 sections Document Template Worked Example
1.0 Project 1.1 Phase A 1.2 Phase B 1.3 Phase C
Doc № KEV-TPL-103 Sec 4 Sheet 1/1 Drawn KEVOS® 10 Jul 2026

In this resource

  1. Purpose of the WBS
  2. Blank Template Structure
  3. Worked Example: Mary's Consulting

§1 Purpose of the WBS

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team.

The WBS is the foundational skeleton of project planning. It translates the broad boundaries established in the Scope Statement into specific, manageable deliverables. The lowest level of the WBS is the Work Package, which provides the precise framework for estimating costs, assigning resources, and developing the schedule.

The 100% Rule The WBS must represent 100% of the work defined by the project scope. If a deliverable is not in the WBS, it is not part of the project. Conversely, the WBS should contain nothing outside the approved scope.
Contents

§2 Blank Template Structure

A conceptual representation of how to layout a WBS either visually (as a tree) or textually (as an indented outline).

While visual trees are excellent for executive presentations, a numbered outline is often more practical for large projects within document processors.

WORK BREAKDOWN STRUCTURE

Project Title [Insert Project Name]
Date Prepared [YYYY-MM-DD]

Visual Tree Structure

  • 1.0 [Project Name]
    • 1.1 [Major Phase / Deliverable]
      • 1.1.1 [Work Package]
      • 1.1.2 [Work Package]
    • 1.2 [Major Phase / Deliverable]
      • 1.2.1 [Work Package]

Numbered List Format

1.1 [Major Phase]
1.1.1 [Work Package]
1.1.2 [Work Package]
1.2 [Major Phase]
1.2.1 [Work Package]
Contents

§3 Worked Example: Mary's Consulting

A completed example demonstrating the structural decomposition for a mid-sized digital implementation project.

This layout presents the project hierarchy first as a nested visual tree, and then as a multi-column numbered list, providing both the executive overview and the detailed numbering required for accounting and scheduling tools.

WORK BREAKDOWN STRUCTURE

Project Title Mary's Consulting - New Company Website
Date Prepared May 10, 2026

Visual WBS

  • 1.0 Mary's Consulting Website
    • 1.1 Project Management
      • 1.1.1Project Initiation
      • 1.1.2Project Planning
      • 1.1.3Execution & Control
      • 1.1.4Project Closeout
    • 1.2 Requirements & Design
      • 1.2.1Requirements Elicitation
      • 1.2.2Requirements Documentation & RTM
      • 1.2.3Information Architecture
      • 1.2.4Visual / Brand Design
      • 1.2.5Design Approval
    • 1.3 Content Development
      • 1.3.1Content Strategy
      • 1.3.2Page Copywriting
      • 1.3.3Case Study Production
      • 1.3.4Consultant Bio Collection
      • 1.3.5Blog Seed Content
      • 1.3.6Imagery & Photography
      • 1.3.7Legal Pages
    • 1.4 Build & Integration
      • 1.4.1Environment Setup
      • 1.4.2CMS Configuration
      • 1.4.3Frontend Development
      • 1.4.4Backend / API Development
      • 1.4.5CRM Integration
      • 1.4.6Search & Analytics
    • 1.5 Test & Quality Assurance
      • 1.5.1Test Planning
      • 1.5.2Functional Testing
      • 1.5.3Performance Testing
      • 1.5.4Accessibility Audit
      • 1.5.5User Acceptance Testing
      • 1.5.6Defect Resolution
    • 1.6 Launch & Transition
      • 1.6.1Pre-Launch Communications
      • 1.6.2Content Migration
      • 1.6.3Production Cutover
      • 1.6.4Post-Launch Hypercare
      • 1.6.5Operations Handoff
      • 1.6.6CMS Training

Numbered WBS List

1.1 Project Management
1.1.1 Project Initiation
1.1.2 Project Planning
1.1.3 Execution & Control
1.1.4 Project Closeout
1.2 Requirements & Design
1.2.1 Requirements Elicitation
1.2.2 Requirements Documentation & RTM
1.2.3 Information Architecture
1.2.4 Visual / Brand Design
1.2.5 Design Approval
1.3 Content Development
1.3.1 Content Strategy
1.3.2 Page Copywriting
1.3.3 Case Study Production
1.3.4 Consultant Bio Collection
1.3.5 Blog Seed Content
1.3.6 Imagery & Photography
1.3.7 Legal Pages
1.4 Build & Integration
1.4.1 Environment Setup
1.4.2 CMS Configuration
1.4.3 Frontend Development
1.4.4 Backend / API Development
1.4.5 CRM Integration
1.4.6 Search & Analytics
1.5 Test & Quality Assurance
1.5.1 Test Planning
1.5.2 Functional Testing
1.5.3 Performance Testing
1.5.4 Accessibility Audit
1.5.5 User Acceptance Testing
1.5.6 Defect Resolution
1.6 Launch & Transition
1.6.1 Pre-Launch Communications
1.6.2 Content Migration
1.6.3 Production Cutover
1.6.4 Post-Launch Hypercare
1.6.5 Operations Handoff
1.6.6 CMS Training

Deliverable Oriented

Notice that WBS nodes are nouns (deliverables), not verbs (activities). "1.4.3 Frontend Development" is the output package; the specific actions to build it will be defined later in the Activity List.

Phase Phasing

The Level 2 items (1.1, 1.2, etc.) represent major project phases. This approach allows the PM to roll up costs and status reports logically for the steering committee.

Control Accounts

For larger projects, the Level 2 phases act as Control Accounts. The total cost of 1.4 Build & Integration can be tracked independently of the individual 1.4.X work packages beneath it.

Contents

Continue learning

Cost Baseline Template & ExampleTemplate · Project TemplatesProject Funding RequirementsTemplate · Project TemplatesProject Schedule (Gantt Chart) Template & ExampleTemplate · Project TemplatesNEXT LESSON →Project Scope StatementTemplate · Project Templates