Skip to main content

⑦ Review & publish options

Defaults for the published report, and whether a technical review is required.

Written by Caim Hermoso

Who this is for: Needs Manage My Audit Templates.

Setting

Default

Effect

Include Root Cause by default

Off

Sets the starting position of the Include Root Cause Analysis toggle when the audit is published

Include Corrective Actions by default

Off

Sets the starting position of the Include Corrective Actions toggle when the audit is published

Require Technical Review

Off

Audits from this template must be approved by a technical reviewer before they can be published

The first two are defaults, not locks — the auditor can change them when publishing. Switch them on where the audience for your reports expects to see the analysis, and off where the report goes outside the organisation and you would rather share findings without internal root cause detail.

Require Technical Review is the significant one. When it is on:

  1. The auditor must choose a Technical Reviewer on the audit’s Audit Details step.

  2. When the audit is finished, the auditor selects Request Review — they cannot publish directly. The audit shows as For Review and the reviewer is notified.

  3. The reviewer reads the full draft report and either selects Approve & Publish, which publishes the audit, or Reject with Reason, which returns it to In Progress for the auditor to fix.

The auditor cannot be their own technical reviewer.

Set this per template, not globally. A full system audit or a certification-facing audit is worth reviewing. A daily cleaning check or a weekly fire door walk-round is not — the review step would just create a bottleneck.

Did this answer your question?