Understand approval phases, steps, and routing
Inspect a form workflow and check how submissions reach the right reviewers.
Table of Contents
Who this is for: administrators responsible for approval routing.
Ready to configure a workflow? Follow Build an approval workflow for step-by-step instructions, screenshots, condition examples, and a testing checklist.
Open the workflow
- In admin view, open Form builder.
- Select the form, then the Workflow tab.
- Read the phases, steps, routing summaries, and conditions.
- Use a step’s Configure control to inspect its available settings before changing it.
Read phases and steps
A phase is a stage of the approval workflow. A step is an individual review within that stage. A phase contains one or more steps. Phases establish the sequence of review; steps define the reviewers and rules for each review.
| Concept | What it controls | When to use it |
|---|---|---|
| Phase | When a group of reviews takes place in the workflow. Phases run in sequence. | Create a separate phase when a review must wait for the required reviews in the preceding phase. |
| Step | A particular review, including who receives it and the conditions under which it is required. | Add another step in the same phase when reviews can run alongside one another. |
How phases and steps work together
The first phase can start when a request is submitted. Applicable steps within the same phase run in parallel: one step does not have to finish before another step in that phase starts. The workflow proceeds to the next phase after the required approvals in the current phase are complete. Conditions determine which steps apply to a particular submission, so not every submission follows every configured step.
A step can route to the submitter’s manager or an approver group. Its settings can also define conditions, escalation, and whether updated entries need another review. A step is not necessarily one person: an approver group can contain multiple people.
Example: manager review, then specialist reviews
Suppose your policy requires manager approval before Compliance and HR review a request:
- Phase 1 — Manager review: one step routes the request to the submitter’s manager.
- Phase 2 — Specialist review: a Compliance step and an HR step run alongside each other, when their conditions apply. Neither specialist step has to wait for the other to start.
If HR must wait until Compliance has approved, put HR in a third phase instead. Putting HR and Compliance in the same phase would allow them to review in parallel.
Choose the right workflow control
- Add a step that runs alongside: adds a parallel review within the current phase.
- Add a phase here or Add the next phase: adds a separate stage in the review sequence.
- Configure: opens a step’s reviewer and routing settings.
The screenshot below shows a different configuration: Manager and Compliance are in separate phases, with a later HR phase. This makes those reviews sequential.

Review unmatched submissions
The Unmatched submissions area controls what happens when no step matches a submission. Available options include automatic approval or routing to an approver group. Select the behavior that matches your organization’s policy.
This is different from a matching step whose approver cannot be found. Such a step waits for an approver unless it has its own escalation.
Check dependencies
The What it reads area identifies questions used by the workflow. Removing or narrowing those questions can change the approval path. Review these dependencies before changing the form.

Verify changes
Test examples that match each conditional path, examples that match no step, and examples with an unavailable manager or empty approver group. Check the resulting review timeline. Confirm saving and publishing requirements before relying on a change.
Prepare reviewer destinations and risk-based routing
Use Configure approver groups and routing tables to inspect resolved group members and routing-table dependencies before publishing. If routing uses a risk bucket, confirm Risk scoring in the form's Settings and test the intended bucket paths. See Read AI-generated risk information.
Automatic approval applies only when the configured unmatched behavior permits it. It is separate from the case where a matched step has no eligible approver.
Understand decisions and drafts
Reviewers can use Submit decision to apply an eligible item’s decision or Save draft to retain an unfinished choice. Bulk actions distinguish saving drafts from submitting decisions.
A saved draft does not complete the step. Deciding one recipient or benefit line does not automatically decide every other line. See Review and act on a request for individual decisions, outcomes and bulk actions.