Overview
A branching intake Checklist asks for details only when they apply. This example starts with a single-choice condition question, shows a description when a defect is reported, and creates an Assignment for the follow-up.
At a glance |
|
Who can do this | Super Users, Checklists › Modify, or permission-folder Administrators/Editors |
Where | Checklists › Edit › question Logic and Triggers |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: A short first question can lead staff to the evidence and follow-up needed for that answer.
Before you start
Agree the defect categories, required evidence and receiving team. Start with a test Checklist. Use answer-based logic for visibility and Assignment Triggers for creating work; they have different jobs.
Walkthrough
1. Add the decision question
Create a Select Question with Single choice and answers such as No defect found and Defect found. Keep the wording unambiguous so staff know which path to use.
2. Show the relevant details
Add a Text Question for the defect description. In its Logic, choose Add Logic › Based on an answer to a question. Select the decision question, equal to and Defect found. Add a Photo Question with the same condition if a photo is required.
3. Route the follow-up
On the decision question, add an Assignment Trigger for Defect found. Set its title, assignees and deadline deliberately. Check the chosen team can be assigned at each intended Location. Avoid duplicating an Assignment already raised by another trigger.
4. Test both paths
Save and run the Checklist at a test Location with each answer. No defect found should hide the follow-up questions. Defect found should show them; complete and sync that test Result, then inspect the generated Assignment and its routing.
Check the outcome
Both branches behave as intended and the completed defect path produces the expected follow-up work. Remove test work through your normal process.
Best practices
Put the decision question before the questions that depend on it.
Keep a branch’s questions on a clearly named page when it becomes long.
Re-test conditions after changing or removing answer options.
Frequently asked questions
Why is my follow-up question hidden?
Its logic may not be met, or its page may also have logic. Check both. Review unexpected visibility.
Will saving progress create the Assignment?
No. Test after completing and syncing the Checklist. Read about trigger execution.
Can one answer show questions and create work?
Yes. Logic controls visibility and an Assignment Trigger creates follow-up work. Configure and test both on the relevant answer.