Create a follow-up Task in Opus from an Audit or from a submission:
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 set up a follow-up Task before they can submit the Audit.
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 it up once in the Audit builder:
Open the Audit, go to the Build tab, and click Edit.
Find the question that should prompt a follow-up, open its … menu, and select Add Trigger (Manage Triggers if the step already has one).
Choose the answer that should require action.
Under then, keep the action set to Create a follow-up task, which Audits select by default.
Click Add Trigger.
Click Publish to apply the Trigger.
💡 Publish to apply: The builder saves your changes to the draft automatically. Auditors don't see the new Trigger until you click Publish.
You don't 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 Audits Overview: Customizing Your Steps 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. The auditor can edit it.
For example, a flagged answer on How does the floor look? might generate Clean the Floor Thoroughly.
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, and later follow-ups in the same Audit start from the auditor's last choice.
Requires approval
On by default. When enabled, the auditor reviews the completed work before the Task is marked complete.
Notes
The Audit step's notes field, shown only when the step collects notes. The Task shows these notes with the question and answer, so the assignee sees the auditor's context.
What Happens When the Audit Is Submitted
Once the auditor submits the Audit, Opus creates the follow-up Tasks:
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.
➡️ Learn more:
Audits Overview: how Audits work, if you're new to them.
Creating Tasks from a Submission
Admins and Managers can also add a Task by hand after a Checklist or Audit is submitted. This is the only way to create Checklist follow-up Tasks.
Create a Follow-Up Task
✅ The submission needs a Location: 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.
You can add a follow-up Task from either the dashboard or the app:
Open the submission. On the dashboard, open the Checklist or Audit and go to Reporting > Submissions.
Go to Follow-up tasks and select New follow-up task.
Describe the work in Task and add any context the assignee needs in Details.
Choose the Assignee. Opus pre-selects the team member who filled out the submission.
Set a due date, proof requirement, and whether the Task requires your approval.
Click Create task on the dashboard or tap Create in the app.
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 doesn't 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 your approval: on by default. When enabled, the assignee submits the completed work for review before the Task is marked complete.
💡 You are the reviewer: When you create a Task by hand, you sign off on it. You can change the reviewer later if someone else should sign off.
Tasks from the Assignee's Perspective
Notifications: assignees are notified the moment they're assigned a Task.
Home screen: a Tasks card appears alongside any open Checklist or Audit windows.
All Tasks: tap View all tasks. The To do section lists Tasks and open windows, soonest deadline first, and Upcoming lists Checklist windows that haven't opened yet.
Doing the work: assignees select Mark as In Progress on the dashboard or Mark as in progress in the app, 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 in the app or Mark as Complete on the dashboard to close the Task.
Changes requested: if the reviewer requests changes, the assignee receives a note explaining what needs to be fixed and can resubmit the Task.
Comments: 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 in the dashboard, pick the Step (Audit step on an Audit) the Task is about so it links to that answer, and use Details 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.
What happens if I choose a Trigger action other than "Create a follow-up task"?
No Task is created. The other two Audit Trigger actions, Flag as issue and Send automated message, respond to the answer in other ways.
Can I write my own description for an Audit-triggered Task?
Not during the Audit. The Task shows the Audit question, the answer, and the auditor's notes as context instead.
To add more detail, edit the generated title before you submit the Audit.
Do I have to assign someone when creating a follow-up Task by hand?
The app requires an assignee. The dashboard doesn't technically enforce one, but always assign someone (even if it's yourself) so the Task reaches the right person and can be tracked to completion.
What can be edited on a Task, and by whom?
Can be changed: the assignee, reviewer, and due date.
Can't be changed: the title, description, proof requirement, approval setting, and Location.
Admins, the Task's reviewer, and Managers of the Task's Location can edit it. The assignee can't make these changes.
Who can delete a Task?
Admins can delete any Task, and Managers can delete Tasks at their Locations. Deleting is permanent and removes the Task along with its comments and proof.