Skip to Content

Stages & gates

Stages show the steps in your firm’s workflow. A gate checks required work before an engagement leaves a stage.

Move an engagement

  1. Open Workflow and select the workflow.
  2. Drag the engagement card to the target stage, or use the stage control in the engagement detail.
  3. Review any Required items not complete message.
  4. Complete the listed work, or enter an explanation and choose Move anyway when that option is available.

You need engagement-editing permission. A rejected move leaves the engagement in its current stage.

Understand gate modes

ModeWhat happens when required work remains
NoneThis gate does not check tasks or blockers.
FlexibleA reason is required to move past incomplete requirements.
StrictThe move is blocked until requirements are resolved or an allowed override includes a reason.
LockedRequirements must be resolved; a reason does not override the gate.

Requirements include unresolved mandatory tasks in the departing stage and active engagement blockers. Completed, Cancelled, and N/A tasks count as resolved for the gate; use the status that truthfully describes the work.

Move back or finish a stage

The detail’s backward-stage control asks for context before moving back. Review the current stage after reopening required work from an earlier stage, because it can pull the engagement back to that stage.

Completing tasks can produce stage-completion feedback. Review the offered action and the resulting stage; do not assume every task completion advances the engagement.

Your firm configures gate modes in Custom pipelines. See Blockers for handling the issues named in a gate message.

Last updated on