Configure Conditions and Triggers

Set up automatic actions that activate based on how operators answer questions in inspections or procedures.

Before You Start

• You need Manager or Supervisor permissions
• You must be creating or editing a template

How Conditions and Triggers Work

Condition: The criteria that must be met (e.g., "If answer is No") Trigger: The action that activates when the condition is met (e.g., "Notify supervisor")

Example: If an operator answers "No" to "Is the safety guard in place?", the system automatically notifies the supervisor.

Steps

Step 1: Select a question

1. Open the template in edit mode
2. Click on the question you want to configure
3. Find the conditions/triggers section

[Screenshot: Question selected with condition options visible]

Step 2: Add a condition

Conditions vary based on the question's response type:

Response Type	Available Conditions
Numeric field	Less than, greater than, equal to, is, is not
Text field	Is, is not, contains
Single selection	Is, is not
Multiple selection	Includes, does not include
Yes / No / N/A	Is Yes, is No, is N/A

1. Select the condition type
2. Set the value to compare against

[Screenshot: Condition configuration dropdown]

Step 3: Select a trigger

Once the condition is defined, choose what happens:

Trigger	Description	Example
Require an action	Creates a follow-up task	"Clean the spill"
Create a ticket	Generates a ticket for tracking	Risk detection triggers ticket
Notify someone	Sends alert to user/team	Notify supervisor of non-compliance
Require evidence	Prompts photo/video upload	Document the issue visually
Add nested field	Shows a follow-up question	"How long has it been like this?"

[GIF: Selecting a trigger and configuring it]

Step 4: Configure trigger details

Each trigger has specific settings:

Require an action:

• Enter the action description
• Set priority if needed

Create a ticket:

• Define ticket details or let operator fill them

Notify someone:

• Select user or team to notify
• Choose timing: immediately or at inspection end

Require evidence:

• Evidence upload prompt appears for operator

Add nested field:

• Add a follow-up question
• Select its response type
• Nested fields can have their own conditions/triggers (except adding another nested field)

[Screenshot: Notification trigger with user selection and timing options]

Step 5: Add multiple conditions (optional)

A single question can have multiple conditions with different triggers:

Example for "Temperature reading" (numeric):

• If > 100: Notify maintenance team
• If > 120: Create urgent ticket AND require evidence

Step 6: Save the template

1. Review all conditions and triggers
2. Click Save

Triggers activate during inspection execution based on operator responses.

Example Configurations

Safety Check

Question	Condition	Trigger
"Is emergency stop accessible?"	Is No	Notify safety supervisor immediately
"Are guards in place?"	Is No	Require evidence + Create ticket
"Is equipment clean?"	Is No	Add nested field: "What cleaning is needed?"

Temperature Monitoring

Question	Condition	Trigger
"Refrigerator temperature (°C)"	> 5	Notify quality team
"Refrigerator temperature (°C)"	> 8	Create urgent ticket + Require evidence

Tips

• Focus conditions on non-compliant or abnormal answers
• Use "Notify immediately" for safety-critical issues
• Require evidence for conditions that need documentation
• Test your triggers by executing a test inspection
• Use nested fields to gather more context without cluttering the main template
• Don't over-trigger — too many notifications can cause alert fatigue