Create a control test from an engagement in Audit Workspace

---
title: Create a control test from an engagement in Audit Workspace
description: Create a control test that runs periodically and provides documented evidence of whether the associated control is operating correctly or not.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/governance-risk-compliance/audit-management/create-control-test-engagement-ws.html
release: brazil
product: Audit Management
classification: audit-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
breadcrumb: [Audit Task Management, Audit Supervisor Workspace, Audit Workspace overview, Audit Management, Governance, Risk, and Compliance]
---

# Create a control test from an engagement in Audit Workspace

Create a control test that runs periodically and provides documented evidence of whether the associated control is operating correctly or not.

## Before you begin

Role required: sn\_audit.manager, sn\_audit\_ws.supervisor

## Procedure

1.  Navigate to **All** > **Audit** > **Audit Workspace**.

2.  Select the lists icon \(\[Omitted image "ListsIcon.jpg"\] Alt text: List icon.\).

3.  Select **All engagements** or **My engagements** in the Execution list.

    Assign an audit task to an engagement that is in one of the following states:

    -   Validate
    -   Fieldwork
4.  Select the link to the engagement record in the **Name** column.

    The engagement record details open in the **Overview** tab.

5.  Select the Audit tasks related list.

6.  Click the grouped button below the related lists and select **New control test** from the list.

7.  On the form, fill in the fields.

<table id="table_m54_5g2_mqb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Number

</td><td>

Unique identification number.

</td></tr><tr><td>

Name

</td><td>

Name of the control test.

</td></tr><tr><td>

Parent

</td><td>

Parent engagement.

</td></tr><tr><td>

Test plan

</td><td>

Test plan associated with this control test.

</td></tr><tr><td>

State

</td><td>

State of the control test. The default state is **Open**.

</td></tr><tr><td>

Control effectiveness

</td><td>

Control effectiveness.

</td></tr><tr><td>

Issue

</td><td>

Issue related to this control test.

</td></tr><tr><td class="sub-head" colspan="2">

Assignment

</td></tr><tr><td>

Assigned to

</td><td>

User assigned to the control test.

</td></tr><tr><td class="sub-head" colspan="2">

Schedule

</td></tr><tr><td>

Planned start date

</td><td>

Intended start date of the control test.

</td></tr><tr><td>

Planned end date

</td><td>

Intended end date of the control test.

</td></tr><tr><td>

Planned duration

</td><td>

Expected duration of the control test. As with actual duration, the planned duration shows total activity time and takes the control test schedule into consideration.

</td></tr><tr><td>

Actual start date

</td><td>

Actual start date of the control test.

</td></tr><tr><td>

Actual end date

</td><td>

Actual end date of the control test.

</td></tr><tr><td>

Actual duration

</td><td>

Duration of the control test from control test start to control test closure.

</td></tr><tr><td class="sub-head" colspan="2">

Design test

</td></tr><tr><td>

Design effectiveness

</td><td>

-   None
-   Effective
-   Ineffective


</td></tr><tr><td>

Design expectations

</td><td>

Basic requirement that should be met for a control to be effective. This field checks if the control was designed properly to achieve the control objective.

</td></tr><tr><td>

Design assessment procedures

</td><td>

Procedure or steps to be followed to conclude whether the design of the control is effective to achieve the control objective or not. This procedure is based on the design expectation.

</td></tr><tr><td>

Design results

</td><td>

Results of testing the design of the control based on the design assessment procedure.

</td></tr><tr><td class="sub-head" colspan="2">

Operational test

</td></tr><tr><td>

Operating effectiveness

</td><td>

-   None
-   Effective
-   Ineffective


</td></tr><tr><td>

Operational expectations

</td><td>

Expectations that should be met to ensure that the control is operating effectively to achieve the control objective.

</td></tr><tr><td>

Operational assessment procedures

</td><td>

Detailed steps, to carry out the operational expectations, which must be performed to conclude that the control is operating successfully.

</td></tr><tr><td>

Operational results

</td><td>

Results of testing the operation of the control based on the operation assessment procedure.

</td></tr><tr><td class="sub-head" colspan="2">

Activity

</td></tr><tr><td>

Work notes \(Private\)

</td><td>

Comments that the audit manager and audit supervisor can only view.

</td></tr><tr><td>

Additional comments

</td><td>

Comments that customers can also view.

</td></tr><tr><td class="sub-head" colspan="2">

Confidentiality

</td></tr><tr><td>

Confidential

</td><td>

Option to enable confidentiality of the record. Only the assigned confidential users or confidential groups of users can access the record.For more information on the confidential option, see [Confidentiality flag for audit and compliance records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/governance-risk-compliance/audit-management/confidentiality-flag-audit-pc.md).

</td></tr></tbody>
</table>8.  Select **Save**.

    You can view the description and monitor the state of the control test in the **State** banner of the Overview page. The state updates as the record progresses through the control test process flows.

9.  To record individual assessment procedures for this control test, select the **Test steps** related list, then select **New**.

    Fill in **Identifier**, **Assessment objective**, and **Objective effectiveness** for each test step.