There are two ways to create a follow-up Task in Opus:
From an Audit: Set up a trigger in advance, then create the Task when an auditor selects a triggering answer.
From a submission: Add a Task by hand after someone submits a Checklist or Audit.
For an overview of Tasks and how your team works with them day to day, see Tasks Overview.
Table of Contents
Creating Tasks from an Audit
Audit triggers let you decide in advance which answers should require follow-up. When an auditor selects one of those answers, Opus prompts them to create a Task before they can continue.
New to Audits? Start with Audits Overview.
Set Up the Trigger
A trigger is the rule that tells Opus when to prompt the auditor to create a follow-up Task. You set up the trigger once in the Audit builder:
Open the Audit in the dashboard builder and find the question that should prompt a follow-up.
Open the step menu and select Add Trigger.
Choose the answer that should require action.
For the Trigger action, choose Create a follow-up task.
Save the Audit.
You do not set the Task's due date, proof requirement, or approval setting here. The auditor chooses those when creating the Task during the Audit.
❗ Only the "Create a follow-up task" Trigger creates a Task. Audits have three trigger actions in total. See Setting Up Triggers for the full list.
Create the Task While Running the Audit
When the auditor selects a triggering answer, a follow-up card opens inside the Audit. They must complete the required fields before they can submit the Audit:
Title
Opus automatically generates a title using AI based on the question and the auditor's notes. For example, a flagged answer on How does the floor look? might generate Clean the Floor Thoroughly. The auditor can edit the title.
Assignee
Required. Every follow-up Task must have an owner before the Audit can be submitted.
Due date
Optional date by which the Task needs to be completed .
Proof of completion
Choose Photo or video, Written note, or None. Photo or video is the default.
Requires approval
On by default. When enabled, the auditor reviews the completed work before the Task is marked complete.
Notes
This is the Audit step's notes field and provides context during the Audit. It is not saved as the Task's description.
What Happens When the Audit Is Submitted
Once the auditor submits the Audit, Opus creates a separate Task for each follow-up:
Multiple follow-ups: If several answers require follow-up, Opus creates a separate Task for each one.
Multiple Tasks for one person: If an Audit assigns multiple Tasks to the same person, they receive a single notification that opens the full task list.
Task context: Each Task carries over the audited location, sets the auditor as the reviewer, and links back to the exact question, answer, and Audit submission.
Task details: The Task keeps the AI-generated title and the due date, proof requirement, approval setting, and assignee selected by the auditor.
💡 Every follow-up needs an assignee. An Audit cannot be submitted while a triggered Task is missing an owner. Opus highlights any follow-ups that still need to be assigned.
Creating Tasks from a Submission
You can also add a Task by hand after submitting a Checklist or Audit. This is the only way to create Checklist follow-up Tasks.
Create a Follow-Up Task
You can add a follow-up Task from either the dashboard or app:
Open the completed Checklist or Audit submission.
Go to the Follow-up Tasks tab and select New follow-up task.
Give the Task a clear title and add any details the assignee needs.
Choose the assignee, who will complete the work.
Set a due date, proof requirement, and whether the Task requires approval.
Create the Task to send it to the assignee.
Task Settings
A few settings work differently depending on where you create the Task:
Assignee: Choose an assignee so the right person is notified. The app requires an assignee. The dashboard does not technically enforce one, but always assign someone so the Task reaches the right person.
Proof of completion: The options differ slightly by platform:
Dashboard: Photo or video required, Photo required, Written note required, or Optional
App: Photo or video, Written note, or None
Requires approval: On by default. When enabled, the assignee submits the completed work for review before the Task is marked complete.
A follow-up Task takes its location from the submission, so the submission must have a location attached. Managers can only add Tasks for locations they manage.
💡When you create a Task by hand, you are the reviewer. You can change the reviewer later if someone else should sign off.
Tasks from the Assignee's Perspective
Tasks work best when the assignee has everything they need to understand and complete the work without having to track down additional context.
From the assignee's perspective:
Assignees receive a notification the moment they're assigned a Task.
Several Tasks from one Audit arrive as a single notification that opens the full Task list.
Their home screen shows a Tasks card alongside any open Checklist or Audit windows.
The All Tasks screen is organized into To do and Upcoming.
Assignees select Mark as In Progress, complete the work, and add any required photo, video, or note.
If approval is required, the assignee selects Mark as Ready for Review in the app or Submit for Review on the dashboard.
If approval is not required, they can select Mark Complete to close the Task.
If the reviewer requests changes, they receive a note explaining what needs to be fixed and can resubmit the Task.
Assignees can comment on the Task at any time to ask a question or share an update.
💡 Give the assignee enough context to act. Tasks created from Audits automatically link back to the original question, answer, and submission. For Tasks created by hand, use the title and description to explain what needs to be done.
FAQ
Can a Checklist create Tasks automatically like a triggered Audit?
No. You must add Checklist follow-ups manually after the submission. Automatic, trigger-based Task creation is an Audit feature. Learn more in Audits Overview.
What happens if I choose a trigger action other than "Create a follow-up task"?
No Task is created. Audits have three trigger actions in total, and the other two respond to a flagged answer in different ways. See Setting Up Triggers for details.
Can I write my own description for an Audit-triggered Task?
Not directly. The Audit step's notes field is not saved as the Task's description. The AI-generated title is the only description an Audit-triggered Task receives. You can edit the generated title if you need to add more detail.
Do I have to assign someone when creating a follow-up Task by hand?
The app requires an assignee. The dashboard does not technically enforce one, but always assign someone (even if it is yourself) so the Task reaches the right person and can be tracked to completion.
What can be edited on a Task, and by whom?
The assignee, reviewer, and due date can be changed after a Task is created. The title, description, proof requirement, approval setting, and location cannot be changed.
Only an Admin, reviewer, or Manager can edit a Task. The assignee cannot make these changes.
Who can delete a Task?
An Admin or Manager can delete a Task. Deleting a Task permanently removes it along with its comments and proof.