What is conditional logic?
Conditional logic is the set of rules governing which parts of a form appear and when. Each rule tests answers already given and then decides whether a later section appears at all. It is policy expressed as navigation, which makes it as consequential as any validation rule.
Also called: Branching logic, Skip logic
Why branching is confused with presentation
Conditional logic is treated as a presentation concern and owned by whoever assembled the form. It is in fact a statement about who the policy applies to, since a question that never appears is a requirement the applicant was never asked to meet. When an auditor finds that a category of applicant skipped a mandatory declaration, the finding lands on the policy owner who had no idea the branch existed. Logic belongs with the rule it enforces, under the same approval.
- A hidden question is a requirement the applicant was never given.
- Branching decides which policy applies, which makes it a policy artefact.
- Each branch multiplies the paths through a form, leaving most of them untested.
- Logic changed without approval alters the obligation quietly and at scale.
How conditional logic works
- Each branch is expressed as a condition over named fields rather than screen positions.
- The policy owner approves the condition alongside the rule it implements.
- Revising an earlier answer re-evaluates every branch that depended on it.
- Answers collected on a path later abandoned are cleared or clearly marked.
- Every distinct path is exercised against a test case before release.
- The path an applicant actually took is recorded with the submission.
How conditional logic is evaluated
Conditional logic is evaluated on path coverage and on whether the right applicants reach the right questions. Examine the following before each release:
- proportion of distinct paths covered by a test case
- count of branches with no approving policy owner
- frequency with which each path is taken in live submissions
- orphaned answers remaining after an applicant changes an earlier response
- rate of assessor findings attributable to a question never shown
Limitations, risks and common failure modes
- A branch added for one scheme silently applies to every scheme sharing the form.
- Changing an early answer leaves answers from the abandoned path in the record.
- Deeply nested conditions become impossible for a policy owner to review.
- Hidden fields remain mandatory in the underlying schema, blocking submission inexplicably.