> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fieldpal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Conditional sections

> How to show fields only when another field's answer meets a condition.

A **Conditional section** is a group of fields that stays hidden on the form until another field on the same template is answered a certain way. Use it to ask follow-up questions only when they're relevant, instead of showing every possible field to every field worker.

For example: only ask for a damage description and photo when a condition rating comes back **Red**, or only ask for a reason when someone answers **No** to a checkbox.

## How it works

Every conditional section has three parts:

* **A trigger field** — one other field on the template, chosen from a dropdown of its siblings.
* **A list of matching values** — one or more values, one per line. The section appears if the trigger field's answer matches *any* value in the list (an OR match).
* **Inner fields** — the fields that only appear once the condition is met. These can be any field type, including short text, image upload, or PDF upload.

<Note>
  A conditional section can't use another conditional section as its trigger. The Field dropdown only lists non-conditional siblings.
</Note>

## Step 1: Add a Conditional section field

Open your template, scroll to the **Fields** section, and click **＋ Add field**. Choose **Conditional section** from the bottom of the type picker.

<Frame>
  <img src="https://mintcdn.com/fieldpal/YY3O4Wx59ZPa2wO2/images/templates/conditional-sections/02-step02-field-type-picker.png?fit=max&auto=format&n=YY3O4Wx59ZPa2wO2&q=85&s=971c8683ece9734c28bffcd2877973a2" alt="Field type picker with Conditional section highlighted" width="1440" height="1489" data-path="images/templates/conditional-sections/02-step02-field-type-picker.png" />
</Frame>

## Step 2: Name the section

Click the new field row to open the **Edit field** panel. Set the **Field name** and, optionally, the **Section heading shown to the worker** — this defaults to the field name if left blank.

A **Section ID** is generated automatically from the section name.

<Warning>
  Don't change the Section ID after reports have been submitted. It's a stable runtime key — changing it breaks references in reports that were already submitted using the old ID.
</Warning>

## Step 3: Set the trigger field and matching values

Scroll down in the panel to **Show this section when…**.

<Frame>
  <img src="https://mintcdn.com/fieldpal/YY3O4Wx59ZPa2wO2/images/templates/conditional-sections/03-step03-trigger-rag.png?fit=max&auto=format&n=YY3O4Wx59ZPa2wO2&q=85&s=b7d2c16986eb2613532067ef950c3fcf" alt="Show this section when panel, trigger field set to new_rag equalling Red" width="440" height="1000" data-path="images/templates/conditional-sections/03-step03-trigger-rag.png" />
</Frame>

* **Field** — pick the sibling field whose answer should control visibility.
* **…equals one of these values** — list the value or values that reveal the section, one per line.

In the example above, the trigger field is a RAG field and the listed value is `Red`, so the section only appears if the field worker sets that rating to Red.

The same pattern works with any field type as the trigger. A short text field can gate a section on an exact answer:

<Frame>
  <img src="https://mintcdn.com/fieldpal/YY3O4Wx59ZPa2wO2/images/templates/conditional-sections/04-step04-trigger-shorttext.png?fit=max&auto=format&n=YY3O4Wx59ZPa2wO2&q=85&s=50b1cae60e9c00061269faa1bef43e58" alt="Trigger field set to a short text field equalling james" width="440" height="1000" data-path="images/templates/conditional-sections/04-step04-trigger-shorttext.png" />
</Frame>

And a combo box can gate a section on one of its option values:

<Frame>
  <img src="https://mintcdn.com/fieldpal/YY3O4Wx59ZPa2wO2/images/templates/conditional-sections/05-step05-trigger-combobox.png?fit=max&auto=format&n=YY3O4Wx59ZPa2wO2&q=85&s=ad098161b38c589ba8e9f08409a29fe7" alt="Trigger field set to a combo box field equalling no" width="440" height="1000" data-path="images/templates/conditional-sections/05-step05-trigger-combobox.png" />
</Frame>

<Tip>
  For a combo box or checkbox trigger, match the option's underlying value (for example `yes` / `no`), not necessarily its display label, if the two differ.
</Tip>

## Step 4: Add inner fields

Under **Inner fields**, click **＋ Add inner field** for each field that should only appear once the condition is met. These work exactly like top-level fields — name them, pick a type, configure options — but they're nested inside the section rather than sitting loose on the form.

Click **Apply** to save the conditional section, then save the template as normal.

## Tips

* Matching is OR-based across multiple lines, not a range or comparison — there's no "greater than" or "not equal to," only "equals one of these listed values."
* If you change the trigger field or values later, it only affects future submissions. Reports submitted under the old rule keep their answers.
* Data entered into a conditional section's inner fields is preserved even if the section is later hidden by a change to the trigger's answer — it just doesn't display.

<Card title="Field types reference" icon="list" href="/templates/field-types">
  See the full list of field types available in report templates, including Conditional section.
</Card>

<Card title="Conditional sections in a report" icon="smartphone" href="/app/conditional-sections">
  See how these appear to the field worker filling in the form.
</Card>
