> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glidepathcpm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizing Tasks with WBS

> Work Breakdown Structure (WBS) numbering and task hierarchy

# Organizing Tasks with WBS

## Feature Spec Reference

Module 2.1 (auto-WBS), Module 2.5 (indent/outdent)

<img src="https://mintlify.s3.us-west-1.amazonaws.com/glide-path/assets/screenshots/02-04-gantt-task-list-with.png" alt="Screenshot" />

## Work Breakdown Structure (WBS)

The WBS is a hierarchical decomposition of your project into manageable work packages. GlidePath automatically assigns WBS numbers based on task hierarchy.

### WBS Numbering

* **Level 1 (Top-level):** 1, 2, 3, etc.
* **Level 2 (Children):** 1.1, 1.2, 1.3, etc.
* **Level 3 (Grandchildren):** 1.1.1, 1.1.2, etc.

### Creating Hierarchy

Use **Tab** to indent (create child) or **Shift+Tab** to outdent (promote to parent):

1. Create a task (e.g., "Phase 1 Design")
2. Create child tasks below it
3. Select a child task and press **Tab** to indent
4. WBS numbers auto-update

### Summary Tasks

When a task has children, it becomes a **summary task**:

* **Dates auto-roll-up** from children (start = earliest child, finish = latest child)
* **Duration** = span from earliest to latest child
* **Cannot edit dates directly** — hierarchy controls them

### Before and After

<img src="https://mintlify.s3.us-west-1.amazonaws.com/glide-path/assets/screenshots/02-04-gantt-task-list-with.png" alt="WBS Hierarchy" />

*Before and after indenting tasks to create a proper WBS structure with auto-numbered hierarchy.*

### Best Practices

1. **Use 2–4 levels maximum** — Deep hierarchies are hard to navigate
2. **Use consistent naming** — Follow a pattern (Phase, Activity, Task)
3. **Group related work** — Keep similar tasks under the same parent
4. **Create summary milestones** — Indicate phase completions at the parent level