Running audits in a standalone app or in a spreadsheet means follow-through is hard to track. Opus Audits solve this by keeping the entire process, from scoring to action items to sign-off, in one place, in the same app your team already uses for training and tasks.
This article explains what Audits are and how to build one. From here, you can jump to running an Audit, resolving flagged issues, and reviewing results.
Table of Contents
What Are Audits?
An Audit is a scored inspection used to make sure your operations are meeting your standards. You walk through a list of multiple-choice questions (like "Is the kitchen clean?" or "Are expiration dates current?"). The Audit is set up with scoring, so it can automatically give you a score based on your answers.
Admins can set a passing score ahead of time (like 80%). If the final score is lower than that, the Audit fails. If any steps have problems, you can assign someone to fix them and then check their work before closing it out.
Common uses include:
Location Audits: when a field leader evaluates how well the store is up to standard. These could be broken into specific store sections or topics.
Store safety walkthroughs: check that equipment, signage, and procedures are up to standard.
Food safety and compliance checks: verify that handling, storage, and labeling meet health requirements.
How to Build an Audit
Go to the Audits page.
From the left-hand menu in your dashboard, go to Operations > Audits.
Click the blue "+ New Audit" button in the top right corner to start building.
Name and describe your Audit.
Give your Audit a name and a short description so your team knows what it covers.
Add sections.
Sections break the Audit into organized parts, making it easier for auditors to navigate.
Add verification steps. Click "+ Add Step" and choose from these step types:
Scored multiple-choice: each answer option is assigned a point value (e.g. "Excellent" = 2 pts, "Mediocre" = 1 pt, "Bad" = 0 pts). These steps calculate the overall Audit score.
Text entry: the auditor types a free-form response.
Customize your steps (optional). Add required answers, Triggers, notes, photo or video uploads, media, and conditional steps. See Customizing Your Steps below.
Set a passing threshold.
Set the minimum score needed to pass (e.g. 80%). If the final score falls below this, the Audit is marked as failed.
Publish.
When your Audit is ready, publish it to make it available for your team.
đ¤ To let others edit, comment on, or view the Audit in the dashboard builder, click Contributors in the top right corner and assign access. Only Admins and Managers can be added.
Customizing Your Steps
By clicking on the ellipsis (...) in each step, you can add additional options to your steps:
Required: Make steps mandatory to answer before submitting.
Triggers are automatic actions based on how a step is answered:
Flag an issue: Highlight a problem in reporting.
Create a follow-up task: Assign a Task so the issue gets owned and fixed.
Send an automated message: Notify the right team members.
Notes: Allow or require the auditor to leave a written note.
Photo or Video upload: Allow or require a photo or video to be attached.
Media or linked content: Attach reference images or link to relevant Courses or Resources from your Library.
Conditional steps: follow-up steps that only appear based on how a previous step was answered (see below).
đ¸ Collect photos and videos in Audits: Any step type in an Audit can be set to include photo or video submissions. Your team can take a new photo or video or choose one from their camera roll, and multiple uploads are supported per step, giving you a complete, timestamped visual record for every item.
Conditional Steps
Conditional steps only appear based on how an auditor answers a previous step. This keeps Audits focused and makes sure auditors only see the steps that apply to their situation.
To add a conditional step:
Open your Audit in the builder on the dashboard.
Click the three-dot menu (...) on any step and select "Add a conditional step."
Set your condition: choose when the follow-up step should appear.
Choose your follow-up step: create a new one or select an existing step from the dropdown.
Click "Create condition."
Example: If an auditor answers "Does this location have an ice cream machine?" with "Yes," they will see follow-up steps about the machine. If they answer "No," those steps won't appear.
After Publishing
Team Access
Once an Audit is published, your team members need Library access to see and run it. Admins can manage this from Library Access.
Run Audits without the extra steps. Enable QR code access to jump straight into the right Audit in Opus. Post them in-store to keep Audits consistent and easy to access. Head to the Manage tab > Settings > QR accessible = Yes.
Setting a Schedule (Optional)
You can set a recurring schedule for any Audit so your team knows when it needs to be completed.
Open the Audit in the dashboard and go to the "Manage" tab.
Select a frequency: daily, weekly, monthly, quarterly, semi-annually, or annually.
Select the locations the schedule applies to.
Click "Create Schedule."
What's Next: Run, Resolve, Report
Once your Audit is built and published, here is where to go next:
How to Run an Audit: complete an Audit in the mobile app, on your own or collaboratively as a team.
Audit Tasks: assign, complete, and approve a follow-up Task for any step flagged during an Audit.
Audit Reporting: review submissions, scores, schedule completion, and trends across locations.
FAQ
What is the difference between a Checklist and an Audit?
Audits are scored and Checklists are not. Audits are built for verification and accountability. They score responses, can fail, and turn flagged issues into follow-up Tasks you can track and resolve. Checklists are better suited for routine operational checks where you just need to confirm steps are done.
Who can build and publish Audits?
Admins and Managers with Create Content permissions can create and publish Audits from the dashboard.
Who can facilitate an Audit?
Any user who has been granted Library Access can facilitate an Audit.
What happens if an Audit fails?
If a submitted Audit score is below the set passing score, the Audit is marked as failed. If a step is set to create a follow-up Task, that Task is created so the issue can be tracked and resolved.
Can a step be included without a point value?
Yes. Text entry steps are not scored and can be used to capture notes or open-ended information.
Where can I see Audit scores and results?
Any user with access to the Audit can see the results in the Opus Training app and the Opus dashboard. For a full breakdown, see Audit Reporting.
What if the work on a Task is not done right?
The reviewer can request changes and send the Task back with a note. The assignee makes the fixes and resubmits, and this repeats until the reviewer approves the Task.
Who can be added as contributors to the dashboard builder?
Only Admins and Managers can be added as individual contributors. Trainees cannot be added. To add someone, you need edit access to the Audit yourself. If you're an Admin you can invite Admins or Managers from across the business; if you're a Manager you can invite Managers at your location.
These permissions are strictly for the dashboard builder and Library, not the mobile app. Being added as a contributor lets someone view, comment on, or edit the Audit content in the dashboard. It does not affect whether the Audit shows up in a user's mobile app for completion. That is still controlled by publishing, assignments, and role and location rules.