If you have ever filled in a form that asked you ten questions that had nothing to do with you, you have felt the need for JotForm conditional logic done well. A good form shows each person only the questions that apply to them, skips the rest, and sends the answers to the right person.
Conditional logic is the set of rules that makes a form react to answers. When a visitor picks one option, the form shows a follow up question. When they pick another, it hides that question and moves on. The form stays short for each person, even when the full form covers many cases.
How JotForm conditional logic works
Every rule has three parts: a trigger, a condition, and an action. The trigger is the answer the visitor gives, such as picking Yes on a dropdown. The condition is the test you set, such as if the answer is Yes. The action is what the form does, such as show the follow up question or jump to page three.
Rules run in order, from top to bottom. When two rules could both apply, the first matching rule usually wins, so the order of your rules matters. There are four rule types you will use most often: show and hide, calculation, skip logic, and routing. Start with a map before you build: write down the questions, the answers that change the path, and where each path ends.
Show and hide questions
Show and hide is the most common use of conditional rules. It keeps the form short by revealing extra questions only when they apply. A contact form asks, “Do you have a company?” If the visitor picks Yes, the form shows a company name field. If they pick No, that field stays hidden.
That is JotForm conditional logic in its simplest form. One answer controls one follow up. Most forms are built from many small rules like this one, stacked together. Keep each rule to one job, so you can test and fix each rule on its own.
One mistake to avoid is hiding a required field and then wondering why the form will not submit. If a field is required but hidden, some forms still block submission. The safe pattern is to make follow up fields required only when they are shown.
Calculations that change with answers
Calculations let the form do the maths for you. A quote form can add up options and show a total before the visitor submits. An order form can multiply quantity by price. A quiz can add up a score.
The pattern is the same each time. Give each option a number value, for example basic 100, standard 250, premium 500. Then set a calculation rule that adds the chosen values into a total field. Show the total on the form so the visitor can see the price change as they pick options. Show a breakdown when the total has more than two parts. If the price depends on details you cannot confirm from the form alone, show an estimate and say the final price comes after a short call.
Skip logic that shortens long forms
Skip logic moves the visitor to the right page based on an answer. It is the best tool for long forms with several very different paths, such as a survey for customers, partners, and job applicants in one form.
Ask one sorting question early, then send each group to its own page. Page one asks, “What brings you here?” Customers go to page two, partners go to page three, and applicants go to page four. Each page holds only the questions for that group. Skip logic works best when the groups do not overlap. Do not use skip logic to hide a long form. If every path is still long, cut questions first.
Approval routing that sends each submission to the right person
Routing rules decide what happens after the visitor clicks submit. The most useful version is approval routing: the form sends each submission to the right approver based on the answers.
This is where JotForm conditional logic saves the most time. Instead of one inbox where someone reads every submission and forwards it by hand, the form routes it at once. A leave request under three days goes to the team lead. A longer request goes to the manager. An expense claim above a limit goes to finance. Nobody has to sort the inbox.
Routing can also change what the visitor sees. A qualified lead can see a booking link on the thank you page. A visitor who does not fit can see a message that explains the next step. Keep routing rules simple enough to explain in one sentence each.
Example 1: client onboarding that asks only what applies
The following example is illustrative, not a real client case.
A web design studio used one long onboarding form for every new client. It asked about logo files, hosting logins, content, and payment details, whether or not the client needed them. Clients left questions blank, and the studio chased answers by email for a week. The rebuilt form starts with one question: “What do you need?” New website, redesign, and care plan paths each ask only their own questions. Each client sees about eight questions instead of twenty.
Example 2: quote request with a live price estimate
The following example is illustrative, not a real client case.
A cleaning company wanted quote requests that did not need a phone call for every enquiry. The old form asked for a message and a phone number, and staff called back to ask the same questions each time. The rebuilt form asks four questions: property type, number of rooms, cleaning type, and preferred day. A calculation rule adds up the price from the answers. The visitor sees the estimate before submitting, with a note that the final price is confirmed after a short call.
Example 3: leave request with approval routing
The following example is illustrative, not a real client case.
A small company handled leave requests by email. Staff wrote to their manager, the manager replied, and HR kept a spreadsheet. Requests got lost. The rebuilt form asks for the staff name, leave type, start and end dates, and a short reason. A calculation rule counts the working days. Routing rules send short requests to the team lead, longer requests to the manager, and sick leave copies to HR.
Mistakes that break a form
Most broken forms fail for a few repeatable reasons. First, rules that fight each other: one rule shows a field, and a second rule hides it. Second, a missing path: the form handles Yes and No, but the visitor picks Maybe, and the form shows nothing. Third, hidden required fields, as covered above. Fourth, rules tied to labels that later change. Fifth, testing only the happy path.
A simple test plan before you publish
Walk through each path as a visitor, from the first question to the thank you page. Submit a test entry for each path and check that the right person receives it. Test the edges: leave optional fields blank, pick the longest path, pick the shortest path, and try the form on a phone. Check the data, not just the screen.
Getting help with your forms
Setting up rules that show the right questions, calculate prices, and route approvals takes a clear map and careful testing. See the Services page, then book a free discovery call to talk through your form and a fixed quote before any work starts.
Start building smarter forms with JotForm here
Disclosure: This article contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you.
FAQ
What is conditional logic in a form?
It is a set of rules that change what the form shows or does based on the answers given.
Can conditional rules change the price on a form?
Yes. A calculation rule can add up option values and show a total or an estimate before the visitor submits. Keep the breakdown visible so the visitor can see how the total was reached.
Why does my form show the wrong questions?
The usual causes are rules that conflict, a rule tied to an option label that changed, or a missing rule for one of the options.
Should every form use conditional rules?
No. A short form with one path does not need them. Add rules when different visitors genuinely need different questions, different prices, or different approvers.
Sources
- JotForm, Conditional Logic for Online Forms: https://www.jotform.com/features/conditional-logic/
- JotForm, How to Set Up Conditional Logic: https://www.jotform.com/help/57-smart-forms-using-conditional-logic/
- JotForm, Form Calculation Guide: https://www.jotform.com/help/259-how-to-perform-form-calculation-using-a-widget/