Conditional logic sounds technical, but the idea is simple: the form reacts to what the person tells it. Answer yes and a follow-up appears; pick one option and an irrelevant section disappears. The form adapts instead of showing everyone everything.
The payoff is a form that feels short to each person while still handling many different situations behind one link.
Show only what is relevant
The core move is hiding fields that do not apply. If someone says they do not need shipping, do not show them a shipping address. If they pick a service that has no add-ons, skip the add-on question. Every hidden field is friction removed for that person.
- Reveal follow-up questions only when the answer calls for them.
- Hide whole sections that a choice makes irrelevant.
- Keep the visible form as short as each case allows.
One form for many paths
Without logic, serving three different customer types means three forms and three links to maintain. With it, one form branches to the right questions for each. A single link handles the new client, the returning client and the just-browsing enquiry.
That is fewer things to build, fewer links to share, and one place to read every response.
Route people to the right outcome
Logic is not only about which questions show — it can change where a submission goes and what the person sees at the end. A high-budget enquiry can land differently from a small one; a specific choice can lead to its own confirmation.
- Send different responses to different people or inboxes.
- Show a confirmation matched to what they picked.
- Skip payment for cases that do not need it.
Do not over-engineer it
Logic is powerful, which makes it easy to overuse. A maze of branching rules is hard to maintain and easy to break. Start with the one or two conditions that genuinely simplify the form, and add more only when a real case demands it.
You can add conditional logic to a form without touching code, free, at onesol.io/forms.
Start From the Questions You Regret Asking Everyone
The easiest way into conditional logic is to look at your current form and find the fields that only apply to some people. A "T-shirt size" box only matters to those who chose a tier that includes a shirt; a "dietary requirements" field only matters to attendees of the event with a meal. Right now every visitor sees those fields whether they're relevant or not, and irrelevant questions are exactly what make a form feel long.
Conditional logic — sometimes called show-when rules — simply means a field appears only when an earlier answer calls for it. You are not adding complexity; you are hiding the parts of the form that don't apply to the person in front of you, so each visitor sees their own shorter version. The form can hold every question it needs while feeling half the length to any individual.
So the first move isn't to build branches, it's to audit. Circle every field that makes some people think "this isn't about me", and those are your candidates. A form that shows everyone only what applies to them almost always converts better than the same questions shown to all.
A Worked Branch, Step by Step
Take a course signup with a mix of new and returning students. Add one question near the top — "Have you taken a class with us before?" — with Yes and No. That single answer becomes the switch that shows two different short paths instead of one long form that tries to serve both.
Set the rules plainly. When they answer No, show the fields a beginner needs: experience level, any injuries, how they'd like to be contacted. When they answer Yes, hide all of that and instead show "Which student ID or email did you use last time?" so you can match them to their record. A returning student never wades through the onboarding questions, and a newcomer never sees a field asking for history they don't have.
The result reads as two tidy forms sharing one link. Each person answers perhaps five relevant fields rather than staring at ten, half of which don't apply — and you still capture everything both groups require, without maintaining two separate forms that drift out of sync.
The Mistakes That Quietly Break a Logic Form
The most common failure is a required field hidden behind a condition that never becomes true — so the form insists on an answer to a question the visitor can't even see, and the submit button refuses to work with no visible reason why. When a field is conditional, its required status must be conditional too, or you build a trap that only surfaces as "the form won't submit and I don't know why".
The second is over-branching. Logic is a scalpel, not a hobby — three or four well-placed rules keep a form short, but twenty overlapping conditions become impossible to reason about, and rules that contradict each other produce fields that flicker or never appear. If you cannot describe your branches in a sentence or two, you have too many.
Whatever you build, walk every path before you publish. Answer Yes and complete the form; answer No and complete it again; try the combinations a real person might. Logic errors are invisible to the person who wrote them and glaring to the person hitting a dead end, so the only reliable test is to become each type of visitor in turn.