Skip to main content

Updated Audit Setup Wizard

Note: This will become the default experience on October 26, 2026.

Overview

The updated Audit Setup Wizard walks you through creating an audit in four steps: choose a program, set the scope, build the evidence request list, and add the audit's details. Nothing is created until the last step, so you can move back and forth freely. Leaving the Wizard before finishing will save a copy of that Audit for completion later.


Before Creating A New Audit

Before you begin, have these ready if they apply to your audit:

  • The Program you are auditing against (if you use one)

  • The Controls or Objectives you want in scope

  • A Request List as a CSV file (if your auditor or a previous engagement provided one)

  • The name or email of the person who will manage the audit

Choose your starting point

Your answers in Steps 1 and 2 shape the rest of the wizard. Use this table to decide.

If you want to

Choose

Repeat an earlier engagement (eg, last year's SOC 2)

Step 1: Base this audit on a previous one

Test each control in a program you already manage (eg, this year’s SOC 2)

Step 1: Use an existing program.

Step 2: On each control

Audit against a framework's requirements without relying on controls (eg, PCI)

Step 2: On each objective

Work from a request list your auditor gave you, without a program, controls or objectives

Step 2: On each request

Run a gap assessment, readiness review or internal audit with no program

Step 1: No program

Start A New Audit

Open Compliance -> Audits (Arrow 1a) and select + New audit (Arrow 1b)

Note: Please refer to this article for the updated Audit Management view


Step 1: Choose a Program

The wizard opens on the Program step. All four steps of the Audit creation process (Program, Scope, Requests, Review & details) run across the top of the Wizard (Box A). A Summary panel on the right fills in as you make choices (Box B).

There are four ways that users can start a new audit:

Method 1: Base this audit on a previous one if the audit is to be based on a prior audit (eg, SOC2 from last period)

Note: Users still walk through the remaining steps and can change anything before the audit is created.

Method 2: Use an existing program if this is a completely new audit to be based on an established Program. Recent Programs appear first, followed by all Programs.

Note: Programs are instances of a framework, and Zen can hold several per framework.

Method 3: No program: gap assessment, readiness review, or internal audit if this audit is meant to capture

Method 4: Resume an unfinished audit setup if you started building a new audit and had to stop before completion


Step 2: Set the Scope

The Scope step decides what is tested and how results are scored.

Note: When you start from a program, its controls are already selected.

Step 2.1 - How will assessments work?

  • On each control (Box A): Controls are tested, and results roll up to the objectives they map to. This is the familiar approach and suits most audits.

  • On each objective (Box B): Objectives are assessed directly, with no control layer in between. This suits frameworks where the audit is based on requirements, and it works even if you have not defined controls. Assessments are always created for each objective in scope.

  • On each request (Box C): Each request concludes from the evidence returned for it. No objectives or controls are assessed. This suits an audit driven by your auditor's request list.

    Note: selection of cards in step 2.1 will change the options available to users in steps 2.2, 2.3 and 2.4.

Step 2.2 - Assessment Scoring

Keep ZenGRC Default or choose another method from the Scored by list. ZenGRC Default concludes on Design, Operation and Maturity. Other methods appear only when an Administrator has set them up in System Settings.

If the Audit is based "On each Control"

If the audit assessment is based on each Control:

Step 2.3 - Which part of the framework does this audit cover?

Search for and select the Program Sections to include:

Step 2.4 - Which controls get tested?

Review the Controls necessary for this audit assessment. When you start from a program, its controls are already selected. Users can:

  • Search by name, code or tag to find specific controls.

  • Use Select all or Edit on a group to change which controls are selected

If the Audit is based "On each Objective"

If the audit assessment is based on each objective:

Step 2.3 - Which objectives get assessed?

Review and select the sections’ objectives to be included in this audit assessment. Click on Narrow to expand each Section and narrow down the objectives to be included.

Note: If the program has no mapped objectives, the wizard tells you so. That is expected for many control-based audits.

If the Audit is based "On each Request"

There is no third step under Scope when the audit is based on each Request.

It is also possible to delay choosing the Scope and instead add controls or objectives later.

Step 2.5 - Review the Summary panel

The Summary panel shows how many controls are in scope and how many control assessments will be created. The panel changes based on the way that the user determines how the assessments will work.

As users choose which Sections/Controls/Objectives they want included in the Audit, the Summary panel figures will update as well.

The image below shows a Scope screen with the option “On each control” chosen by the user. Note the count of the figures in the Summary panel (Box A). The value “394 objectives in scope” are affected by what is chosen in the section “Which part of the framework does this audit cover?” (Box B). The values 230 controls and 230 control assessments are determined by what is chosen in the “Which controls get tested?” portion of the Scope step (Box C).

In the subsequent image, the user deselected one program from Which part of the framework does this audit cover? and several Control Sets in the section Which controls get tested? Notice how the Summary panel (Box A) values change based on the removal of these Sections (Box B) and Controls (Box C).

The user deselected five Control Sets from the Which controls get tested? section (Box C) and yet the Summary panel shows a decrease of only one control and one control assessment (from 230 to 229). This is because one control can be counted under several Control Sets: when the user deselected the accountability Control Set, the Audit Wizard removed all Control Sets that only contained the sole control (GOV-01-Cybersecurity & Data Protection Governance Program) found under the accountability Control Set.

Note: Control Sets come from the tags assigned to Controls, and Controls without tags appear under Ungrouped. Update tags within controls to change Control Sets.


Step 3: Build the request list

The Audit Client provides evidence based on what is chosen in the Request list. There are four ways that users can begin their Request list:

Option

What it does

Suggested list for your scope

Creates one request per item in scope, already mapped to it.

Start from an existing list

Pick a saved request list, or copy the requests from a previous audit. Saved request lists come from tags on your requests.

Upload a request list

Import a CSV from a prior engagement, your auditor or another tool.

Start with an empty list

Create the audit with no requests and add them later. Select the link under the options.

Suggested list for your scope

For most users, the option Suggested list for your scope will be appropriate for Auditing needs. In choosing this option, users will prompt the Audit Wizard to create one Request per scoped Control (which were set during Step 2: Set the Scope).

Start from an existing list

For users who already have an established list from which they want to work, they can select Start from an existing list. They are they able to select a list from:

  • a saved Request list (Arrow 1)

  • a prior Audit (Arrow 2)

Upload a request list

Some users may receive a list of Requests from an auditor, may keep Requests in a separate file, or are working in conjunction with another platform. For users who are taking a list of Requests from outside the platform, they can use the feature Upload a request list to upload multiple Requests into the Audit.

Before Request Upload

After Request Upload

Note: Users should compare their external list format against the request list template included in the Wizard to ensure that each Request is properly uploaded.

Or start with an empty list and add requests later


Step 4: Review & details

The final step in the Audit Setup Wizard includes sections where users can enter final yet important details:

  • Enter the Audit title (Box A). Use a name your internal team and/or auditors will recognize, including the framework used and the audit period (eg, "Weyland Yutani - SOC II - Oct 2026 to Mar 2027")

  • Under Audit Managers (Box B), start typing a name or email and select the person from the list

    • The Audit Manager owns the engagement and can change anything on it; there can be more than one Audit Manager

  • Under Default assessors (Box C), choose who is assigned as assessor on the assessments the wizard creates. The default is Audit Manager.

  • Optional: select Show dates (Arrow 1) to enter Fieldwork start, Audited period from and Audited period to (Box D)

Before clicking on Create Audit, users should review Summary panel on the right for accuracy:

In addition, users should review the On Create portion of the Summary card for an automated written explaination of what will happen after Create Audit is selected.

Once users have confirmed that the information is correct in the Review & details portion of the Audit Setup Wizard, they should click on Create Audit. Selecting this will bring the user to a page showing the creation status of the Audit.

The platform will work on the audit in the background, so the user who create the audit can navigate away from this page as the audit creation process finishes.

The newly created audit's status is set to Draft after it is created. Users can change this status in the Audit Listing page by hovering their cursor in the Status cell (Box A). This will reveal a pencil icon, which users should select (Arrow 1).

Users can then change the audit status in the subsequent dropdown menu that appears.

Tips for using the wizard

  • Select Back at any time to change an earlier choice. After going back, use Continue to move forward through each step again.

  • Scope, Requests and Assignees can all be changed on the audit page after it is created

  • If you gather evidence in one audit and test in another, create the evidence-gathering audit with the controls in scope, then share its evidence with the audit your auditor sees

    • This keeps internal comments and back-and-forth out of the auditor's view

What is different from the previous wizard

  • Audit details (title, managers, dates) now come at the end instead of the beginning.

  • The audit, its assessments and its requests are all created in one step at the end. Previously, the audit record was created when you left the first step, and an abandoned wizard could leave requests behind.

  • Users can base a new audit on a previous one from the start of the wizard.

  • Audits can now be assessed on each control, objective or request

  • ZenGRC can suggest a request list from your scope

  • Users can choose a scoring method for the audit's assessments

  • The wizard leaves the new audit in Draft rather than starting it.

  • The new wizard replaces the previous audit setup process, and there is no option to switch back.

Troubleshooting

Problem

What to do

I cannot find my program

Search by name in the Search your programs box. The list shows only programs in your instance. If the program does not exist yet, create it first, or choose No program.

The wizard says no objectives are mapped to the program

This is expected if your program is built on controls only. Continue with a control-based audit.

Continue or Create Audit is unavailable

On the Requests step, choose an option first. On the last step, fill in the audit title, at least one audit manager and the default assessors.

A CSV upload shows warnings

Check the column names against your template (for example Assignee, not Assignees) and confirm that assignees are ZenGRC users. Unknown assignees are replaced with the default assignee.

Control or request groups are missing

Control set groups and saved request lists are built from tags. Tag your controls or requests to create groups. Items without tags appear under Ungrouped.

The scope counts in the Summary panel look different from what I selected

Review the controls under Which controls get tested?, and check the objectives you selected above them. Both affect the counts. You can adjust scope on the audit page after creation.

Did this answer your question?