Conditional Logic

Conditional logic lets you create dynamic forms that adapt based on the answers your field team provides. Instead of showing every field to every user, you can show or hide fields, skip entire sections, or require certain answers only when specific conditions are met. This keeps forms short and relevant.

How conditional logic works

At its core, conditional logic follows a simple pattern: If a field has a certain value, then perform an action on another field.

For example:

  • If "Damage Found?" equals "Yes," then show the "Describe Damage" text field.
  • If "Asset Type" equals "Electrical," then show the "Voltage Rating" number field.
  • If "Condition Rating" is less than 3, then require the "Photo Evidence" field.

Setting up a condition

  1. Open your form in the Form Builder.
  2. Click the field you want to control (the field that should be shown, hidden, or required conditionally).
  3. In the right panel, scroll to the Visibility section.
  4. Click Add Condition.
  5. Configure the condition:
    • Source field -- The field whose value determines the behavior.
    • Operator -- How to evaluate the value (equals, does not equal, contains, is greater than, is less than, is empty, is not empty).
    • Value -- The specific answer to check for.
  6. Choose the action: Show this field or Hide this field when the condition is true.
  7. Click Save.

The Form Builder displays a small lightning-bolt icon on fields that have conditions applied, so you can quickly see which fields are dynamic.

Combining multiple conditions

You can add multiple conditions to a single field using AND or OR logic:

  • AND -- All conditions must be true. Example: Show "Emergency Contact" only if "Injury Reported?" is "Yes" AND "Severity" is "High."
  • OR -- At least one condition must be true. Example: Show "Additional Notes" if "Status" is "Failed" OR "Status" is "Needs Repair."

To add another condition, click Add Condition again. Then choose whether the conditions are combined with AND or OR using the toggle above the conditions list.

Conditions on sections

You can also apply conditional logic to entire sections, not just individual fields. This is useful for large form segments that only apply in certain situations.

For example, if your form has a "Hazardous Materials" section, you can hide it entirely unless the user selects "Yes" for "Hazardous Materials Present?"

To set a condition on a section:

  1. Click the section header in the Form Builder.
  2. Open the Visibility settings.
  3. Add your condition just like you would for a field.

When a section is hidden, all fields within it are also hidden and not required, even if they are marked as required in their individual settings.

Conditional requirements

Beyond showing and hiding fields, you can make a field required only when a condition is met:

  1. Click the target field.
  2. In the Validation section, set Required to "Conditional."
  3. Define the condition (same interface as visibility conditions).

This is valuable for situations where extra documentation is needed only in specific scenarios. For instance, you might require a photo only when an inspection fails, but leave it optional when the inspection passes.

Supported operators

Operator Works with Example
Equals All field types Status equals "Complete"
Does not equal All field types Type does not equal "N/A"
Contains Text fields Notes contains "urgent"
Is greater than Number fields Temperature is greater than 100
Is less than Number fields Score is less than 5
Is empty All field types Comments is empty
Is not empty All field types Photo is not empty

Testing conditional logic

Always test your conditions before publishing:

  1. Click Preview in the Form Builder toolbar.
  2. Fill in the source fields and verify that dependent fields appear, disappear, or become required as expected.
  3. Try edge cases -- what happens when the source field is left empty?

Best practices

  • Keep conditions simple. One or two conditions per field is usually enough. Complex chains of conditions are harder to maintain and debug.
  • Name your fields clearly. When you see a condition like "If Field_12 equals 3," it is hard to understand. Descriptive labels make conditions self-documenting.
  • Document your logic. For forms with many conditions, keep a simple reference document that lists which fields depend on which answers.
  • Use section-level conditions when several fields share the same visibility rule. This is cleaner than applying the same condition to each field individually.

Need more help? Contact our support team.

Open the Web App