Building an Audit is only half the job. Someone still has to walk the floor and complete it, and if that step is clunky, follow-through slips. Opus keeps running an Audit simple: your team opens it in the mobile app, answers each step, and submits for an automatic score, with any flagged issues routed straight into a follow-up Task.

This article walks through how to run an Audit from start to finish, complete it with your team, and hand off anything that needs fixing.

Table of Contents

Audits are run from the Opus mobile app. Once you have Library access, you will find the Audit on your home screen or by searching your Library.

Audits can be completed collaboratively, just like Checklists. More than one team member can contribute to the same Audit submission, which is useful for larger walkthroughs that span several areas or shifts. Collaborative completion is on by default and can be turned off in the Audit's settings in the dashboard builder.

When a step is flagged during an Audit, Opus prompts you to create a follow-up Task before you finish. Each flagged step becomes its own Task, which you assign to a team member at that location, with a due date, the proof you want back, and whether it needs your approval. The assignee does the work and submits it, then you approve it or request changes.

Audits can only be completed in the Opus mobile app. You can build and review them in the dashboard, but the run itself happens on mobile.

Yes. You need Library access to the Audit. Any user who has been granted that access can facilitate the Audit.

Opus calculates your score automatically and marks the Audit passed or failed against the passing threshold the Admin set. If any steps were flagged, you are prompted to create and assign a follow-up Task before finishing. To see results afterward, head to Audit Reporting.

Yes. Collaborative completion lets multiple team members contribute to one Audit submission. It is on by default and can be turned off in the Audit's settings.