Conditional Logic
Conditional logic makes your forms smarter by showing or hiding fields based on client responses. This creates a personalized experience and ensures clients only see relevant questions.
How Conditional Logic Works
Conditional logic uses "if-then" rules to control field visibility:
- Trigger Field: The field that clients interact with first (e.g., a dropdown asking "Are you a business or individual?")
- Condition: The rule that determines when to show/hide fields (e.g., "If answer equals 'Business'")
- Target Fields: The fields that appear or disappear based on the condition (e.g., "Show EIN field and Business License upload")
Setting Up Logic Rules
Add conditional logic to any field in the template editor:
- 1. Select the Target Field: Click on the field you want to show/hide conditionally. This opens the field settings panel.
- 2. Add Logic Rule: In the settings panel, click "Add Conditional Logic". Choose "Show this field if..." or "Hide this field if..."
- 3. Choose Trigger Field: Select which field's answer will trigger this rule. Only fields that appear earlier in the form can be used as triggers.
- 4. Set Condition: Choose the condition type (equals, not equals, contains, is empty, is not empty) and specify the value to match.
- 5. Test Your Logic: Use preview mode to test the logic by filling out the form and verifying fields appear/disappear as expected.
Advanced Logic Patterns
- Multiple Conditions: Combine multiple conditions with AND/OR logic. For example, "Show field if entity type is 'Corporation' AND revenue is greater than $1M"
- Chained Logic: Create sequences where field B depends on field A, and field C depends on field B. This creates branching paths through your form.
- Section Visibility: Apply logic to entire sections to show/hide multiple related fields at once.
Common Use Cases
- Entity Type Branching: Show different document requirements for individuals, partnerships, corporations, and LLCs.
- Yes/No Follow-ups: Ask "Do you have dependents?" and only show dependent information fields if they answer "Yes".
- Income Thresholds: Request additional documentation only from clients above certain income or revenue levels.
- State-Specific Requirements: Show different fields based on the client's state or jurisdiction.
- Service Selection: Let clients choose which services they need, then show only relevant document requests.
Best Practice: Keep logic rules simple and test thoroughly. Complex nested logic can confuse clients if not implemented carefully.