> 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-sections.md).

# Project Sections

### Overview

Project sections group work inside a Project. They support predictable navigation and timeline planning.

### Key Concepts

#### Project section

A project section is a container inside a Project. Sections group work into phases, sprints, or workstreams.

### How It’s Used

Sections are flexible.

Common patterns:

* **Phases**: Plan, Design, Build, Test, Deploy
* **Subphases**: nested under a parent section
* **Sprints**: Sprint 1, Sprint 2, Sprint 3
* **Workstreams**: Change Management, Data Migration, Integrations
* **Milestones** or other stages

### Modeling phases and sprints in Transform

Transform does not use dedicated “Phase”, “Subphase”, or “Sprint” object types.

Use sections instead:

* **Phase** → top-level section
* **Subphase** → child section under a parent
* **Sprint** → section named by sprint (for example: `Sprint 2`)
* **Workstream** → section grouped by functional area

### Section fields and behavior

Typical section fields:

* **Name**
* **Parent section** (for nesting)
* **Start date / end date** (for timeline planning)
* **Status** (if enabled)
* **Budget** (if enabled)

{% hint style="info" %}
For Gantt usage, set section start and end dates early.
{% endhint %}

### Benefits

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

### Setup Steps

{% stepper %}
{% step %}

### Create top-level sections

Create sections for major phases or workstreams.
{% endstep %}

{% step %}

### Add child sections (optional)

Nest sections for subphases and sprints when hierarchy is needed.
{% endstep %}

{% step %}

### Set section dates

Set start and end dates for timeline planning and Gantt visibility.
{% endstep %}
{% endstepper %}

### Sections on the Gantt chart

When a section has start and end dates, it shows as a bar on the Gantt chart.

This lets you see phases and sprints alongside individual tasks.

Tip: In many setups, you can adjust section dates directly in Gantt.

### Best Practices

* Use **top-level sections** for major phases or workstreams.
* Use **child sections** for subphases and sprints.
* Keep section names **unique within a Project**.
* Add **dates** so timelines stay accurate.
* Use a consistent naming pattern across Projects.

### Summary

Project sections group work into phases, sprints, and workstreams. Section dates enable clear Gantt timelines.

Related:

* [Project Structure and Hierarchy](/organizations-and-projects/project-structure-and-hierarchy.md)
* [Creating and Customizing Gantt Charts](/getting-started/creating-and-customizing-gantt-charts.md)
* [Create and Assign Tasks](/transformations/create-and-assign-tasks.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/organizations-and-projects/project-sections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.