Glossary · Form mechanics
Conditional logic
Showing, hiding, skipping or routing based on answers — the category’s number one functional complaint, and the missing piece is a debugger.
Also: Branching, skip logic, display rules
One of 25 entries in the Endpoint Forms glossary.
Definition
Rules that change the form as it is being filled: show this field if that answer, skip to step four, route to a different owner, require something conditionally.
Why it matters
It is the most-complained-about functional capability in the whole category — twelve independent sources in our research, second only to pricing, and unlike pricing it is unclaimed. Everyone has it; nobody has made it hold.
“The conditional logic is always the biggest headache it never works right for anything beyond super simple forms.”
“Conditional settings would erase whenever possible answers in the drop-down list”
“I’d pay for a form builder that handles conditional logic well and stays simple to manage without making every small change feel complicated.”
In practice
The complaints cluster at four or five conditions, and the reason is structural rather than a bug in any one product. Rules are authored as a flat list and executed as a graph. Past a handful of rules the graph has paths the author never pictured, and every builder shows you the list.
- Attach rules to the field they govern, not to a central rules screen, so the rule is visible where its effect is.
- Test paths, not rules. Enumerate the realistic answer combinations and walk them. The bug is almost never in one rule; it is in two rules interacting.
- Watch rules-per-form as a health metric. Past about eight, the form is a decision tree wearing a form’s clothes, and it needs a different tool or a split.
- Never depend on rule order. If reordering the list changes the outcome, you have written a program, and you are maintaining it in a UI with no version control.
The common mistake
Forgetting that logic changes your denominators.
A question shown to 30% of respondents cannot be compared with one shown to everyone, and yet both appear in the same drop-off report with the same-looking percentages. Branching quietly makes every field-level metric conditional on a path.
Report per-field rates against the population that actually reached the field. If your tool does not do that — most do not — the cliff in your drop-off curve may be a branch rather than a problem.
Related terms
- Form drop-off analysis
- Seeing exactly which question people stop at — the feature even competing vendors name as the one worth paying for.
- Multi-step form
- Splitting one form across several screens — the category’s most confident best practice, and one of its least evidenced.
- Progressive profiling
- Ask three fields now and three more next time — a trade of completion for enrichment that almost nobody measures.
- Completion rate
- Submissions divided by the people who could have submitted — and the denominator is the half nobody agrees on.
- Outcome webhook
- A callback that tells the form what happened to a submission — the direction webhooks in this category almost never run.