Layouts and stages
A layout decides where a field appears. It never decides which values are legal — that belongs to the field. Find layouts under Settings → Layouts.
Building a layout
- Open a layout, or create one.
- Drag a field from the palette onto a stage.
- Set its placement options.
- Preview to see the real form.
- Publish when you are happy.
Placement options
| Option | Effect |
|---|---|
| Width | Full or half. Long text, asset pickers, URLs and formulas default to full because they need the room. |
| Important | Highlights an empty value without blocking anything. |
| Read-only | Visible but not editable at this stage. |
| Hide when empty | Keeps the form short on records where the field does not apply. |
| Conditional visibility | Show only when another field has a given value. |
| Label and help override | Reword the field for this context without changing it globally. |
Dependency validation
If a field’s options are filtered against another field — cities depending on country — the builder checks that the other field is on the same layout and earlier. If it is not, the row is badged so you can see it before publishing. This check is the reason “just drag the field on” is safe advice.
Stages
Stages are the lifecycle a risk moves through — Identification, Assessment, Assessment Approval, Risk Control, Risk Treatment, Closed.
On each stage you decide which fields must be filled before anyone can leave it. Two tiers, deliberately:
- Required to continue — blocks the transition.
- Important — highlights it, does not block.
The requirement is stored separately from the placement, so making a field required at one stage can never accidentally hide it at the next.
Stages are shared by every register. Editing them reaches every register, the Stage column, saved filters, reports and score history — so the publish dialog separates lifecycle changes from layout changes and warns accordingly. Deleting a stage requires migrating the records currently sitting in it.
Draft, preview, publish
Every edit is a draft until published. Preview renders the actual form, including live option filtering. Publish shows a computed diff plus the blast radius — which registers are affected and how many existing records.
Accessibility
Dragging is not the only way to reorder. Every row has up and down buttons, and Alt plus the arrow keys moves a focused row. This is required for WCAG 2.5.7 conformance, so please do not remove it from your process documentation either.