Skip to main content

How do I build a complex branching workflow with Mobilize AI?

This guide explains how to create workflows with multiple levels of branching logic where users make sequential selections that determine which questions they see.

Written by Lauren Baird
Updated this week

Answer

Use Mobilize AI when you need to build a workflow where users make a series of selections and only see the questions that apply to their path. This is useful for workflows that branch by things like location, department, shift, work type, or other layered choices.

The quality of the output depends heavily on how you structure your source file and how clearly you instruct Mobilize. For complex branching workflows, the most important success factors are:

  • a clean source file

  • consistent category values

  • a clear prompt

  • careful review of the generated draft

  • full testing before publish

If your dataset is too large, split it into multiple workflows instead of trying to force everything into one draft.


Steps

Step 1: Prepare your source file

Build your workflow content in Excel, Word, or a plain text editor before using Mobilize.

Structure the content so each branching level is clearly defined, followed by the final questions.

Recommended example structure

LOCATION: Building 1
DEPARTMENT: Safety
SHIFT: Morning
- Are fire exits clear and unobstructed?
- Is emergency equipment easily accessible?
- Are safety signs visible and legible?
SHIFT: Evening
- Are fire exits clear and unobstructed?
- Is emergency lighting functional?
DEPARTMENT: Maintenance
SHIFT: Morning
- Are tools properly stored and secured?
- Is equipment clean and operational?

LOCATION: Building 2
DEPARTMENT: Safety
SHIFT: Morning
- Are fire exits clear and unobstructed?
- Is emergency equipment easily accessible?

You can also use a row-based or bracket-based format as long as the branching levels are clear and consistent.

Formatting rules

  • Use the exact same spelling for repeated values

  • Keep one final question per line or row

  • Make sure every category combination has its related questions

  • Use clear header names for each branching level

  • Save the file with a clear name and date

Before moving on, check this

  • spelling is consistent

  • headers are clear

  • all questions are complete

  • all intended branching paths are represented

Step 2: Open Mobilize AI

  1. Open ANVL Insights.

  2. Open Mobilize AI.

If you do not see Mobilize AI, contact your Business Administrator (BA) for access.

Step 3: Give Mobilize a detailed prompt

Upload or paste your source content and give Mobilize very clear instructions.

Use a prompt like this and edit it to match your workflow:

Create a branching logic workflow using the questions below. Follow these requirements exactly:

Use Exact Language: Use the questions exactly as written below - do not modify, paraphrase, or reword any questions.

Branching Structure:
- Create branching levels in the order of my columns or headers from left to right
- Each header except the final question column becomes a branching level
- Show questions only after ALL selections are made

Required Tags:
- Add a "reportName" tag to every single question for reporting purposes

Navigation Logic:
- Users must select in the order of my headers
- First question: select from Header A options
- Second question(s): select from Header B options based on the first selection
- Continue through all remaining levels in sequence
- Finally, display only the questions that match the full selection path

Intervention Logic:
- For questions where "No" or another undesirable answer indicates an issue, add a follow-up question such as "What action will you take to address this?"
- Only show the follow-up when the triggering response is selected

Additional Requirements:
- Preserve exact question wording
- Ensure proper filtering based on all branching selections
- Include reportName tags for all questions
- Handle the correct number of branching levels based on my structure

Please provide all of the questions you will create before generating the draft.

Then:

  1. paste in your structured questions or upload your file

  2. review the prompt

  3. send it to Mobilize

  4. ask Mobilize to list all questions it plans to create

  5. review that list carefully

  6. then create the draft

This checkpoint is important. It helps catch missing questions, rewording, or wrong branching before the draft is built.

Step 4: Create the draft

  1. Select Mobilize to create the draft.

  2. Enter the draft name.

  3. Select Create.

  4. Wait for the draft to finish processing.

  5. Open the draft in Editor.

If draft creation fails, the workflow is often too large for one pass.

If that happens

  • split the workflow by the top-level branching category

  • create multiple workflows instead of one very large workflow

Example
If your top level is:

  • Building 1

  • Building 2

  • Building 3

Create:

  • one workflow for Building 1

  • one workflow for Building 2

  • one workflow for Building 3

Step 5: Review the generated draft

Open the draft and check the structure before testing.

Review these items carefully:

  • branching levels match your source structure

  • all unique values appear as options

  • questions appear only after all required selections are made

  • question wording matches your source exactly

  • every question has a reportName tag

  • filtering works correctly for each path

  • all intended questions are included

Make edits as needed and save the draft.

Step 6: Test the workflow

Publish the draft to your testing site and test it thoroughly.

  1. Start the workflow in ANVL Workflows

  2. go through different selection paths

  3. verify only the correct questions appear

  4. compare the workflow to your original source file

  5. confirm tags are present

  6. test issue-triggered follow-up questions

  7. test every major branch before rollout

For mobile or browser testing, refresh the user experience by signing out and signing back in before testing the newest version.

Step 7: Finalize and document

Once the workflow works as expected:

  1. save your source file with a clear name and date

  2. document the workflow purpose

  3. keep the prompt you used for future updates

  4. note what worked well and what to avoid next time

Common issues and how to fix them

Questions are missing

  • check for inconsistent spelling in your branch values

  • confirm every row or line has a complete path

  • confirm you pasted the full source data into Mobilize

Branching is wrong

  • check the order of your headers

  • make sure the prompt clearly says selections must happen in sequence

  • check for duplicate or inconsistent values

Questions were reworded

  • reinforce that Mobilize must use exact language

  • provide the original wording again

  • ask it to regenerate without paraphrasing

Draft creation fails

  • split the workflow into smaller workflows

  • separate by top-level category

Success criteria

Your workflow is ready when:

  • users move through all branching levels in the correct order

  • only relevant questions appear for the selected path

  • question wording matches the source exactly

  • all required reportName tags are present

  • all intended data is represented

  • every major path has been tested successfully

Additional Details

  • Complex branching workflows work best when you think of them as a decision tree, not just a list of questions.

  • Keep the number of branching levels practical. Too many layers can make the workflow harder to maintain and harder for users to complete.

  • If the same question appears across multiple branches and should report together, use the same reportName tag consistently.

  • Treat Mobilize as a strong first draft tool, not a final publishing step. Review and testing are still required.

  • For large or business-critical workflows, pilot the workflow with a small group before broader rollout.


Did this answer your question?