Conditional Logic in Forms: The Feature That Doubles Completion
Conditional logic shows each respondent only the questions that apply to them. Here is how to design rules that shorten forms without losing data.
Long forms are not the problem
Irrelevant questions are. A 40-field form where each person sees 12 relevant fields feels short. A 15-field form where five questions clearly do not apply feels like a chore, and people abandon it.
Conditional logic is how you get the first experience.
The mental model
A rule has three parts: a trigger (an answer), a condition (equals, contains, greater than, is empty) and an action (show, hide, require, skip to). Rules are evaluated live as someone types, so the form reshapes itself while it is being filled.
Simple example:
- If Are you an existing customer? equals Yes → show Account ID
- If Are you an existing customer? equals No → show How did you hear about us?
Two rules, one form, two experiences.
Patterns that work
Branch on role
Ask who the person is in question one, then show only their branch. Applicant, parent, agent and staff can share one form and never see each other's fields.
Progressive disclosure
Show the follow-up only when the answer warrants it. A rating of 1–3 opens a "what went wrong" box; 4–5 opens "what did we get right". Same form, better feedback quality.
Conditional requirements
Instead of hiding, make a field required only in certain cases. "Reason for cancellation" is optional normally and required when status is Cancelled.
Skip logic for disqualification
If someone fails a screening question, jump them straight to the end with an appropriate message rather than making them fill six more fields you will discard.
Designing rules that do not break
Three failure modes account for almost every broken logic setup:
- Orphaned required fields. A hidden field that is still required blocks submission with no visible error. Always pair hide rules with a requirement that follows visibility.
- Contradictory rules. Two rules acting on the same field in opposite directions. Keep one rule per field per trigger where you can.
- Deep chains. Logic four levels deep is impossible to test. Flatten by asking one better qualifying question earlier.
Test like a respondent
Before publishing, walk each branch end to end. Pick the three most common personas who will fill the form and complete it as each of them. Most logic bugs surface in the first two minutes of real use.
What it does to your data
Cleaner columns. Instead of a spreadsheet full of "N/A" from people who were shown a question that never applied, you get sparse, meaningful data. Analytics per question become interpretable because the denominator is only the people who should have answered.
Where to use it first
If you only add logic to one form, add it to your highest-traffic one — usually a lead form or a registration. Measure completion before and after. A well-branched form routinely lifts completion by double digits because the perceived length drops even though total field count rises.
Combining logic with other features
Logic composes with everything else: show a payment field only for paid ticket types, request an e-signature only for the agreement branch, surface an advanced table only for applicants selecting multiple subjects. The rule engine does not care what kind of field it is targeting.
Start with two rules. Publish. Add more when you see where people hesitate.