Lorixen.
EN

Conditional Logic in Forms: The Right Questions for Each Person

Short answer: Conditional logic lets a form show, hide or skip questions based on earlier answers, so each person only sees what applies to them. Sketch the branches as a decision tree on paper first, keep every rule tied to one clear trigger question, and never make a field required when it might be hidden. Then walk every path yourself before the form goes live.

A form that asks a homeowner about loading-dock access tells the visitor you weren't thinking about them. Conditional fields fix that, but they also create new ways for a form to break quietly. Below: a worked tree, then rules you can check.

A worked decision tree (hypothetical)

Imagine a small renovation company in Ontario with one "Request a quote" form. This is an illustrative example, not a real client. The owner wants different details depending on who is asking.

Question 1: Is this for a home or a business?

  • If "Home" → show Which rooms? (checkboxes) and Do you own the property? (yes/no).
    • If Do you own the property? = No → show a short note asking them to confirm the owner is on board, plus an optional Owner's contact field.
    • If Yes → skip straight to timing.
  • If "Business" → show Company name, Type of space (office, retail, restaurant, other) and Can work happen after hours?
    • If Type of space = Restaurant → show Is the kitchen part of the job?
    • If Other → show a free-text Describe the space field.

Question 2 (everyone): When would you like the work to start?

  • If "Within 2 weeks" → show Is this urgent repair work? and a line explaining that rush requests are answered by phone.
  • Otherwise → continue to contact details.

End: everyone reaches the same contact block and the same submit button, but the thank-you message changes: business enquiries are told to expect a site visit call, home enquiries are told to expect an email with a booking link.

Notice the shape: two trigger questions near the top, shallow branches, and a shared ending. That is far easier to maintain than a tree five levels deep.

Show/hide, page jumps and endings: which tool does what

Most form builders give you three kinds of logic, sometimes under different names.

Show or hide a field. In Gravity Forms, you enable conditional logic on a field and choose to show or hide it when all or any of your conditions are met. Tally calls these "show or hide blocks" and also lets you group conditions with "all" or "any". This is the right tool for one or two extra questions inside a page.

Skip or jump to a page. Gravity Forms has page conditional logic, which decides whether a whole page is shown or skipped based on earlier answers, plus a separate rule for whether the Next button appears. Tally offers "jump to page". Typeform's logic jumps can send a respondent to another question or to a default or custom thank-you screen. Use page-level branching when a group of questions belongs together, like the business section in the tree above.

Change the ending. Different confirmation messages or redirects are a gentle way to set expectations without adding questions. Tally can redirect to different URLs, and Gravity Forms supports conditional logic on confirmations and notifications.

These products are examples only. Check your own builder's documentation, because the wording and limits differ.

The required-field trap

This is where most broken forms come from. You mark Company name as required, then hide it for home enquiries. What happens on submit depends on the tool. Gravity Forms states that fields hidden by conditional logic are ignored on submission and not saved in the entry, which avoids the trap but means hidden data is gone. Other builders, or custom-coded forms, may still try to validate a hidden required field, and the visitor sees an error about something they cannot see.

Safer habits:

  • Make a field required only inside the branch where it appears. Tally, for example, can make answers required based on the respondent's input.
  • If a value hidden in one path feeds a later calculation, test that calculation with the field hidden.
  • Don't rely on hidden fields to "keep" a value from a branch the person backed out of. Treat each submission as only what was visible at the end.

Accessibility when fields appear and disappear

A sighted mouse user notices a new field slide in. A screen-reader user may not. MDN's guidance on aria-live explains that a live region lets you announce content changes the user didn't directly trigger; a "polite" region waits until the user is idle. For conditional fields, a short announcement such as "Two more questions added below" is usually enough.

For multi-page branches, the W3C forms tutorial recommends telling people at the start how many steps will follow, showing progress on each step, and making optional stages easy to recognize and skip. With branching, the step count can change, so word your progress indicator honestly ("Step 2") or update the total when a path adds a page.

Rules checklist before you publish

  • [ ] Every branch is drawn on one page, with each trigger question named.
  • [ ] Trigger questions use fixed choices (radio buttons, dropdowns), not free text. Gravity Forms warns that special characters or HTML in choice values can stop rules working, and recommends plain-text values.
  • [ ] No rule depends on its own field. Gravity Forms doesn't support self-referencing rules, and other tools behave unpredictably.
  • [ ] Nested rules are avoided or kept shallow; check whether your tool supports them at all.
  • [ ] Required fields are required only where they are shown.
  • [ ] Revealed fields sit right after their trigger and are announced to assistive technology.
  • [ ] Field labels in the builder are descriptive, not "Untitled 7". Tally's troubleshooting advice makes the same point: clear field names make logic easier to audit.
  • [ ] Notification emails and your CRM receive the right fields for each path.
  • [ ] The form still feels fast on a phone. Gravity Forms notes its logic runs in the browser, and very large forms with many rules can slow down; splitting into smaller forms is its suggested fix.

Testing every path

Write the paths out as a list: Home + owner + soon, Home + tenant + later, Business + restaurant + soon, and so on. Submit one test entry for each and check three things: what the visitor saw, what landed in the inbox or CRM, and which thank-you message appeared. Tally's own troubleshooting tips suggest several test runs with different answers each time; doing it as a written list means nobody skips the awkward combinations. Re-run it whenever a choice label changes.

FAQ

Do conditional fields hurt form completion?

Usually the opposite, because people see fewer irrelevant questions. Problems come from broken rules, not the logic itself.

Can I use conditional logic in a plain HTML form?

Yes, with JavaScript, but you then own validation, announcements and server-side checks yourself. Builders handle much of that for you.

Should I branch on a free-text answer?

Avoid it. People type "Restaurant", "restaurant " or "cafe/bar". Use a fixed list with an "Other" option instead.

What happens to data in a branch someone abandons?

It depends on the tool. In Gravity Forms, hidden fields are not saved. Check your builder so you don't expect data that was never stored.

Planning a quote or application form with a few too many "it depends" questions? Send us the questions you ask today and we can map the branches with you.

Sources

WhatsAppLet’s talk