> For the complete documentation index, see [llms.txt](https://docs.studio.uzu-app.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.studio.uzu-app.com/en/basic-features/phase/flow.md).

# Phase progression

Phase Progression is the screen where you set the **order of the phases** and their **branching**.

From the left menu, select "Phases," and within that screen, click "Progression Settings" to move to the editing screen.

\\

## Basic Operations

The basic operations are "arranging" and "connecting."

Phases can be connected as follows, allowing you to set which phase follows which. The alphabets written on the line correspond to the alphabets displayed on the left column.

If you want to reconnect an already connected line (transition) to a different place, find the corresponding alphabet from the left column and select **Delete** from the "..." menu.

*Note: If you are browsing on a smartphone, the left half will not display unless you hold it horizontally.*

![](/files/rDEirxCGg4UbNtxMj3Aa)

\\

## Types of Transitions

There are two types of lines (transitions) between phases: "**Basic Transition**" and "**Conditional Transition**."

| Type of Transition     | Appearance              | Description                                                                                                              |
| ---------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Basic Transition       | ○ White with black text | <p>Transitions on tap or after a set time has passed<br>If no conditional transitions apply, this transition occurs.</p> |
| Conditional Transition | ● Black with white text | Transitions only if certain conditions are met.                                                                          |

\\

Setting multiple lines (transitions) from one phase will always result in one being a "**Basic Transition**" and the rest as "**Conditional Transitions**." This can be visualized as branching from voting to an ending.

When there are multiple conditional branches, they are prioritized from top to bottom in the left column. The alphabets are just identifiers and do not indicate priority.

To set or delete transition conditions, press the "..." button.

![](/files/iibnX7KMawYNYPvxxCE9)

You can also use a combination of "and" and "or" in nesting conditions. For more details, see [here](/en/basic-features/condition.md#gurpu).

## Frequently Asked Questions

For frequently asked questions related to phase progression, see [here](/en/qanda/qanda.md#phases)


---

# 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://docs.studio.uzu-app.com/en/basic-features/phase/flow.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.
