> 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/organizations-and-projects/project-structure-and-hierarchy.md).

# Project Structure and Hierarchy

Understand how Organizations, Projects, sections, and work items roll up for navigation and reporting.

### Overview

Project structure defines how delivery work is organized inside a Project. A clear hierarchy makes navigation, reporting, and governance easier.

### Key Concepts

* **Organization → Project**: top-level separation of work
* **Project sections**: grouping mechanism for phases, sprints, and workstreams
* **Work items**: requirements, tasks, tests, and artifacts
* **Hierarchy**: parent-child relationships that support rollups

### How It’s Used

Use sections to model delivery phases and workstreams. Use consistent naming to support search and reporting.

### Benefits

* Faster navigation in large Projects
* Cleaner timelines for Gantt views
* Clearer ownership when sections map to workstreams

### Setup Steps

{% stepper %}
{% step %}

### Confirm Organization and Project boundaries

Create one Organization per client or department. Create one Project per initiative.
{% endstep %}

{% step %}

### Define Project sections

Create top-level sections for phases or workstreams. Add child sections for subphases and sprints.

* [Project Sections](/organizations-and-projects/project-sections.md)
  {% endstep %}

{% step %}

### Standardize fields used for reporting

Add custom fields at Project scope. Use Organization-level Segmentation for cross-Project reporting.

* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
* [Segmentation](/blueprints/segmentation.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Keep section names stable and unique within a Project.
* Use the same phase names across related Projects.
* Keep workstream sections aligned to real ownership boundaries.

### Summary

Project hierarchy is built from Organization and Project boundaries plus section structure. Consistent structure improves navigation and reporting.

Related:

* [Organizations](/organizations-and-projects/organizations.md)
* [Projects](/organizations-and-projects/projects.md)
* [Creating and Customizing Gantt Charts](/getting-started/creating-and-customizing-gantt-charts.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/organizations-and-projects/project-structure-and-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.