What is conditional logic: a plain definition with a worked example
Conditional logic is the branching inside a form or workflow that changes what happens next based on what has already been answered, so each person is shown only the steps that apply to their situation. The same underlying process produces a different path for every participant.
You will also see it called branching logic, skip logic, conditional branching or, in the interface design literature, progressive disclosure. The terms differ by industry more than by meaning.
What does conditional logic mean in practice?
A workflow without branching is a straight line. Everyone answers everything, including the two thirds of it that has nothing to do with them, and the designer is forced into a choice between a long path that covers every case and a short one that covers none properly.
Branching removes that choice. The path is assembled as the participant moves through it, from what they have already told you.
How does conditional logic work?
Every rule has the same shape: a trigger, a condition, and an action. If the answer to step four is yes, show steps five and six. If it is no, skip to step seven.
- Triggers. An answer to a question, a selection from a list, a numeric threshold, or sometimes an attribute known before the workflow starts, such as the asset type or the contract.
- Actions. Reveal a step, hide one, make one mandatory, change the instruction text, jump to a different section, or end the workflow early.
- Order of evaluation. Rules fire as answers arrive, which is why a rule that depends on a later answer will never run and is the single most common bug in a branched flow.
- Defaults. What happens when a condition matches nothing. Leaving that undefined is how participants end up stuck on a step nobody can complete.
Conditional logic explained: a water damage report
A property team asks the tenant one question early: is the leak still running? If the answer is yes, two extra steps appear, one asking them to show the stopcock and one asking whether the water has been turned off. If the answer is no, neither step is ever shown.
An urgent case is escalated within minutes because the branch flagged it. A historic stain goes into the normal queue, and the tenant reporting it was never asked about a stopcock they had no reason to think about.
Why branching beats a longer form
Length has a measurable cost. Baymard Institute's 2024 benchmark of e commerce checkouts found an average of 11.3 form fields, down from 12.7 in 2019, and concluded that most sites need only eight in total. Seventeen percent of users in its research had abandoned a checkout specifically because the process was too long or too complicated.
Checkout is not inspection, but abandonment behaves the same way wherever people are asked to complete something on a phone. Every irrelevant step is a reason to stop, and a workflow abandoned at step nine returns nothing at all.
The design principle behind it is older than the software. Jakob Nielsen introduced progressive disclosure in 1995 as a way to reduce errors by deferring secondary options until they are needed, and Nielsen Norman Group still cautions that more than two levels of disclosure tends to hurt usability, because people lose track of where they are. Branching is a tool for reducing what a participant faces, not a licence to build a decision tree.
How conditional logic differs from validation and required fields
- Validation judges an answer already given: is this a plausible mileage, is this photo too dark. Conditional logic decides which question gets asked at all.
- Required fields control whether a participant may proceed past a step. Branching controls whether that step exists for them.
- Routing rules act after submission, deciding which team or queue receives the case. Conditional logic acts during capture. The two often share triggers and are worth designing together.
Common mistakes with conditional logic
- Branching on something the participant cannot reliably judge. Asking an untrained person whether the damage is structural produces a path chosen by a guess.
- Too many branches. A tree with fourteen paths cannot be tested properly, and untested paths are where participants get stranded.
- Hidden mandatory steps. A step that is required but only appears on one branch is invisible to whoever is maintaining the flow, until submissions start arriving without it.
- Never walking the paths. Every branch needs to be completed end to end by a real person on a real phone before it goes live. Reading the rule table is not the same test.
- Treating a branch as a finding. A path taken records what someone reported, not what is true. It is context for the reviewer, never a conclusion.
Conditional logic is one component of the wider sequence described in guided workflow, and in visual evidence collection it is what makes a single capture flow workable across cases that differ in the detail. The principle it serves is set out in guided capture: the organisation decides what needs to be seen, and the participant is asked only for their part of it.
Drag and drop builders with conditional questions are now standard in this category, including in Venta Capture, a product of VentaVid, where checkboxes, dropdowns and text answers can each open or close later steps in a flow.