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.

9 min read 3 sections Document Template Worked Example

Doc № KEV-TPL-103 Sec 4 Sheet 1/1 Drawn KEVOS® 10 Jul 2026

In this resource

Purpose of the WBS
Blank Template Structure
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

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Work Breakdown Structure (WBS) Template & Example. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Use Work Breakdown Structure (WBS) Template & Example as a decision instrument rather than an administrative form. The subject terms—work, structure, breakdown, template, example—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.

Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.

A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.

Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.

Step-by-step operating method

Name the decision. Write the decision, approval, handover or control activity the completed template must support.
Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.

Completion and governance protocol

Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.

Information type	Minimum useful content	Review test
Outcome	Observable change and intended recipient	Not merely a deliverable or activity
Measure	Definition, baseline, target, frequency and source	Two reviewers would calculate it the same way
Ownership	One accountable role plus contributors and approver	Authority matches responsibility
Uncertainty	Assumption, risk or issue with response and trigger	Status reflects current reality
Control	Version, approval, review date and change rule	Current baseline is identifiable

Common failure modes and recovery actions

1. Watch for

Filling every box even when a field is not applicable instead of recording why.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Writing vague statements without an owner, measure, date or evidence source.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Copying a previous project without revalidating assumptions and stakeholders.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Using the document as a private worksheet when it is meant to support a shared decision.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Creating an approved baseline but failing to define who maintains it and when.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

Is the purpose and intended decision clear to a reader outside the team?
Are owners, dates, measures and sources complete and internally consistent?
Which fields are assumptions and how will they be validated?
What event, threshold or review date causes this document to change?
Are mandatory requirements distinguished from recommendations and illustrative values?
Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Work Breakdown Structure (WBS) Template & Example?