Conditional logic forms: 8 examples and how to test them

Each example is an illustration written as the rule you would set up, using the four actions available in Zunoform: jump, skip, end and redirect. The same ideas work in most builders; only the menu names change.

Question: "What is this about?" with Billing, Bug, Account access. Rules: if Billing, jump to "Invoice number"; if Bug, jump to "Which browser?" then a screenshot upload; if Account access, jump to "Email on the account". Each branch ends by jumping to the shared "How urgent is this?" question, so the paths rejoin. Our IT support ticket template uses a smaller version: it skips a hardware-only question unless the category is hardware.

Question: "Have you used a project management tool in the last 6 months?" Rule: if No, end the form, and give that ending a polite thank-you. Put disqualifiers first so people who don't fit spend 20 seconds rather than five minutes. The focus group screener template jumps anyone who fails a screening question to a "not a match" ending.

Question: "Do you have health insurance?" Rule: if "No, self-pay", skip the next question (insurer and policy number). This is the smallest useful rule, and our patient intake template ships with it. In single-page and document layouts, a forward skip hides the skipped question as soon as the answer is chosen.

Conditions: budget is greater than 5000 AND timeline is "This quarter" (match all). Action: redirect to your booking page, with the respondent's name and email carried in the URL so the booking form opens pre-filled. Everyone else continues to a standard thank-you ending.

Question: "Are you a new or existing customer?" Rule: if Existing, jump past the five onboarding questions to "What can we help with?". One form with a branch is easier to maintain than two near-identical forms, because a wording fix happens once.

Question: "Will you attend?" Rule 1: if No, end the form. Question: "Bringing a guest?" Rule 2: if No, skip the next question (guest name). A declining guest answers one question; an attending guest with a partner answers everything. The gala dinner RSVP template jumps decliners straight to an ending.

Options carry points and the form keeps a running score. On the last question, the rule tests the score variable: if score is greater than 7, jump to the "Advanced" ending; otherwise continue to the "Getting started" ending. For more than two result bands, Zunoform's outcome quiz setting routes to endings by score range without writing a rule per band. One trade-off: when a form reads the score mid-form, the scoring key has to be sent to the browser, whereas a quiz that only reveals results at the end keeps it on the server. Our guide to quizzes with different results based on score covers band design.

Question: "Why are you cancelling?" Rule: if "Too expensive", jump to "Would a 3-month discount change your mind?"; if "Missing a feature", jump to "Which feature?". Other reasons skip the offer. Keep the offer honest and one question long; a form that argues with people reads as a trap.

Logic helps completion when it removes questions, because each person sees fewer of them. It hurts when it is used to add questions, or when a revealed question appears far below the fold on a phone and nobody notices it. We have not seen a published, primary-source study that isolates the effect of logic alone, so treat any single percentage you read about it with caution.

The practical rule: branch to shorten. If a rule makes some people answer more, check whether that data changes a decision. If it does not, delete the branch.

Google Forms supports one kind of logic: "go to section based on answer", available on multiple-choice and dropdown questions. To make one question conditional you move it into a section of its own. That works for two or three branches and becomes hard to maintain beyond that. Our Google Forms conditional logic guide covers the setup step by step and the workarounds.

Zunoform's logic is on every plan, including Free with 500 responses a month. Rules are attached to questions, test any earlier answer or variable with operators such as is, contains, starts with, greater than, less than and is empty, combine them with match all or any, and then jump, skip, end or redirect. The same rules run in the conversational, single-page and document layouts. Separately, tag groups label responses by their answers, and outcome quizzes route to endings by score range. On Pro, a rule can also add an amount to a payment question, and that price is recalculated on the server.

Where it doesn't fit: Zunoform has no dedicated show/hide action, so a question that should appear in the middle of a page for some people and not others has to be modelled as a jump or skip. Jotform and Tally have native show/hide. If your branching is two single-choice decisions and you need unlimited free responses, Google Forms or Tally already does it.