> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow-automation/building-job-stages.md).

# Building Job Stages

Create and configure the stages a Job moves through.

Every Job Template is a series of **stages** — Prepare, Meet, Implement, Review, whatever suits the workflow. A Job always sits in exactly one stage at a time, moves forward (or sideways) via **Outcomes** (see [Stage Outcomes](/workflow-automation/stage-outcomes.md)), and stage entry/exit is what Stage Actions time themselves off.

## Where to find it

**Home → Settings → Workflow Templates →** pick a template **→ Stages** tab. Click **+ Add Stage** or the pencil icon on an existing stage.

## Fields

| Field                       | Notes                                                                               |
| --------------------------- | ----------------------------------------------------------------------------------- |
| **Stage Name** *(required)* | What shows on the Job's progress path.                                              |
| **Order** *(required)*      | Position in the sequence. Stages display and (by default) progress in this order.   |
| **Description**             | Internal notes — not shown to clients.                                              |
| **Days to Complete**        | Expected turnaround for this stage — drives due-date colouring/warnings on the Job. |

### Stage Assignment

Who owns a Job while it's sitting in this stage:

* **Account Team Role** — whoever holds that role on the Job's linked Account (e.g. "Primary Adviser", "Para-planner") automatically becomes the assignee when a Job enters this stage.
* **Specific User** — always the same named person, regardless of which Account the Job belongs to.

**Backup role**: tick **Has a backup account team role** and pick a fallback role — used automatically if the primary assignee (the Account Team Role above) isn't set on that particular Account, so a Job never ends up unassigned.

### Icon

Any Lightning Design System icon name (e.g. `standard:task`, `utility:check`) — shown on the Job's stage progress indicator.

### Advanced — Flow Hooks

**On Entry Flow API Name** / **On Exit Flow API Name** — for anything too custom for the Stage Actions builder, you can point a stage directly at your own Flow, fired the instant a Job enters or leaves it. Most workflows won't need this — it predates the Stage Actions system and is kept for backward compatibility and edge cases the builder doesn't cover.

## See also

* [Stage Outcomes](/workflow-automation/stage-outcomes.md) — how a Job actually moves out of a stage
* [Stage Actions — Overview](/workflow-automation/stage-actions-overview.md) — timed automation while a Job sits in a stage