How to Add Conditional Logic to a Form (No Code)

A form without conditional logic asks every question to every person. The B2C buyer gets the enterprise budget question. The freelancer gets the procurement section. The candidate who marked "no" on driver's license still sees "what year is your car."

The form is technically working. The completion rate is quietly tanking.

Conditional logic is the difference between a form that asks 8 relevant questions and a form that asks 25 questions, 17 of which do not apply. Done well, completion rate jumps 30 to 50%. Done badly, the form gets confusing and people drop off mid-flow.

This post is the practical setup for adding conditional logic in plain English, with three logic types covered, an example multi-path lead form, and the common traps to avoid.

What conditional logic actually solves (and what it doesn't)

Conditional logic shines on three patterns:

• Personalization: ask the budget question only to qualified leads, ask the technical fields only to engineering candidates, ask the dietary restrictions only if the event has food.
• Branching: route B2B leads down one path and B2C leads down a different one with different fields, even though they fill the same form.
• Dynamic copy: change the help text or the next-step message based on what the person already answered.

It does not solve:

• A form that is fundamentally too long. If 25 questions become 22 with logic, the form is still too long. Cut, do not branch.
• A form with vague goals. Logic on top of unclear copy makes the form harder to follow, not easier.
• A form with bad routing on the back end. If hot leads do not get followed up, no amount of conditional logic on the front end fixes it.

The rule of thumb: use logic to remove irrelevant questions, not to add more.

The 3 logic types

Most form builders ship three patterns. The names differ but the patterns are identical.

1. Show / hide

The most common. A field appears or disappears based on a previous answer.

If "are you currently using a CRM" is yes, show "which CRM." Otherwise hide it.

Low risk, high payoff. Use this freely.

2. Jump-to (skip logic)

The form skips ahead based on an answer. Useful for multi-step forms with branching paths.

If "company size" is "solo," jump to step 4 (skip the team-size and procurement steps).

Medium risk. Done well, it cuts long forms in half. Done badly, the form feels confusing because steps disappear without explanation.

3. Branch-specific fields

Different answers surface different follow-up fields.

If "country" is United States, show a US-states dropdown. If France, show a French-regions dropdown. Otherwise show a plain text field.

The most powerful pattern, built from show/hide rules across several fields. Also the most likely to break if you do not test every branch.

How to add logic in Brieform by describing it

Most form builders give you a visual rule editor. Click the field. Add a rule. Pick the trigger field. Pick the operator. Pick the value. Click save. Repeat 12 times for a complex form.

Brieform skips that. Because it's an AI-native form builder with an MCP server, you describe the logic in plain English right inside your AI client (Claude, ChatGPT, Cursor, or any MCP client). Brieform supports 8 condition operators — equals, not_equals, contains, not_contains, greater_than, less_than, is_empty, is_not_empty.

Step 1: build the form first

Describe the base form to your AI and get all the fields in place.

Step 2: ask your AI to add the rules

In the same conversation, your AI calls Brieform's update_form tool to attach the logic — no separate panel or rule editor.

Step 3: describe the logic in plain English

Hide the budget field if the user marked themselves as a student. Show the technical questions only if the role is engineering. Skip step 3 entirely if the company size is solo. If country is France, show region dropdown with French regions; if US, show state dropdown.

Brieform parses each statement, identifies the trigger field and the target field, and creates the rule. You see the rule in plain English afterwards and can review or edit it.

Step 4: test on the live preview

Preview mode lets you fill the form as a respondent. Run through each branch manually to make sure the logic fires the way you described it.

Step 5: ship

No separate publish step for logic. The rule is live as soon as the form is published.

Example: a multi-path lead form (B2B vs B2C)

A SaaS that sells to both businesses and consumers needs different fields for each. Same form, two paths.

The base form

Name, email, country, "are you signing up for personal use or for a business" (the splitter question).

The B2B path

If the answer is "business":

• Show: company name, role, company size, use case (multi-select), urgency.
• Hide: any consumer-only fields.

The B2C path

If the answer is "personal":

• Show: how did you hear about us, primary use case (free text), referral code.
• Hide: company fields, role, size.

The result

A B2B respondent sees 8 fields. A B2C respondent sees 6. Same form. Different experience. The conditional logic handles which fields appear; when it's time to route the leads, your AI client reads the responses via get_responses and posts the B2B and B2C ones wherever you want — Slack, Notion, your CRM — using the connectors it already has.

In Brieform, the entire field setup above is described in your AI chat. No rule editor, no nested if-statements, no copy-paste between fields.

Logic tips that improve completion rate

The difference between logic that helps and logic that hurts comes down to a few patterns.

Hide aggressively, show sparingly

The goal of conditional logic is fewer questions, not more. Default to hiding fields that do not apply. Be cautious about adding fields that only appear conditionally because they often surprise people.

Keep the splitter question early

If the form branches based on a single field, that field should be in the first 1 to 3 questions. Branching late in the form means the respondent fills 10 fields before realizing half of them did not need to apply.

Avoid nested logic chains

Logic that depends on logic that depends on logic is hard to debug. If a form needs more than 2 levels of nested rules, it is probably trying to be 2 different forms.

Always preview the worst-case path

Every branch should be tested as a respondent. The path with the most fields, the path with the fewest fields, the path nobody normally takes. Bugs in conditional logic almost always show up on the edge cases.

Show progress where possible

If the logic significantly changes the form length, a progress bar helps. "Step 2 of 5" is reassuring. "Step 2 of ?" is not.

Avoiding the conditional-logic trap

The trap most teams fall into: using conditional logic to keep a long form long.

The instinct is to add fields because they might be useful for one segment. "Let's also ask about their existing tooling, but only if they are enterprise." Six months later, the form has 40 fields with 20 conditional rules and the completion rate has dropped 30%.

The better default: cut every field that is not used in the first follow-up. If sales does not look at "existing tooling" before the first call, do not collect it on the form. Ask it on the call.

Conditional logic should make a tight form smarter. It should not be the workaround that lets you keep a bloated form alive.

FAQ

Is conditional logic available on the free plan?

Yes. Conditional logic is part of every Brieform tier including free. The free plan has the same logic capabilities as paid plans — the constraints on free are response volume and form count, not features.

Can I chain multiple conditions?

Yes. A field can have multiple rules attached, and rules can use AND/OR operators. "Show this field if country is France AND company size is over 50" works. Brieform recommends staying under 3 conditions per rule to keep the form maintainable.

Can I hide entire sections?

Yes. On multi-step forms, an entire step can be hidden or skipped based on a previous answer. The progress bar adjusts automatically so the respondent sees the correct number of remaining steps.

Does logic work on multi-step forms?

Yes. Logic on multi-step forms includes show/hide on individual fields and jump-to-step for skipping entire pages. Logic can also span steps — a rule on step 3 can depend on an answer from step 1.