Lesson 3 of 8 · 10 min

Stage types explained

Sequential vs Decision stages, and entry requirements.

Lesson 3 of 8

Every stage in a workflow is one of two types, and any stage can be gated by entry requirements. This lesson covers both so you can model choices and approvals correctly.

Before you start

  • A workflow open in the builder (see 'Creating your first workflow')
  • Admin access ('manage workflows')

Two stage types: Sequential and Decision

Open a stage on the canvas and the editor's Setup tab shows a Type control with exactly two options: 'Sequential' and 'Decision'. Sequential is the default straight-through stage — a matter completes it and moves on. Decision is a branch point: the matter pauses so the team can choose which outgoing transition to follow (e.g. 'Unconditional' vs 'Terminated'). Rename each outgoing transition on a Decision stage so the choices are clear. There are no 'Parallel' stages in MatterFirst — model concurrent work with tasks and automations instead.

Initial and terminal stages

Two checkboxes on the Setup tab mark a stage as the 'Initial stage' (where matters start) and as a 'Terminal stage' (an end state such as Completed or Cancelled). Every workflow needs one initial stage and at least one terminal stage.

Approval is an entry requirement, not a stage type

MatterFirst has no dedicated 'Approval gate' stage. Instead, any stage can carry entry requirements on its Requirements tab — conditions that must be satisfied before a matter is allowed to move into the stage. The available requirement types are 'All tasks completed', 'Contact type present', and 'User approval'. Use 'User approval' to require a named person to sign off before a matter can enter the stage — that is how partner sign-off and compliance gates are built.

  1. 1

    Set the stage type

    Click a stage on the canvas to open its editor, and stay on the Setup tab. Use the Type control to pick 'Sequential' or 'Decision'. Choosing 'Decision' reveals a panel explaining the branch and showing how many outgoing transitions (branches) the stage currently has. The Setup tab also has the 'Initial stage' and 'Terminal stage' checkboxes.

    The Setup tab: choose Sequential or Decision, and mark initial/terminal stages.
  2. 2

    Add an entry requirement

    Switch to the Requirements tab. It explains the 'Entry gate' — a matter can move into this stage only once its requirements are satisfied. Under 'Add requirement', pick a type ('All tasks completed', 'Contact type present', or 'User approval'), choose the specific value where needed, and click 'Add Requirement'. Use 'User approval' for partner or compliance sign-off.

    Requirements gate entry to a stage — including a 'User approval' sign-off.

Tips & pitfalls

  • Give each branch off a Decision stage a clear transition label (e.g. 'Approve', 'Reject') — that label is exactly what the team clicks to move the matter along.
  • A 'User approval' requirement gates entry into the stage; it is not a separate approval stage. If a matter seems stuck, check the target stage's Requirements tab.

Key takeaways

  • Stages are either Sequential (straight-through) or Decision (a team branch point)
  • There are no Parallel or Approval-gate stage types
  • Approval is a per-stage entry requirement ('User approval'), alongside 'All tasks completed' and 'Contact type present'
Creating your first workflow Connecting actions to stages

Put the lesson into practice.

Book a guided session and our team will help you configure MatterFirst for your own practice.

Book a session Back to the Academy