---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create a control test from an engagement

# Create a control test from an engagement {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
After defining a control, audit managers create control tests that run periodically and provide documented evidence of whether the associated control is operating correctly. After creating multiple control tests on an
engagement, use the Control tests grid to view, manage, and request evidence for all tests in one place.

## Before you begin

Role required: sn_audit.admin and sn_audit.manager

Starting with Audit Management 23.x.x, you can store supporting documents in Microsoft Word or PDF formats on evidence, engagement, and control test records. Use the ServiceNow Otto® panel to ask questions or summarize documents. Use voice assist to enable voice chat and audio summaries. For more information, see [Using Document Management System in Audit Workspace](https://www.servicenow.com/docs/8F8z~gYhYxGQqF_~AigbJg "The Document Management System in Audit Workspace provides a centralized repository for storing and managing documents in engagements, control tests, and evidence records. The Documents panel is a native side pane that allows you to store, version, and control access to documents linked to engagements, control tests, and evidence records.").

## Procedure

1. Navigate to AllAuditEngagementsAll Engagements.
2. Open the engagement for the audit task you want to create.  
   Assign audit tasks to engagement in one of the following states:
   * Validate
   * Fieldwork
   * Awaiting approval
   {#t_CreateControlTest__ul_mk2_gjj_mv}
3. In the Audit Tasks Related List, click New.
4. In the Audit Tasks Interceptor, click Control Test.
5. On the form, fill in the fields.  
   {#t_CreateControlTest__table_nht_mjj_mv__entry__2}

   | Field | Description |
   |-|-|
   | Number | Unique identification number. |
   | State | * Open * Work in Progress * Review * Closed Complete * Closed Incomplete * Closed Skipped {#t_CreateControlTest__ul_ccj_nmj_mv} |
   | Parent | Parent audit task. |
   | Control effectiveness | Control effectiveness. |
   | Assigned to | User assigned to this control test. |
   | Issue | Issue related to this control test. |
   | Test plan | Test plan associated with this control test. |
   | Short description | Brief description of the control test. |
   | Schedule ||
   | Planned start date | Intended date the control test should begin. |
   | Planned end date | Intended date the control test should end. |
   | Planned duration | Expected duration of this control test. As with actual duration, the planned duration shows total activity time and takes the control test schedule into consideration. |
   | Actual start date | Date that this control test began. |
   | Actual end date | Date that this control test ended. |
   | Actual duration | Duration of the control test from control test start to control test closure. |
   | Design test ||
   | Design effectiveness | * Effective * Ineffective * None: Default value; to be populated after design testing is complete {#t_CreateControlTest__ul_jtz_m4j_mv} |
   | Design expectations | Basic requirement that should be met by a control so that it is effective. This checks if the control was designed properly to achieve the control objective. |
   | Design assessment procedures | Procedure or steps to be followed to conclude whether the design of the control is effective to achieve the control objective or not. This is based on the design expectation. |
   | Design results | Results of testing the design of the control based on the design assessment procedure. |
   | Operation test ||
   | Operation effectiveness | * Effective * Ineffective * None: Default value; to be populated after design testing is complete {#t_CreateControlTest__ul_jjf_q4j_mv} |
   | Operation expectations | Expectations that should be met to ensure that the control is operating effectively to achieve the control objective. |
   | Operation assessment procedures | Detailed steps, to carry out the operation expectations, which need to be performed to conclude that the control is operating successfully. |
   | Operation results | Results of testing the operation of the control based on the operation assessment procedure. |
   | Activity journal ||
   | Work notes | Comments that are viewable by the audit manager. |
   | Additional comments | Customer-viewable comments. |
   | Confidentiality ||
   | Confidential | 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 confidential option, see [Confidentiality flag for audit and compliance records](https://www.servicenow.com/docs/JTKSBzfaqg9MNO4W44JCEw "You can set the confidentiality flag at the record level for an issue, engagement, observation, control test, activity, interview, and walkthrough records. The users whom you determine to view and update these records are allowed users."). |
   [Table 1. Control test form]

   {#t_CreateControlTest__table_nht_mjj_mv}  
   The control test form captures two types of testing:
   * Design Test: Validates whether the control was designed properly to achieve the control objective. Set Design effectiveness to Effective or Ineffective based on design assessment procedures and results.
   * Operational Test: Validates whether the control is operating effectively in practice. Set Operation effectiveness to Effective or Ineffective based on operational assessment procedures and results.
   {#t_CreateControlTest__ul_cdr_dcj_lkc}Both sections capture expectations, assessment procedures, and results to provide documented evidence of control effectiveness.  
   Note:  
   After you create the control test and assign it to a user, that assigned user can edit the Design results and Operational results fields. Other fields are editable only by users with sn_audit.admin or sn_audit.manager roles.
6. Click Submit.
7. Attach a document with the record in the Document panel.
8. Ask questions about the document in the ServiceNow Otto® panel.
9. Use voice assist to navigate documents with voice commands and receive audio summaries.

## Result

After creating the control test, you can:

* View in grid: Use the Control tests tab on the engagement record to view all control tests in a single grid without opening individual records. For information, see [View control tests in a grid on an engagement](https://www.servicenow.com/docs/owkKfhBvUFJlD4gxMhCEjw "Use the Control tests tab on an engagement record to view, manage, and request evidence for all control tests in a single grid.").
* Request evidence: Select Request evidence directly from the grid to collect evidence from the assigned auditor.
* Personalize columns: Show or hide additional columns such as Reference and Implementation Statement through column personalization settings.
* Use Hierarchical view: Switch to Hierarchical view for a tree-structured layout of control tests and related audit tasks.
{#t_CreateControlTest__ul_f4y_kcj_lkc}

## What to do next

Beginning with 23.x.x release, the control test form also has a Documents panel in
addition to the Attachments panel. You can add, version, and manage permissions on documents
while the control test is not in a Closed Complete, Closed Incomplete, or Closed Skipped
state. For more information, see [Using Document Management System in Audit Workspace](https://www.servicenow.com/docs/8F8z~gYhYxGQqF_~AigbJg "The Document Management System in Audit Workspace provides a centralized repository for storing and managing documents in engagements, control tests, and evidence records. The Documents panel is a native side pane that allows you to store, version, and control access to documents linked to engagements, control tests, and evidence records.").
* **[Automatically generate control tests from an engagement](https://www.servicenow.com/docs/6j~FJHDEH1fd8vEMynSHDg)**   
  After adding an entity to an engagement, you can automatically generate control tests.

*[\>]: and then