# Navigation Rules in FeatureOS Forms

_By Sathi · Sep 18, 2025_

Navigation Rules in FeatureOS Forms allow you to create smart, **adaptive surveys by skipping, branching, or showing questions based on a user’s response.** Available only in **Wizard-type forms**, this feature makes surveys more dynamic, ensures respondents see only relevant questions, and improves the overall experience.

Here’s how a Navigation Rule looks inside the form builder:

![](https://vault.featureos.app/uploads/attachment/upload/ad64133123d9214caadcf5f38eb24435.png)

## How Navigation Rules Work

A navigation rule is made up of **three parts**:

1.  **Operator** – defines the condition type (e.g., equals, contains, is empty).
    
2.  **Value** – the specific answer or input to check against.
    
3.  **Go to Field** – the next question or section the respondent should jump to if the condition matches.
    

You can add multiple navigation rules within a single field to cover different scenarios, making the form highly flexible.

## Supported Operators by Field Type

Each field type supports different operators depending on the nature of the input. Below are the detailed options:

### 1. **Short Text, Long Text, Email, and URL Fields**

Operators available:

-   **Contains / Not Contains** – Useful for matching keywords in text responses.
    
-   **Equals / Not Equals** – For exact matches like email or URL.
    
-   **Is Empty / Is Not Empty** – To check whether a respondent skipped a field.
    

_Example_: If an Email field _is empty_, you could skip ahead to a reminder question asking for contact details.

### 2. **Switch Field**

Operators available:

-   **Is Checked**
    
-   **Is Not Checked**
    

_Example_: If a toggle is checked for “I want product updates,” direct the respondent to a preferences section.

### 3. **Number Field**

Operators available:

-   **Between**
    
-   **Equals / Not Equals**
    
-   **Greater Than / Greater Than or Equal**
    
-   **Less Than / Less Than or Equal**
    

_Example_: If _Years of Experience > 5_, skip junior-level questions and go directly to advanced ones.

### 4. **Date Field**

Operators available:

-   **Before / After**
    
-   **Between**
    
-   **On or Before / On or After**
    
-   **Equals / Not Equals**
    

_Example_: If the date entered is _before Jan 1, 2025_, direct respondents to legacy product questions.

### 5. **Dropdown, Poll, and Checkboxes**

Operators available:

-   **Equals / Not Equals**
    
-   **Contains / Not Contains**
    
-   **Is Part Of / Is Not Part Of**
    

_Example_: If a respondent selects _Python_ in a “Preferred Language” dropdown, take them to a question specific to Python use cases.

### 6. **Slider Field**

Operators available:

-   **Between**
    
-   **Equals / Not Equals**
    
-   **Greater Than / Greater Than or Equal**
    
-   **Less Than / Less Than or Equal**
    

_Example_: If satisfaction score (0–10) is _≤ 5_, skip ahead to a follow-up question asking why the rating was low.

### 7. **Star Rating and NPS Rating**

Operators available:

-   **Between**
    
-   **Equals / Not Equals**
    
-   **Greater Than / Greater Than or Equal**
    
-   **Less Than / Less Than or Equal**
    

_Example_: If NPS score is _≥ 9_, direct respondents to a referral section. If _≤ 6_, show a feedback text box asking how you can improve.

## 📌 Why Use Navigation Rules?

-   **Personalization** – Tailor the survey flow based on user responses.
    
-   **Efficiency** – Skip irrelevant questions and reduce completion time.
    
-   **Targeted Insights** – Collect only the data that matters for each respondent.
    
-   **Higher Completion Rates** – A smoother experience encourages respondents to finish the form.
    

## **🛠** Steps to Apply Navigation Rules

1.  Go to the **Designer** tab of your form.
    
2.  Select a field and scroll to the **Navigation Rules** section on the right panel.
    
3.  Click **Add Navigation Rule**.
    
    -   Choose the **Operator** (e.g., Equals, Contains).
        
    -   Enter the **Value** (the expected response).
        
    -   Select the **Go to Field** (the next question to display).
        
4.  Add more rules if needed.
    
5.  Click **Save Changes**.
    

## **Need Help?**

Email us at [**support@featureos.app**](mailto:support@featureos.app) or drop your question on our [support board](https://feedback.featureos.app/admin/kb/a/viewing-and-managing-form-responses/en#)! 😊

[View this article on the web](https://help.featureos.app/en/articles/navigation-rules-in-wizard-type-form)