Building Multi-Page Forms with Conditional Logic in monday.com

Published on April 24, 2026

Long forms kill completion rates. When someone sees 20 fields on a single page, they are more likely to close the tab than fill it out. Multi-page forms with conditional logic solve this — they break the experience into manageable steps and show only the fields that matter.

Here is how to build them in FormFlow.

Quick answer

• Use multi-page forms to reduce overwhelm and improve completion.
• Use visibility rules to control fields/pages based on answers.
• Use form routing when you need entirely different form layouts from one entry link.

Why Multi-Page Forms Work Better

• Less overwhelming — Users see 3-5 fields at a time instead of 20
• Higher completion rates — Progress indicators motivate people to finish
• Smarter data collection — Conditional logic hides irrelevant fields
• Better organization — Group related fields together logically

Creating Multi-Page Forms

Adding Pages

1. Open your form in the FormFlow builder
2. Look at the Left Panel — this is your page manager
3. Click Add Page to create a new page
4. Give each page a clear title (e.g., “Contact Details”, “Project Information”, “Additional Notes”)

Organizing Fields Across Pages

Drag fields from the right panel into the center panel. The center panel shows the currently selected page. Switch between pages in the left panel to add fields to different pages.

A good rule of thumb: Group 3-7 fields per page, organized by topic.

Example: Job Application Form

Navigation Between Pages

FormFlow automatically adds Next and Previous buttons between pages, and a Submit button on the final page. Users see a progress indicator showing which page they are on and how many remain.

You can customize the button text in your form settings — for example, changing “Next” to “Continue” or “Submit” to “Send Application”.

Visibility Rules: Show and Hide Fields Dynamically

Visibility rules let you control which fields appear based on what the user has already entered. This keeps forms short and relevant.

How Visibility Rules Work

1. Click on a field in the form builder
2. Open the Visibility settings
3. Define a condition: “Show this field when [another field] [equals/contains/is not empty] [value]”
4. The field remains hidden until the condition is met

Example: Support Ticket Form

You have a Category dropdown with options: Bug Report, Feature Request, and General Question.

• When Category = Bug Report, show: “Steps to Reproduce”, “Browser”, “Screenshot Upload”
• When Category = Feature Request, show: “Describe the Feature”, “Priority Level”
• When Category = General Question, show: “Your Question” (long text field)

Without visibility rules, the user would see all of these fields. With them, they only see what is relevant to their selection.

AND/OR Logic

For more complex conditions, you can combine rules:

• AND — All conditions must be true. Example: Show “Billing Address” when Country = “USA” AND Order Type = “Physical”
• OR — Any condition can be true. Example: Show “Urgent Flag” when Priority = “High” OR Category = “Bug Report”

Reusable Conditions

If multiple fields share the same visibility condition, you can create a reusable condition and apply it to all of them. This saves time and keeps your logic consistent.

For example, if five fields should only appear when “Employment Type = Full-Time”, create one reusable condition and attach it to all five fields instead of configuring each one individually.

Page-Level Visibility

Visibility rules are not limited to individual fields. You can apply them to entire pages.

Example: Multi-Department Request Form

• Page 1: General Info — Always visible. Includes a “Department” dropdown.
• Page 2: IT Request — Only visible when Department = “IT”. Shows fields for system access, software needs, hardware requests.
• Page 3: HR Request — Only visible when Department = “HR”. Shows fields for leave type, dates, manager approval.
• Page 4: Facilities Request — Only visible when Department = “Facilities”. Shows fields for location, issue description, urgency.
• Page 5: Confirmation — Always visible. Shows a summary and submit button.

The user only sees the pages relevant to their department. A three-page experience instead of a five-page one.

Form Routing

Form routing takes conditional logic further. Instead of just hiding and showing fields, it lets you display entirely different forms based on a board column value.

How Form Routing Differs from Visibility Rules

Example: Client Onboarding

You have a “Client Tier” status column on your board with values: Enterprise, Professional, and Starter.

• Enterprise clients see a comprehensive form with fields for legal contacts, SLA preferences, and dedicated account manager selection
• Professional clients see a mid-level form with standard onboarding fields
• Starter clients see a minimal form with just the essentials

The form automatically adjusts based on the client tier — no need to create three separate forms.

Setting Up Form Routing

1. Open your form in the FormFlow builder
2. Go to Form Routing settings
3. Select the board column to route on (e.g., Status, Dropdown)
4. Define which form layout appears for each column value

Best Practices

Keep Pages Focused

Each page should cover one topic. Do not mix “Contact Details” and “Payment Information” on the same page.

Use Clear Page Titles

Tell users what each page is about. “Step 2 of 4: Project Details” is better than “Page 2”.

Limit Conditional Depth

Avoid nesting conditions more than two levels deep. If your logic is getting complex, consider using form routing instead of visibility rules.

Test Every Path

With conditional logic, users can take different paths through your form. Test each combination to make sure every path leads to a valid submission.

Show a Progress Indicator

Multi-page forms should always show users where they are. FormFlow includes progress indicators by default — keep them visible.

Putting It All Together

Here is a real-world example combining all three features:

Scenario: Employee equipment request form

1. Page 1 (always visible): Employee name, department, request date
2. Form routing based on department: IT employees see tech-specific options, other departments see general equipment
3. Page 2 with visibility rules: If request type = “Laptop”, show model preferences and specifications. If request type = “Furniture”, show dimensions and location
4. Page 3 (always visible): Manager approval, priority level, additional notes

The result: a single form that handles every department and every equipment type, while each user sees only what is relevant to them.