> 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/stage-outcomes.md).

# Stage Outcomes

How a stage ends — moving to the next stage, closing the Job, or both, plus anything that should happen automatically when it does.

An **Outcome** is a named way a stage can end — "Client Approved", "Client Declined", "Not Proceeding" — shown as buttons on the Job when the adviser is ready to move it forward. Each stage can have as many outcomes as make sense.

## Where to find it

**Home → Settings → Workflow Templates →** a template **→ Stages** tab **→** open a stage **→ Outcomes** section **→ + Add Outcome**.

## Fields

| Field                          | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Outcome Label** *(required)* | The button text an adviser clicks, e.g. "Approved".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| **Display Order**              | Left-to-right button order.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Next Stage**                 | What picking this outcome does — see below.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Evaluation Mode**            | `Manual` — the normal case, a person clicks the button. `Result(s) Exists` / `Result Empty` — for outcomes decided automatically rather than clicked (e.g. "did a Fact Find record get created for this client during this stage?"). `When all actions complete` — the engine picks this outcome by itself once nothing attached to it is still pending; this is what a [Parallel Sub-Jobs](/workflow-automation/parallel-sub-jobs.md) outcome uses under the hood, set automatically when you turn on **Wait for the sub-job to complete** on one of its Job actions rather than something you pick here directly. |
| **Icon**                       | Icon on the outcome button.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Description**                | Internal notes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |

### Next Stage: Move to Stage vs Close Job

The **Next Stage** picker offers every other stage in the template, **plus a Close Job option**. Picking a real stage moves the Job there when this outcome is chosen; picking Close Job marks the Job Completed instead — no need to invent a dummy "Closed" stage just to end a workflow.

### Attaching actions to an outcome

Any action type available under Stage Actions can also be attached directly to a specific outcome — "when *this* outcome is picked, also send this email / create this task / kick off this Job". These fire **immediately**, the moment the outcome is clicked — they don't have the day-offset/recurring timing options a stage-level action has, since there's no waiting involved; the outcome being picked *is* the trigger.

{% hint style="success" %}
**🆕 An outcome can hold the Job open, not just fire-and-forget.** A **Job**-type action attached to an outcome can have **Wait for the sub-job to complete** turned on — the outcome then keeps the Job on its current stage until that sub-job (or several, with **Adviser chooses whether to run** also on) is done, and moves the Job on by itself the moment it is. See [Parallel Sub-Jobs](/workflow-automation/parallel-sub-jobs.md) for the full setup — the classic case is a signed-advice outcome that launches Super/Investment/Insurance implementation and only lets the file move to review once all three are finished.
{% endhint %}

## See also

* [Building Job Stages](/workflow-automation/building-job-stages.md)
* [Stage Actions — Overview](/workflow-automation/stage-actions-overview.md)
* [Parallel Sub-Jobs](/workflow-automation/parallel-sub-jobs.md) — an outcome that launches and waits on several Jobs at once