> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/organization-level-configurations/opportunity-stage-validation-and-gating.md).
# Opportunity Stage Validation and Gating
Stages define how opportunities move through your pipeline. Rox lets you put **gates** on stages — rules that must be satisfied before a deal can leave a stage — and optionally enforce **sequential progression** so deals can't skip steps.
### Part 1 — Setting up gates to progress deals
A gate is a rule attached to a single stage. When a rep tries to move an opportunity *out* of that stage, Rox checks the rule first. If it fails, the deal stays put until the rule is satisfied.
**To set up a gate**
1. Go to **Settings → Opportunities → Stages**.
2. Click the **⋯** menu next to a stage and choose **Stage Validation**.
3. Configure any combination of the four tabs below, then click **Save**.
#### Reviewers — require approval to exit a stage
Turn on **Review Required** to make the stage wait for human approval before a deal can move forward.
* Choose one or more **approvers**.
* You can chain approvers into **sequential approval phases** — e.g., the deal first needs a manager's approval, and only then routes to the VP. Each phase must complete before the next begins.
* When a rep tries to advance the deal, an **approval request** is created and assigned to the configured reviewers. The deal does not move; it enters a pending state until every phase is approved.
* If a reviewer rejects, the deal stays in the current stage and the rep is notified.
#### Fields — require data before exit
Mark specific opportunity fields as required for the stage. If any required field is empty when a rep tries to advance the deal, Rox blocks the move and shows which fields are missing. Field checks always run *before* approvals, so reviewers never see incomplete deals.
#### Duration — track time in stage
Set a **maximum stage duration** in days. Note: duration does **not** block progression — it triggers reminders and notifications (see the Notifications tab). Use this to flag stuck deals, not to enforce a hard deadline.
#### Notifications
* **Notify approvers when input is required** — pings reviewers as soon as a deal lands in their queue.
* **Duration exceeded** — fires when a deal sits longer than the max duration you set.
* **Reminder schedule** — daily, weekly, or monthly nudges for pending items.
### Part 2 — Enforce sequential stage progression
By default, reps can move opportunities to any stage — including jumping straight from "Lead" to "Closed Won." Sequential Stage Progression prevents that.
**To enable it**
1. Go to **Settings → Opportunities**.
2. Scroll to **Sequential Stage Progression**.
3. Toggle it on.
**Behavior when enabled**
* Deals can only move **one stage at a time**, forward or backward, following the order shown in your Stages list.
* If a rep tries to skip a stage, Rox blocks the move and surfaces an error.
* Closed states (Closed Won, Closed Lost, Non Qualified) still follow the same rule — a deal must reach the final regular stage before it can be closed.
**When to use it**
Turn it on if your sales process depends on every deal going through each step (e.g., for forecasting accuracy or compliance). Leave it off if reps need flexibility to handle deals that arrive mid-funnel.
**Tip**: Sequential progression works alongside stage gates. A deal advancing one stage at a time still has to clear each stage's reviewers and required fields along the way.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.rox.com/development/product/organization-level-configurations/opportunity-stage-validation-and-gating.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.