Conditional logic, calculations and scoring

A rule reads when this, do that. The when tests an answer, a hidden field or a calculated value. Add several conditions and set Match to all or any of them. The do is one or more actions:

• Jump to a question further on.
• End survey, sending the person to the ending you pick.
• Calculate: add to, subtract from, multiply, divide or set a calculated value.
• Require an answer to other questions.

There are two ways in, both under Add logic on a question's toolbar. Only show this question when… keeps the question hidden until an earlier answer matches. After this question, if… adds a rule that runs once the question is answered; it sits as a card in the canvas, under the question it runs after. The Add menu has the same entries under Logic, plus Ending.

These are the conditions each kind of answer can test, as the picker lists them:

Once a form has a rule, a question that only shows sometimes, or more than one ending, a Flow button appears in the top bar. It opens a map of every path from the first question to each ending, so you can see where each kind of respondent ends up.

A guardian branch. In the course registration form, "Is the person taking part under 18?" is a Yes/No question. The next page's "Your name (parent or guardian)" question is set to Only show this question when… that answer is Yes, and it is required. Answer No and it never shows, so it can never stop anyone from submitting. The same form asks "Tell us what the instructor should know" only when the checkbox answer includes a medical condition, an allergy, an injury or support needs.

A lead that books a call. The lead generation form asks for team size, timing and budget, and asks about budget only when the team is bigger than the smallest size. A rule named "Soon and with budget → book a call" checks that the start is this month or within three months and that the budget is not the lowest band. If both are true, End survey sends the person to an ending with a Book a demo button; everyone else reaches the default ending, which links to a guide. The form also keeps a Lead score as people answer, so each response carries its score in Results and in exports.

More patterns in the templates. The Brazilian wax consent form ends early when someone has taken Accutane in the last six months. The pre-trip inspection form sends a driver who marks the vehicle unsafe to a screen telling them not to drive it. The golf scramble registration form skips the player boxes when someone enters alone, the apartment rental application drops the landlord questions for someone who lives with family, and the bakery order form ends on your booking link, before any cake questions, when someone picks Wedding. The business credit application asks for a personal guarantee only from companies and trusts, and the bookkeeping client intake form adds monthly transactions only when someone picks Bookkeeping.

The VBS registration form opens a block for each extra child, the writing competition entry form shows parent questions only to under-18 age groups, and the eyelash extension consent form asks for a patch test only on a first set. A video release form asks for a parent's signature when the model is under 18, a personal training intake form pauses on a clearance screen after a yes to its health questions, and an equipment service request form ends on a call-us screen when the job is urgent.

Scoring sits on the question you score. Turn on Score this question in its settings, give each answer its points, and the total adds itself up as people answer. Choice, picture choice, yes/no, consent checkbox, rating, NPS, number and slider questions can all carry points.

A score can grade a lead, mark a quiz or check eligibility before someone applies. Outcome by score, under the endings in the canvas, shows a different ending for each score range: pick the value it is Based on, set where each range starts, and pick an ending for each range. It writes one rule per range, which you can then edit like any other rule.

For anything beyond a running total, add a value in Settings, under Calculated values, then have a rule change it with Add, Subtract, Multiply by, Divide by or Set to. A text value can be Set to a word or built up with Add to the end of. Type @ in any text to show a value, such as the running total on a catering request form, a class shirt order form, a fundraising order form or a business travel request form.

Piping repeats an earlier answer in a later question: "Thanks, {name}. Which of our services do you need?" Type @ in a question title, a description, an ending or a redirect URL to insert an answer, a hidden field or a calculated value.

Hidden fields carry data in through the link: ?campaign=spring&customer=1234. Set them up in Settings, under Hidden fields. The values arrive with the response and can be used in logic, so you can tell responses apart without asking people who they are. The course evaluation template takes ?cohort= this way, the membership renewal form takes ?season=, and a client testimonial form takes ?job=, so each quote arrives with its project. On the new starter form, HR fills in the job details through the link, so the new hire only checks them. Links that carry information shows how to build those links.

Take every path in the preview before you save the form. Until it is saved, nothing submitted in the preview is recorded, so you can check each ending as a different kind of respondent. After that the form is live and a test submission is a real response. Open it in Responses and choose Delete this response to remove it, or test a change on a copy: duplicate the form from its menu in your dashboard, test the copy, then delete the copy.

When a rule does not do what you expect, it is usually one of these:

• The person never reached it. A rule runs after its question is answered. If an earlier jump skipped that question, or it sits in a hidden section, the rule never runs.
• It tests a later answer. Conditions compare answers given before the question they belong to. Move the rule, or the question it tests, so the answer comes first.
• Two rules want to move the person. Only the first Jump to or End survey in a rule takes effect.
• A hidden question is required. It is not an error: a question that is hidden is never required and never sent, so it cannot stop anyone from submitting.
• It jumps backwards. A jump to an earlier question can loop. The form shows each question at most 3 times, so it always finishes, but the person may see a question more than once.

When you can see where people give up, tighten the logic. Drop-off insights on Pro shows which question lost them.