# Add conditions to your questions
URL: https://docs.awellhealth.com/docs/design-care-flows/add-conditions-to-your-questions

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).





Visibility logic shows a follow-up question only when an earlier answer makes it relevant, so each
respondent sees a shorter form.

## Add a visibility condition [#add-a-visibility-condition]

1. Select the question or description to show conditionally.
2. Click the **Logic** tab in the right pane.
3. Toggle **Add visibility logic** on. The statement changes to "This question is only visible:".
4. Click **+ Add condition** to open the data points menu.
5. Choose the data point, meaning the earlier question, that drives the condition.
6. Choose the operator. The available operators depend on the question type.
7. Choose the operand, meaning the specific answer that makes the question appear.

<img alt="The Logic tab on a question, with visibility logic switched on and a condition comparing an earlier answer" src="__img0" />

A condition reads an earlier answer, picks an operator, and compares it to a value. **Add condition** adds
another.

## Conditions join with AND or OR, never both [#conditions-join-with-and-or-or-never-both]

Several conditions can drive one question, joined with **AND** or **OR**. AND and OR can't be mixed in
the same set, so a rule that needs both is a sign the question should be split.

## Date and text answers can't drive visibility logic [#date-and-text-answers-cant-drive-visibility-logic]

Answers from **date, short text and long text** questions can't drive visibility logic. A question that
controls what comes next has to be a type that can: single select, multiple select, number, slider, or
an ICD question, which records a diagnosis using the International Classification of Diseases.

Check the question type at design time rather than after the form is written.

## Next steps [#next-steps]

Conditions inside a form control which questions appear. To branch the care flow itself, see
[Decision component](/docs/design-care-flows/decision-component).