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.
Start here to learn what Audits are and how to build one, then move on 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 area 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: a field leader evaluates how well a store meets your standards, broken into specific store areas or topics.
Store safety walkthroughs: check that equipment, signage, and procedures are up to standard.
Safety and compliance checks: verify that handling, storage, and labeling meet regulatory requirements.
How to Build an Audit
Go to the Audits page.
From the left-hand menu in your dashboard, go to Operations > Audits.
Click New Audit in the top right corner and choose New audit from scratch.
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 (for example, Excellent = 2 points, Mediocre = 1 point, Bad = 0 points). 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 (for example, 80%). If the final score falls below this, the Audit is marked as failed.
Publish.
When your Audit is ready, click Publish to make it available for your team.
š” Build it together: To let others edit, comment on, or view the Audit in the dashboard, click the Collaborators icon in the top right corner and give them access. Only Admins and Managers can be added.
Customizing Your Steps
Open the ā¦ menu on a step to add options:
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: Any step type in an Audit can 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 the Audit's Build tab in the dashboard.
Open the ā¦ 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 "Is any equipment damaged?" with "Yes," they see follow-up steps asking which equipment and what happened. If they answer "No," those steps don't appear.
After Publishing
Team Access
Once an Audit is published, your team members need Library Access to see and run it. On the Audit's Manage tab, select Library Access, click Add Access, and choose who should have access. Learn more in Library Access Overview.
š” Skip the clicks: Turn on QR code access so your team can scan a code and jump straight into the right Audit in Opus. Post codes in-store to keep Audits consistent and easy to reach. On the Manage tab, select Settings and set QR code accessible to Yes.
Setting a Schedule (Optional)
Set a recurring Schedule for an Audit so your team knows when it needs to be completed. Each Audit has one Schedule.
Open the Audit in the dashboard, go to the Manage tab, and select Schedule.
Click Configure Schedule.
Under Frequency, choose Daily, Weekly, Monthly, Quarterly, Semiannually, or Annually.
Under Locations, select the Locations the Schedule applies to.
Click Create schedule.
To change it later, click the edit (pencil) icon on the Schedule.
What's Next: Run, Resolve, Report
Once your Audit is built and published, here's where to go next:
How to Run an Audit: complete an Audit in the Opus Training app, on your own or with your 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 only need to confirm steps are done.
Who can build and publish Audits?
Admins, and Managers whose Role has the Create Content permission, can create and publish Audits in the dashboard.
Who can facilitate an Audit?
Anyone with Library Access to the Audit can facilitate it.
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. This only applies to Pass/Fail Audits ā see How to Score Audits for how Audit Grades work instead.
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?
In the app, anyone with Library Access to the Audit can see its submissions for their own Locations, and Admins see every Location. In the dashboard, Admins and Managers can review results on the Audit's Reporting tab (reports need the View Reporting permission). 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 collaborators on an Audit?
Only Admins and Managers can be added as individual collaborators. Trainees can't 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 your business; if you're a Manager, you can invite Managers at your Location.
These permissions only apply to the dashboard, not the app. Being added as a collaborator lets someone view, comment on, or edit the Audit content in the dashboard. It doesn't affect whether the Audit shows up in someone's app for completion. That is controlled by publishing and Library Access.