---
title: How to Use Conditional Logic on Forms
description: "Conditional logic lets you build smarter forms that adapt to the person filling them out. Instead of showing every field at once, you can set up conditional paths — groups of follow-up fields that only appear when a specific answer is given to a parent question.\n\nFor example, a safety form might ask \"Was there an incident?\" — if the answer is True, additional fields for incident details, photos, and descriptions appear automatically. If the answer is False, those fields stay hidden and the form stays short."
---

[Skip to content](https://help.jointimecloud.com/how-to-use-conditional-logic-on-forms#main-content)

[Contact us](https://help.jointimecloud.com/kb-tickets/new?hsLang=en)

[![Timecloud-Logo-600-2](https://help.jointimecloud.com/hs-fs/hubfs/Timecloud-Logo-600-2.png?width=200&height=40&name=Timecloud-Logo-600-2.png)](https://help.jointimecloud.com/?hsLang=en)

Open main navigation

Close main navigation

- [Contact us](https://help.jointimecloud.com/kb-tickets/new)
- [Go to app.jointimecloud.com](https://app.jointimecloud.com/)

[Go to app.jointimecloud.com](https://app.jointimecloud.com/)

 Got questions? Ask away

- There are no suggestions because the search field is empty.

1. [Service Portal](https://help.jointimecloud.com/?hsLang=en)
2. [Forms & Checklists](https://help.jointimecloud.com/forms-checklists?hsLang=en)

# How to Use Conditional Logic on Forms

## Conditional logic lets you build smarter forms that adapt to the person filling them out. Instead of showing every field at once, you can set up conditional paths — groups of follow-up fields that only appear when a specific answer is given to a parent question. For example, a safety form might ask "Was there an incident?" — if the answer is True, additional fields for incident details, photos, and descriptions appear automatically. If the answer is False, those fields stay hidden and the form stays short.

**How It Works**

- A **conditional path** is a group of fields attached to a parent question.
- The path only appears when the parent's answer matches a condition you set.
- Only **True/False** and **Dropdown** field types can trigger conditional paths.
- You can nest paths up to **3 levels deep** (a follow-up question can have its own follow-up).
- Hidden fields are skipped entirely — they don't block submission and their values are not recorded.

 Setting Up Conditional Paths (Admin)

### **Adding a Conditional Path**

1. Open the **form editor** and navigate to the **field builder**.
2. Find the **True/False** or **Dropdown** field you want to use as the trigger.
3. Click the **+** button on that field — this is the **Add conditional path** action.
4. For **True/False** fields: the path is created automatically, defaulting to the first unused answer (True or False). You can have up to 2 paths — one for each answer.
5. For **Dropdown** fields with multiple options: a **Conditional Path Settings** dialog opens where you choose which answer(s) reveal the path. If only one unused option remains, the path is created automatically.

### **Conditional Path Settings**

The settings dialog lets you configure:

- **Condition** — which answer(s) reveal this path. For True/False parents, pick one. For Dropdown parents, you can select multiple options (the path appears when any of them is chosen).
- **Title** (optional) — a heading shown above the nested fields when filling out the form (max 100 characters).
- **Description** (optional) — additional instructions shown below the title (max 500 characters).

To edit these settings later, click the **Settings** (gear icon) on the conditional path box.

### **Adding Fields to a Conditional Path**

- Click **Add field** inside the conditional path box to add a new field directly into that path.
- You can also **drag and drop** existing fields into or out of a conditional path.
- Fields inside a path can themselves have their own conditional paths (up to 3 levels of nesting).

### **Removing a Conditional Path**

- Click the **Delete** (bin icon) on the conditional path box header.
- If the path contains fields, you'll be asked to confirm — removing the path also removes all fields nested inside it.

 What Form Fillers See

When someone fills out a form with conditional logic:

- The form starts by showing only the top-level fields.
- As they answer a question that has conditional paths, the matching follow-up fields **appear automatically** below.
- If they change their answer, the previous follow-up fields disappear and any new matching ones appear.
- Answers entered in a hidden path are cleared — only visible fields are submitted.
- If a conditional path has a **title** or **description**, it appears as a labelled section above the nested fields.

This works consistently on the **web app**, **mobile app**, and **public forms**.

**Viewing Submissions**

When reviewing a submitted form:

- Only the fields the submitter actually saw and answered are displayed.
- Nested fields are **indented** to show which conditional path they belong to.
- Branches the submitter never reached (because they gave a different answer) are hidden entirely.

**Tips**

- Start with a **True/False** or **Dropdown** question as your trigger — these are the only field types that support conditional paths.
- Use **titles** on your conditional paths to give context — e.g. "Incident Details" or "Hazard Information".
- Nesting deeper than 2 levels can make forms harder to fill out on mobile. Keep it simple where possible.
- A Dropdown with many options can have one conditional path per option — each path reveals different follow-up fields.
- Values already used by another path on the same parent are labelled *"used by another path"* in the settings dialog, so you can see at a glance which answers are taken.
- Removing or editing the parent field's options may affect its conditional paths — check the path settings if you change a Dropdown's options.

- [Account & Security](https://help.jointimecloud.com/account-security?hsLang=en)
- [Attendance & Timesheets](https://help.jointimecloud.com/attendance-timesheets?hsLang=en)
- [Award Interpretation](https://help.jointimecloud.com/award-interpretation?hsLang=en)
- [Biometric Scanners](https://help.jointimecloud.com/biometric-scanners?hsLang=en)
- [Employees](https://help.jointimecloud.com/employees?hsLang=en)
- [Forms & Checklists](https://help.jointimecloud.com/forms-checklists?hsLang=en)
- [Geofencing](https://help.jointimecloud.com/geofencing?hsLang=en)
- [Human Resources](https://help.jointimecloud.com/human-resources?hsLang=en#main-content)

    - [Organisation View](https://help.jointimecloud.com/human-resources?hsLang=en#organisation-view)
- [Integrations](https://help.jointimecloud.com/integrations?hsLang=en)
- [Job Tracking](https://help.jointimecloud.com/job-tracking?hsLang=en)
- [Leave Management](https://help.jointimecloud.com/leave-management?hsLang=en)
- [Mobile App](https://help.jointimecloud.com/mobile-app?hsLang=en#main-content)

    - [Kiosk](https://help.jointimecloud.com/mobile-app?hsLang=en#kiosk)
    - [Mobile App](https://help.jointimecloud.com/mobile-app?hsLang=en#mobile-app)
- [Payroll](https://help.jointimecloud.com/payroll?hsLang=en#main-content)

    - [Xero](https://help.jointimecloud.com/payroll?hsLang=en#xero)
    - [iPayroll](https://help.jointimecloud.com/payroll?hsLang=en#ipayroll)
    - [MYOB](https://help.jointimecloud.com/payroll?hsLang=en#myob)
    - [Smartly](https://help.jointimecloud.com/payroll?hsLang=en#smartly)
- [Reporting](https://help.jointimecloud.com/reporting?hsLang=en)
- [Roster](https://help.jointimecloud.com/roster?hsLang=en)
- [Settings](https://help.jointimecloud.com/settings?hsLang=en)
- [Shifts](https://help.jointimecloud.com/shifts?hsLang=en)
- [Time Clock](https://help.jointimecloud.com/time-clock?hsLang=en)
- [Dashboard](https://help.jointimecloud.com/dashboard?hsLang=en)

Service Desk

Copyright © 2025, Timecloud Ltd