Overview
Site Audits 2.0 standardizes property inspections across your organization. It allows you to create reusable audit templates with predefined sections, questions, and scoring criteria so you can collect consistent data, generate meaningful reports, and identify issues faster.
Site Audits 2.0 provides a structured, template-driven approach. Instead of relying on loosely defined categories and scoring types, you can build templates for your auditors to follow step by step in the field.
Who this affects: System Administrators and Office Managers who create and manage templates; Account Managers, Operations Managers, and Sales Representatives who perform audits; and Ops/General Managers who review audit results.
Things to know
Site Audits 2.0 is controlled by a feature flag that your organization must have enabled.
The legacy Site Audit experience remains available during the Early Access period. The two systems operate independently, and existing legacy data will not be imported into Site Audits 2.0.
Templates are the foundation of every audit in 2.0. You can't start a new audit without selecting a template.
Templates are branch-specific. A template only appears for users working in branches where the template has been assigned.
Requirements
Access to Site Audits 2.0 depends on the permission level assigned to your user role. Permissions are found under the Site Audits category in Administration > User Management > User Roles.
Note:
Removing a higher permission level doesn't automatically remove the lower levels. For example, removing the Admin permission doesn't remove View or Edit — those remain enabled unless you clear them separately.
How it works
Site Audits 2.0 is built around three core components: templates, tags, and audits. Together, they form a structured workflow where administrators define what gets inspected, organizers categorize templates for easy retrieval, and field teams follow a consistent process at every property.
Templates
A template defines the structure of an audit. Each template contains:
Settings — The template name, status (Active or Inactive), branch assignments, and tags.
Sections — Logical groupings within the template, defined by a Headline section type. Each section includes a headline and an optional description that provide context for auditors.
Questions — Individual data collection points within each section. Questions belong to one of three response types:
Text — Free-form written responses. Supports optional placeholder text and a required toggle.
Multiple Choice — A predefined list of options where the auditor selects one answer. Requires at least two options.
Multi-Select — A predefined list of options where the auditor selects one or more answers. Requires at least one option.
Templates are built in the Template Builder, which provides drag-and-drop reordering for sections and questions, duplication of question blocks, and a three-dot action menu for delete and duplicate actions.
To learn more, read our article about setting up Templates.
Tags
Tags are labels you assign to templates for organization and filtering. You can use tags to group templates by property type, service line, client requirement, or any category that fits your workflow. Tags are managed from a dedicated screen and can also be created inline while building a template.
Site Audits
An audit is a completed (or in-progress) instance of a template applied to a specific property. When an auditor starts a new audit, they select a template. The audit inherits the template's sections and questions, and the auditor fills in responses. Once submitted, the audit becomes a record associated with that property.
Key terms
Workflows
Template lifecycle
Created (Inactive) — An administrator creates a new template. It defaults to Inactive, meaning it's saved but not available for audits. The administrator defines the settings, sections, and questions using the Template Builder.
Active — When the administrator changes the status to Active and assigns at least one branch, the template becomes available for audits at those branches. Users with Edit or Admin permissions can select it when starting a new audit.
Edited — An Active or Inactive template can be edited at any time. Changes to an Active template apply to future audits only — audits already in progress or completed aren't affected. [VERIFY — confirm whether editing an Active template affects in-progress audits]
Deactivated — When your administrator changes the status back to Inactive, the template is no longer available for new audits. Previously completed audits that used this template remain accessible.
Audit lifecycle
Started — A user with Edit or Admin permission starts a new audit by selecting a template and a property. The audit inherits the template's current structure.
In Progress — The auditor works through the sections and questions, filling in responses.
Completed — The auditor submits the audit. All required questions have been answered. The audit becomes a permanent record associated with the property.
Behavior notes and exceptions
Branch-level visibility: Templates are only visible to users working in branches where the template has been assigned. If a user has access to multiple branches, they see only templates assigned to the branch context of the property being audited.
Permission hierarchy: The three permission levels are cumulative. View is the base; Edit includes View; Admin includes View and Edit. Selecting a higher level automatically enables the lower levels, but removing a higher level doesn't remove the lower ones.
Required questions: When a question is marked as required in the template, the auditor can't submit the audit without providing a response for that question. Optional questions can be left blank.
Question response type validation: Multiple choice questions require at least two predefined options. Multi-select questions require at least one predefined option. Text questions have no minimum — they accept any free-form input.
Tag assignment status: Tags display an "Assigned to Template" status indicator when they're associated with at least one template. A tag created from an Inactive template may not immediately reflect this status.