Audits and Checklists show you what's happening across your Locations. Tasks make sure the right things get fixed.
A Task turns a flagged issue or follow-up into a specific piece of work with an owner, due date, and proof of completion. The assignee does the work, and a reviewer can sign off before the Task is closed.
With Tasks, you can:
Make sure nothing slips: every issue has an owner and a status you can see at a glance.
Build in real accountability: require a photo, video, or note as proof, and approve the work before it counts as done.
Keep context attached: a Task created from a form links back to the exact question and answer, so the assignee knows why it matters.
Track everything in one place: your team sees their Tasks in the Opus Training app, and you track every one from the dashboard.
Table of Contents:
How Tasks Are Created
Tasks are created from Audits or Checklists. Each Task stays linked to the submission it came from, so the assignee can see the original context.
You can create Tasks:
From an Audit: configure an Audit so an auditor can create a Task when an answer requires follow-up.
Set this up when you build the Audit in the dashboard. Learn more in Audits Overview.
From a Checklist submission: after a Checklist is submitted, an Admin or Manager can add a follow-up Task by hand.
➡️ Learn more:
How to Set Up and Manage Tasks: set up an Audit Trigger, then create and manage Tasks step by step.
Understanding Tasks
Every Task tracks:
Who is doing the work
Where it needs to happen
When it is due
What proof is required
It also stays linked to the Audit or Checklist submission it came from.
Task Roles
Role | What they do |
Assignee | Completes the Task and adds any required proof |
Reviewer | Reviews submitted work and approves it or requests changes |
Admin or Manager | Can manage Tasks, including editing or deleting them |
The reviewer is the person who created the Task by hand or the auditor who created an Audit-triggered Task.
The reviewer can be changed later if someone else should sign off.
The Task Lifecycle
A Task starts in Not started when it is assigned. It moves through these stages, and whether it passes through review depends on whether approval is required:
Not started → In progress → Ready for review → Completed
After a Task is assigned:
The assignee selects Mark as In Progress in the dashboard or Mark as in progress in the app to start the work.
What happens next depends on the Task's approval setting:
Approval required: the assignee submits the Task for review by selecting Submit for Review in the dashboard or Mark as ready for review in the app. The Task then waits for the reviewer.
Approval not required: the assignee marks the Task complete, and it moves directly to Completed.
When a Task is Ready for review, the reviewer can:
Select Mark complete to approve the work and complete the Task.
Select Request changes to send it back to the assignee. A note explaining what needs to be fixed is required. The Task returns to In progress so the assignee can make the changes and resubmit it.
⚠️ Completing a Task is final: A completed Task can't be reopened. Check the proof before you select Mark complete.
💡 Past due Tasks: If a Task passes its due date before it's completed, it's flagged in red.
Creating a Task from a Submission
After a Checklist or Audit has been submitted, you can create a Task in the dashboard or in the app.
Audit Tasks can also be created automatically during an Audit.
In the Dashboard
Open the Checklist or Audit, go to Reporting > Submissions, and open the submission.
Click the Follow-up tasks tab, then New follow-up task.
Enter the Task and any Details the assignee needs.
(Optional) Under Step, pick the step the Task is about.
Choose the assignee.
Set a due date, the proof required, and whether the Task needs your approval.
Click Create task.
In the Opus Training App
Open the completed Checklist or Audit submission.
Tap the Follow-up tasks tab, then New follow-up task.
Enter a title and any details.
Choose the assignee (required in the app).
Set a due date, the proof required, and whether the Task needs approval.
Tap Create.
Where to Find Tasks
Where you look depends on what you're trying to do:
Manage Tasks across your Locations: the dashboard.
Work your own Tasks day to day: the Opus Training app.
Check whether follow-ups were resolved: the Audit or Checklist submission.
Dashboard
Best for: managing Tasks across your Locations, filtering and searching, and Admin-level oversight.
Go to Operations > Tasks.
Admins see every Task. Managers see Tasks for the Locations they manage.
The list shows:
Title, Location, Assignee, Created, Due date, and Status
Source audit: the Audit or Checklist the Task came from
Brand, if your business uses Brands
To narrow the list:
Use the search bar, or the Status and Location filters.
Or find a Task from the submission that created it, on its Follow-up tasks tab.
Opus Training App
Best for: working your own Tasks day to day.
The Tasks section of your home screen shows your Tasks alongside open Checklist and Audit windows, up to three items at a time.
Tap View all tasks to open Tasks. The To do tab lists your Tasks and open windows, then upcoming Checklist windows. The Submissions tab lists submitted Checklists and Audits.
Audit or Checklist Submission
Best for: checking whether an Audit's or Checklist's follow-ups have been resolved, Location by Location.
Each Audit submission shows whether its follow-up Tasks are still pending or resolved, so you can spot which Locations need attention at a glance.
To find them:
Go to the dashboard.
Open the Audit or Checklist and click the Reporting tab.
Find the submission in the Submissions view and click it.
Open the Follow-up tasks tab.
💡 Nudge the assignee: Open a Task directly from here to check its status, leave a comment, or add a photo.
Tracking a Task
Once a Task is created, Admins and Managers get full visibility into its activity, in both the dashboard and the app.
Every Task keeps a running activity log, so you can see exactly what happened and when:
When it was created, and from which Audit or Checklist
When the assignee started it and added proof
When they submitted it for review
Any changes the reviewer requested
When it was completed
Notifications
Task notifications are push notifications in the app. If push notifications are off, Opus sends a text instead.
Assigned: the assignee is notified.
Several Tasks from one Audit arrive as a single notification that opens the full Tasks list, not one notification per Task.
Submitted for review: the reviewer is notified.
Changes requested: the assignee is notified, with the reviewer's note.
Completed: the assignee and reviewer are notified, except whoever completed the Task.
Comments: participants are notified of new comments. An @mention sends a separate alert.
Reassigned: only the new assignee is notified. The previous assignee is not.
⚠️ There are no due-date reminders: Opus does not send "due soon" or overdue alerts. The red Past due or Overdue label is the only signal.
FAQ
Can I create a Task from scratch?
No. A Task always starts from a completed Audit or Checklist submission. Create it from the Audit or Checklist it relates to so its context stays attached.
Who is the reviewer?
The reviewer is the person who created the Task by hand or the auditor who created an Audit-triggered Task. You can change the reviewer later if someone else should sign off.
Can I reassign a Task?
Yes. The assignee, reviewer, and due date can all be updated after the Task is created.
Can a completed Task be reopened?
No. Once a Task is marked complete, it cannot be reopened by the reviewer, Admin, or anyone else. If it was closed by mistake, delete it and create a new Task.
Who can add or remove proof?
Only the assignee can add or remove proof. Opus checks the proof requirement both when the assignee submits the Task and when the reviewer marks it complete.
The proof must match the requirement. For example, a photo does not satisfy a Written note requirement, and a written note does not satisfy a Photo requirement.
Does completing a follow-up change the Audit score or result?
No. The score and result, like Pass, Fail, or a grade, are set when the Audit is submitted and do not change afterward.
The Audit records what was true at the time of submission. The Task tracks the work needed to fix the issue.






