> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/blueprints/creating-blueprints/process-hierarchy.md).

# 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

{% stepper %}
{% step %}

### Create a parent process

Create a top-level grouping node such as `Finance` or `Implementation`.
{% endstep %}

{% step %}

### Add child processes

Add child processes that represent real subsets of the parent.
{% endstep %}

{% step %}

### Keep depth shallow

Prefer 2–3 levels for most Blueprints.
{% endstep %}
{% endstepper %}

### 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](/blueprints/creating-blueprints/processes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/blueprints/creating-blueprints/process-hierarchy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.