When an Audit flags an issue, Opus doesn't just surface it. It kicks off a clear workflow to make sure the issue actually gets fixed.
The auditor assigns a Task, the right person at that location takes action, and nothing gets closed out until the auditor signs off. Every flagged step is tracked from submission to resolution.
Table of Contents:
Step-by-Step Guide
Tasks can be created while completing an Audit, or by hand after it is submitted. For a full overview, see Tasks Overview. To learn how to set up the steps that trigger a follow-up Task, see the Audits Overview guide.
The Full Lifecycle at a Glance
An Admin builds the Audit and marks which answers need a follow-up.
A leader (for example, a Regional Manager) runs the Audit on the floor.
As they go, the auditor creates a follow-up Task for anything flagged.
On submit, the Audit and its Tasks are finalized and sent out.
The assignee (often a GM or store owner) sees the Tasks they need to do, right in their app.
They do the work and submit each Task for review, with proof.
The auditor reviews the outcomes and approves, or sends it back with a note.
The whole lifecycle is visible to everyone, start to finish.
Step 1: Assign the Task (Auditor)
When an auditor gives an answer that needs follow-up, Opus prompts them to assign a Task before they finish the Audit.
Opus drafts the Task title automatically with AI from the flagged question and the auditor's notes, and it can be edited.
The auditor selects an assignee, who must be someone at the Audit's location. An assignee is required.
The auditor can set a due date, choose the proof required, and add any notes before sending.
š” A Task can be assigned to anyone at that location, including trainees, so whoever is on the floor can take care of what needs to be done.
Step 2: Complete the Task (Assignee)
Once the Audit is submitted, the Task appears on the assignee's home screen in the Opus Training app. They are also notified with a push notification.
The assignee starts the Task, does the work, and adds any required photo, video, or note as proof.
Once the work is done, they submit the Task back to the auditor for review.
Step 3: Review and Approve (Auditor)
After the assignee submits the Task, it returns to the auditor in the Opus Training app.
The auditor reviews the work and can approve the Task if the issue is resolved, or request changes if more is needed.
If the auditor requests changes, they add a note and the Task goes back to the assignee to fix.
This continues until the auditor approves the Task.
š” Every Task is tracked from start to finish, so nothing falls through the cracks.
FAQ
What triggers a Task?
When an auditor gives an answer set up to require follow-up, Opus prompts them to assign a Task before the Audit is submitted. The Task starts with a title drafted from the flagged question.
Who can be assigned a Task?
Only users at the same location where the Audit was submitted can be selected as the assignee.
Where do assignees find their Tasks?
Tasks appear on the assignee's home screen in the Opus Training app. They will also receive a push notification when a Task is assigned to them.
What happens if the auditor is not satisfied with the work?
The auditor requests changes and adds a note, which sends the Task back to the assignee. They complete it again, the auditor reviews again, and this repeats until the Task is approved.
Can the auditor set a deadline for a Task?
Yes. When assigning the Task, the auditor can set a due date and add any notes before sending it to the assignee.