Flows are the sets of questions asked during an activity. There are two types: scripts and assessments. Flows are where you build the actual questions that appear in your activities. These questions are what members will answer during screenings, check-ins, or assessments.

Each question you create is linked to a Data ID—a unique identifier that makes the information reusable across multiple features in the Pear Suite platform. Data IDs are critical for:

• Firing Recommendations
• Displaying information in the Member Overview
• Generating Care Plans
• Creating Calculations and Reports
• Importing or Exporting Member Data
• Pulling Analytics

So, creating thoughtful and clearly labeled questions is one of the most important parts of designing your workflows.

Step-by-Step: Creating a Flow

1. Go to the Templates section and click the Flows tab.
2. Click + Add Flow to create a new template.
3. Choose whether you want to build a Script or an Assessment:
   • A Script is interactive and allows branching logic, answer actions, and recommendations.
   • An Assessment shows all questions on one scrollable page and is best used for standardized tools like PHQ-9 or PRAPARE.

Once you select the type, you’ll be taken to a screen where you’ll build your flow.

Adding Questions to a Flow

On the right-hand side, you'll see a list of questions already in the flow (which will be empty at first).

To add a new question:

• Click the green + Add Question button.
• You can also use the search bar to look for existing questions by question title or Data ID.

Each question requires:

• A Data ID – This must be unique across your entire organization. This is how the system tracks and links responses.
• A Question Title – What appears in the question bank and should describe the question clearly.
• A Question Text – What will be shown to the user. You can use placeholders (like {{firstName}} or {{phone}}) to auto-fill known member information.
• An Answer Type – Choose from options like yes/no, choose one, choose many, text, number, date, read-only, etc.
• Answer Options – Depending on the type, write out the options available (e.g., Yes, No, Sometimes).

Using Branching Logic

If you’re using a Script, you can add branching logic to tailor the flow based on a member’s response.

• Branching logic only works with "Choose One" type questions.
• You can guide the user to different follow-up questions based on what the member selects.

For example: If the answer is "Yes" → go to Question 5. If "No" → go to Question 6.

Branching helps reduce unnecessary questions and creates a smoother user experience.

Naming Conventions for Data IDs

To keep your flows clean and searchable, use the following best practices for Data IDs:

• Never reuse a Data ID in the same organization.
• Name Data IDs based on the flow they belong to. For example, a Prenatal Intake flow might use: PI01, PI02, PI03...
• Use sequential numbering where possible.
• Use Title Case for question titles. Avoid ALL CAPS or all lowercase.
• Make each question title searchable and specific—avoid repeating the same title across flows.
• Read-only questions will have a system-generated DROQ Data ID and cannot be customized.

After adding all your questions, click Save to create your flow. You can now attach this flow to any activity template.

If you’re unsure whether to use a script or an assessment, or need help designing a question set, contact your Customer Success Manager.