# Pre-flight Checks: Structure report

> Names, groups and nesting.

Glider documentation · Playout & On Air · Web page: https://cgglider.com/docs/checks/structure/

Sections of this page: [Overview](https://cgglider.com/docs/checks.md) · [Wiring report](https://cgglider.com/docs/checks/wiring.md) · [Structure report](https://cgglider.com/docs/checks/structure.md) · [Scene & script reports](https://cgglider.com/docs/checks/scene-script.md) · [Unit report](https://cgglider.com/docs/checks/units.md) · [Working with failures](https://cgglider.com/docs/checks/workflow.md)

| Issue | Level | Means |
| --- | --- | --- |
| No descriptive name (node or group) | failure | An operator would see a raw id. Name it. |
| Driven on air but in no group | failure | Group it so the operator can drive it as one unit. |
| …with no sibling to group it with | warning | Place it in a named group manually. |
| Repeating group inside a repeating group | failure | Flatten one of them. |
| Group nested more than 4 deep | failure | Flatten the hierarchy. |
| Group wrapping a single node | info | Consider ungrouping it. |

> **Why naming is a failure, not a nit:** Every other system on the page — bindings, the rundown, the deck, agents — addresses components by name. Unnamed nodes make all of them ambiguous.