---
title: "How to keep a scenario readable"
description: "Rules for a comfortable scenario in Scenario Builder: one section, one job; group frames, branch labels, ties, the Tidy up hint and aligning blocks."
---

# How to keep a scenario readable?

A scenario is read by more people than its authors: a colleague picks up your work, and you come back to it half a year later. A few simple rules make the flow clear at a glance, and when a section still grows too big, the editor gently suggests what to do with it.

## When you need it

- A section has grown to dozens of blocks and the connection lines cross each other.
- You are handing a scenario to a colleague or taking over someone else's.
- You see the "Tidy up" hint above the canvas and want to know what it suggests.

## What you need to know

- The hint is only a suggestion. It changes nothing by itself and publishes nothing; your clients notice nothing until you click "Publish".
- The hint appears when a section has more than 60 blocks or more than 25 crossings of connection lines. Notes and group frames do not count as blocks. Your manager or support turns the hint on — if you do not see it, that is normal.
- Aligning **cannot be undone with a button**. Until you publish, reloading the page brings the blocks back to their old places, but it also discards **all** unpublished changes to the scenario, not just the alignment. The "Tidy up" hint does not come back after such a reload: it treats the section as already tidied and shows again only when the section grows noticeably (a quarter more blocks or crossings). After publishing, you can restore the earlier look from the [version history](/en/scenariobuilder/how-to/view-scenario-history.md).

## Rules for a comfortable scenario

1. **One section, one job.** "Checkout", "Returns" and "Feedback" are separate sections, not one long chain.
2. **Split large sections into parts.** Select several blocks with a frame and click "Move to..." — that part moves to another section. How sections pass control to each other is described in [Moving between sections: entry and exit](/en/scenariobuilder/explanation/entry-exit-section-flow.md).
3. **Wrap blocks in a group frame** when together they do one step ("Payment", "Support"). See [How to group nodes with a frame](/en/scenariobuilder/how-to/group-nodes-on-canvas.md).
4. **Label branches** after a split so it is clear what each arrow is for: select an arrow and give it a label in the inspector (see [How to edit a scenario](/en/scenariobuilder/how-to/edit-scenario.md)).
5. **Give blocks clear names:** "Ask for phone number", not "Message 14".
6. **Tie bundles of lines.** When several connections run side by side in the same direction, gather them into a tie. See [How to tie connections into a bundle](/en/scenariobuilder/how-to/tie-connections-on-canvas.md).

## The "Tidy up" hint

### 1. See the hint
<!-- docs-assets src=https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-banner-single.png montage=single section=s6 scenario=tidy-hint-banner content_hash=6eac7ebf1fea alt="1. See the hint" -->
![1. See the hint](https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-banner-single.png)

Open a large section. A strip appears above the canvas saying how many blocks and crossings the section has, with the buttons **"Tidy up"** and **"Not now"**.

### 2. Open the window
<!-- docs-assets src=https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-dialog-single.png montage=single section=s7 scenario=tidy-hint-dialog content_hash=c6ee9e65b538 alt="2. Open the window" -->
![2. Open the window](https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-dialog-single.png)

Click **"Tidy up"**. The window lists what you can do with the section:

- **Advice to split the section.** If the reason is the number of blocks, it comes first: aligning does not reduce the number of blocks, so it is better to split the section into parts.
- **Align blocks.** Blocks line up in rows from left to right, following the flow, and group frames adjust to the new block positions. The **"Auto Layout"** button at the bottom of the canvas does the same. Under the description is a forecast: "Crossings: about 9 instead of 34". Sometimes aligning does not reduce the crossings — then the window says so honestly.
- **Ask the AI assistant** (if your role has access to it). The assistant opens on the right with a ready question about this section.

### 3. Align the blocks
<!-- docs-assets src=https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-aligned-single.png montage=single section=s8 scenario=tidy-hint-aligned content_hash=eb254476afe1 alt="3. Align the blocks" -->
![3. Align the blocks](https://storage.static.kwizbot.io/connectiveone-docs/docs-assets/keep-scenario-readable/en/tidy-hint-aligned-single.png)

Click **"Align blocks"**. The blocks line up in rows, the message "Nodes have been automatically arranged" appears, and the "Unpublished changes" marker shows next to the Publish button. The hint strip disappears.

### 4. Postpone the hint

Click **"Not now"** or the cross in the strip. For this section the hint is not shown again until the section grows by about another quarter. The same happens after any alignment of blocks and after "Ask the AI assistant".

## How to check that it worked

- After "Align blocks" the blocks stand in even rows from left to right.
- The hint strip is gone and does not return when you reopen the section.
- The "Unpublished changes" marker is next to the Publish button — review the result and publish, or reload the page to bring back the old layout (this also discards all other unpublished changes).

## Related materials

- [Edit a scenario](/en/scenariobuilder/how-to/edit-scenario.md)
- [Group nodes with a frame](/en/scenariobuilder/how-to/group-nodes-on-canvas.md)
- [Tie connections into a bundle](/en/scenariobuilder/how-to/tie-connections-on-canvas.md)
- [Moving between sections: entry and exit](/en/scenariobuilder/explanation/entry-exit-section-flow.md)
- [Scenario Builder hub](/en/scenariobuilder/integrator-hub.md)
