Skip to main content

Audit workspace overview

How audit workspaces are structured, what they contain, and how users navigate the audit lifecycle inside AssureGrid.

Purpose

An audit workspace is the main operating space for a specific audit engagement in AssureGrid. It brings together the audit context, planning outputs, walkthrough activities, refinements, evidence, execution workpapers, issues, and reporting into one connected workflow. Instead of managing these stages in separate tools, the workspace keeps them organized inside one lifecycle.

What This Page Covers

This guide explains:

  • what an audit workspace is

  • what users can see in the workspace list

  • how workspace stages are organized

  • how users move into a specific workspace

  • how the lifecycle tabs are structured

What an Audit Workspace Represents

A workspace typically represents one audit engagement or one active audit stream. It provides the structure needed to manage:

  • audit scope

  • team assignment

  • audit memo context

  • planning outputs

  • walkthrough and refinement work

  • evidence collection

  • workpaper review

  • issue management

  • final report generation

Each workspace is designed to maintain continuity across the audit lifecycle.

Where Audit Workspaces Fit in the Platform

Audit workspaces are usually used after initial setup is complete, including:

  • user access

  • organization onboarding

  • team setup

  • control inventory work where relevant

Once a workspace is created, it becomes the primary place where the audit lifecycle is executed.

Workspace Overview List

The Audit Workspaces page usually shows a list of all workspaces available to the user. This list helps users:

  • find active audits

  • review stage progress

  • identify assigned teams

  • understand current status at a glance

  • open an existing workspace

Typical Information Shown in the Workspace List

Depending on the view, the workspace list may include the following fields:

FieldDescription
Workspace NameUnique name identifying the audit engagement.
Audit TopicSubject or scope of the audit.
Entity or RegionOrganizational unit or geographic region under audit.
FrameworkApplicable compliance or control framework.
StageCurrent lifecycle stage of the workspace.
TeamAssigned team members or audit ownership.
Start DateDate the workspace became active.
Anticipated End DateTarget completion date for the engagement.
Progress IndicatorVisual indicator of overall stage completion.
ActionsQuick actions available for the workspace row.

This information gives users a quick operational view of ongoing audit work.

Workspace Stages

Each workspace follows a lifecycle made up of multiple modules. These stages appear as lifecycle tabs inside the workspace and help users move through the audit in a controlled order. The following table summarizes the typical stages and their purpose:

StagePurpose
OverviewWorkspace summary, audit context, team assignment, and current stage status.
Audit PlanningRCM review, test steps, evidence list, and walkthrough question generation.
Walkthrough Preparation & SchedulingWalkthrough coordination, scheduling, and preparation of walkthrough materials.
Data RefinementsReview and approval of AI-generated suggestions against original data.
Evidence ManagementUpload, organize, and manage evidence files linked to controls.
Audit ExecutionWorkpaper review, testing documentation, and sign-off.
Issue ManagementIssue identification, tracking, and resolution workflow.
Audit Report GenerationDraft and finalize the formal audit report for distribution.

Stage-Based Workflow

The workspace is not just a container for files or notes. It is an operational workflow. That means:

  • each stage has a specific purpose

  • outputs from one stage feed into the next

  • attestations can unlock the next stage

  • users should complete each stage before progressing

Opening an Existing Workspace

To enter a workspace, follow the steps below:

  1. Open Audit Workspaces from the main navigation.

  2. Locate the desired workspace in the list.

  3. Click the workspace row or workspace name.

Expected Outcome

The selected workspace opens and displays either the workspace overview dashboard, or the last relevant stage depending on the implementation.

Search and Filtering

The workspace overview list may include tools such as search, filter, stage selection, and sorting. These tools help users find a specific audit workspace more quickly, especially when there are multiple audits in progress.

What Users Typically Do First Inside a Workspace

Once a workspace is opened, users typically:

  • review the Overview tab

  • confirm the audit context

  • check team or ownership details

  • understand current stage and progress

  • move into the next required stage, such as Audit Planning

Why Workspace Structure Matters

The workspace structure is important because it gives each audit:

  • a defined operational context

  • traceable stage progression

  • linked outputs across modules

  • centralized review and attestation history

  • one place to manage the audit lifecycle end to end

Best Practices

  • Use clear naming conventions for workspaces.

  • Review stage status before opening downstream modules.

  • Confirm the correct team or audit engagement before beginning work.

  • Use the overview list regularly to monitor in-progress audits.

  • Avoid treating workspaces as just folders — they are workflow containers.

Common Misunderstandings

A workspace is not just a project shell

It is the structured environment where the audit lifecycle actually runs.

Opening a workspace does not mean all stages are ready

Some stages depend on prior completion or attestation.

Workspace list and workspace detail are different

The workspace list is the portfolio view. The workspace detail is the engagement work area.

Important Always confirm the correct workspace is selected before beginning any stage work. Each workspace maintains its own independent lifecycle, data, and audit context. Working in the wrong workspace may result in outputs being saved to the incorrect engagement.