Process Hierarchy

Model rollups with parent-child processes for navigation and reporting.

Overview

Process hierarchy models rollups inside a Blueprint. It supports navigation and reporting without creating extra fields.

Key Concepts

• Parent process: grouping node used for rollups
• Child process: real subset of a parent process
• Hierarchy depth: number of parent-child levels

How It’s Used

Use hierarchy when teams need both summary and detail reporting. Use it to model phases, business areas, or workstreams.

Benefits

• Cleaner reporting and rollups
• Faster navigation in large Process maps
• More consistent structure across Projects

Setup Steps

1

Create a parent process

Create a top-level grouping node such as Finance or Implementation.

2

Add child processes

Add child processes that represent real subsets of the parent.

3

Keep depth shallow

Prefer 2–3 levels for most Blueprints.

Best Practices

• Use parent nodes as categories, not deliverables.
• Avoid deep trees that create reporting friction.
• Keep naming consistent across Blueprints.

Summary

Process hierarchy enables rollups for navigation and reporting. Parent-child structure should stay shallow and consistent.

Related:

• Processes