Overview
Based on an answer to a question is the most common logic condition. It shows or hides a Checklist page or element depending on how a question in the same Checklist was answered, so follow-up questions appear only when they're needed.
This article is the reference for the answer condition. For logic in general and the other five condition types, see Adding logic to a Checklist. To make an answer raise an Assignment or require a photo, use a trigger instead: see Adding triggers to a checklist.
At a glance |
|
Who can do this | Super Users, a Role with Checklists › Modify (or Create, for Checklists you created), or an Administrator or Editor of the Checklist's permission folder |
Where | Checklists › a Checklist › Edit › a page header or element › Logic |
Works on | Backend (web) to set up. The logic runs in the Mobile app and RideOps. |
Availability | All organizations |
💡 Why this matters: A Checklist that asks everyone everything is slow and easy to get wrong. Answer-based logic keeps it short: the "describe the damage" page only appears when someone answers "Damaged", so Users see a short form and you still capture full detail exactly when it's needed.
Add an answer condition
1. Open the logic panel
Go to Checklists, select the Checklist and click Edit. Click the header of the page, or the element, that you want to show or hide, and open its Logic section.
2. Choose the question
Click Add Logic and choose Based on an answer to a question. In Question, pick the question whose answer decides; each entry shows the page it's on, and you can type in Search here... to find it. For a Select Question Group, pick one of its lines; for a Water Quality Question, pick one of its parameters.
3. Set the operator and value
Choose the operator, then the value to compare with, such as an option, a number or a smiley. The operators depend on the question type (see below). Every field is required: a condition that isn't fully set up stops you from saving the Checklist.
4. Save
Click Accept Changes, then Save the Checklist. To combine this condition with others, choose All or One at the top of the logic panel, as described in Adding logic to a Checklist.
How answers are compared
The question type decides how the condition compares the answer. For the exact operator names per type, see the operator table in Adding logic to a Checklist.
Question type | The condition compares |
Select Question or a Select Question Group line | The option you pick. equal to is met when that option is chosen (ticked, for Multiple choice); not equal to when a different option is chosen, or on Multiple choice when that option isn't ticked. |
Number Question, Slider Question, a Water Quality parameter | The number you enter. |
Temperature Question | The temperature you enter, in Celsius or Fahrenheit. Readings in either unit are compared correctly. |
Duration Question | A number of seconds. |
Date Question | How many hours the entered date is before or after the moment the question was answered (1 hour or more). |
Smiley Question | The smiley you pick, or an N/A answer. |
Photo, File, Signature and Scanner Question | Only whether the question has been answered. |
Water Quality Question with a ruleset | Whether the reading is below, within or above the rule's range. |
Text Question, Email Question | The text you type, up to 75 characters. See the heads-up below. |
⚠️ Heads-up: Known issue in the mobile app: conditions on a Text Question or Email Question don't compare typed words correctly. equal to a word is never met, and not equal to is always met, whatever was typed. RideOps compares the text exactly. Until this is fixed, ask the question as a Select Question with fixed options and base the logic on those.
When the condition is checked
As the User answers — the page or element appears or disappears as soon as the answer changes, in the Mobile app and in RideOps.
Before the question is answered — most conditions aren't met, so content that depends on them stays hidden. Not answered is met and, in the mobile app, so is not equal to an option on a Multiple choice Select Question, because the option isn't ticked yet.
When the question is hidden — if the question the condition reads is hidden by its own logic, everything that depends on it is hidden too.
Hidden questions don't need an answer, so the Checklist can still be completed.
The Question list offers every question in the Checklist, including questions on later pages. A condition can read a later question, but the content it controls then stays hidden until the User reaches and answers that question, so put the controlling question first. Page logic can't read questions on the same page, and an element can't read its own answer. Questions whose logic already depends on the element you're editing are greyed out; if a circular dependency slips through, the editor shows a Warning, because the User can't complete the Checklist.
Examples
Follow up on a fault. A ride inspection asks Restraint condition? with Good and Damaged. The page Damage report has the condition Restraint condition equal to Damaged, so only Users who report damage see it.
Skip what doesn't apply. The first question asks Is the splash pad open today? The later pages have the condition equal to Yes. When the answer is No, those pages are hidden and the Checklist can be completed straight away.
Choose a path. A step check asks Step type? with Type A and Type B. Each type's questions sit on their own page, with page logic equal to that type.
Best practices
Branch on Select Questions: fixed options make conditions predictable and easy to read later.
Put the controlling question before the pages and elements it controls.
Group follow-up questions on their own page and use page logic, rather than repeating the same condition on each element.
After copying a page, check its conditions: see the FAQ below.
Test every answer path in the mobile app before you schedule the Checklist.
Frequently asked questions
Can I skip the rest of a checklist, or stop someone continuing, if they answer "No"?
You can hide the rest, but not block progress. Give the later pages the condition equal to "Yes"; hidden questions don't need answers, so the Checklist can be completed. Logic can't end a Checklist or stop someone from choosing an answer.
Can I show a field based on what someone typed in a Text question?
Not reliably at the moment. The editor offers equal to and not equal to for Text Questions, but a known issue in the mobile app stops them comparing words correctly. Ask the question as a Select Question and base the logic on its options instead.
If I copy a page, does the logic come with it?
Yes. Conditions that read a question on the copied page are switched to the copy of that question. The page's own logic, and conditions that read questions elsewhere, still point at the original questions, so check them after copying.
Can I show a number of questions based on a number someone enters?
Yes. Give each follow-up question its own condition on the Number Question, for example the second one greater than or equals 2 and the third greater than or equals 3. Logic can't create questions; it only shows or hides ones you've added.
Can the condition read a question that comes later in the checklist?
Yes, the editor lets you pick any question. The content stays hidden until that question is answered, though, so the User may not see it when they expect to. Put the controlling question first whenever you can.