Triggers turn a Checklist answer into immediate follow-through. When a step gets a response that needs attention, Opus can flag it, prompt a fix, or notify the right team members automatically, so issues get handled during the shift instead of discovered later.
Table of Contents:
How Triggers Work
What Are Triggers?
Triggers are automatic actions tied to Checklist steps. They allow you to:
Flag as issue: highlight problems for easy reporting.
Suggest corrective action: prompt team members to fix issues.
Send automated message: notify the right team members based on step responses.
Why Use Triggers?
Triggers save time and reduce manual follow-ups. They help prevent "pencil whipping" (marking work complete without doing it) by creating actionable steps or notifying team members directly from your Checklists.
šÆ Example: If a team member answers "No" to "Is the walk-in cooler at temperature?", a Trigger can flag the step in reporting and send the Manager an automated message right away.
Step-by-Step: Setting Up Triggers in Checklists
ā Before you start: Triggers work on Checkbox, Yes/No, Number input, Temperature, and Multiple choice steps. Text entry steps can't have Triggers.
You need permission to edit the Checklist.
Here's how to add Triggers to your Checklists:
Open your Checklist.
In the dashboard, open the Checklist, go to the Build tab, and click Edit.
Choose a step.
Select the step where you want to add a Trigger, open its ⦠menu, and select Add Trigger.
Set the condition (If...). Define when the Trigger should activate, for example:
If a number or temperature is out of range
If a specific response is selected (for example, "No" on a Yes/No step)
Choose the action (then...). Decide what should happen when the condition is met:
Flag as issue: highlight it on the submitted Checklist and in reporting.
Suggest corrective action: prompt the team member to fix it as they complete the Checklist.
Send automated message: send an Opus message to the team members you choose under Select recipients. Optionally, click Add a custom note to include your own text.
(Optional) Click Add action to add another. Each Trigger can use each action once.
Save the Trigger.
Click Add Trigger to save your setup.
Publish.
Click Publish to apply your changes.
š” Triggers reach your team when you publish: Your changes save to a draft automatically, so team members keep using the last published version until you click Publish.
ā ļø No corrective action on Checkbox steps: A Checkbox left empty can't trigger an alert until the Checklist is submitted, so Suggest corrective action is unavailable on Checkbox steps.
FAQ
Can I add multiple actions to a Checklist step?
Yes. A Trigger can use each action once, so a step can have up to three actions. Checkbox steps can have up to two, because Suggest corrective action isn't available on them.
What happens if someone doesn't respond to the Trigger?
A Checklist can be submitted without acting on a Trigger, like a corrective action prompt. If the Trigger also has Flag as issue, the step shows as flagged in Checklist reporting.
Can I edit or delete Triggers later?
Yes.
Navigate back to the Checklist, go to the Build tab, and click Edit.
Open the step's ⦠menu and select Manage Triggers.
Make your updates and click Update Trigger, or click Delete Trigger to remove it.
Click Publish to apply your changes.


