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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create Audit Engagement

# Create an engagement {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Audit managers create engagements to manage audit information and collect entities,
controls, and control tests that are relevant to the audit.

## Antes de Iniciar

Role required: sn_audit.admin or sn_audit.manager  
Nota:  
For more information on engagements, see [Manage engagements](https://www.servicenow.com/docs/J74mesAegYMLo5jcCWiaNA "The audit engagement process involves creating, planning, scoping, and conducting engagements as well as reporting on engagement findings.").

## Por Que e Quando Desempenhar Esta Tarefa

To know more about how to define a control and control objective, see:

* [Create a control](https://www.servicenow.com/docs/olRZxn3gXXvNu8hBplaimg "Controls are automatically generated when you associate a policy with an entity type or an entity type with a control objective. A control is created for each entity listed in the entity type for the control objective. Controls can also be manually created.")
* [Create a control objective](https://www.servicenow.com/docs/287wQlzQmbQeaxyWnxO3IA "A control objective is an objective, direction, or standard that acts as guidance for company interactions and operations. Control objectives can be categorized, classified, and related to policies.")
{#t_CreateEngagement__ul_qg5_qjj_31c}

## Procedimento

1. Navigate to AllAuditEngagementsCreate New.
2. On the form, fill in the fields.  
   {#t_CreateEngagement__table_nht_mjj_mv__entry__2}

   | Field | Description |
   |-|-|
   | Number | A unique identification number. |
   | State | * Scope * Validate and plan * Fieldwork * Awaiting approval * Follow up * Closed {#t_CreateEngagement__ul_ccj_nmj_mv} |
   | Name | Name of the engagement. |
   | Type | Type of engagement. The choices are: * None * Internal Audit * External Audit * SOX Audit * IT Audit * Financial Audit * Compliance Audit * Certification Audit * Regulatory Audit * Operational Audit * Continuous Audit * Vendor Audit * Customer Audit * Store Audit * Quality Audit * Project Audit {#t_CreateEngagement__ul_szv_hyc_1nb} |
   | Percent complete | Number that represents the percentage of the engagement that has been completed. |
   | Assigned to | User assigned to the engagement. |
   | Auditors | Auditors were assigned to the engagement. |
   | Approvers | Approvers assigned to the engagement. |
   | Description | General description of the engagement. |
   | Objectives | Stated objectives of the engagement. |
   | Schedule ||
   | Engagement planned start | Estimated start date of the engagement. |
   | Engagement starts | Choice to automatically determine the start date of the engagement. The choices are: * Scope * Validate * Fieldwork {#t_CreateEngagement__ul_ggb_552_wmb} |
   | Engagement actually start | Actual date the engagement begins. |
   | Engagement planned end | Estimated end date of the engagement. |
   | Engagement ends | Choice to automatically determine the start date of the engagement. The choices are: * Follow Up * Closed {#t_CreateEngagement__ul_ovz_rx2_wmb} |
   | Engagement actual end | The actual date that the engagement ends. |
   | Fieldwork planned start | Estimated start date of the fieldwork. |
   | Fieldwork planned end | Planned end date that was originally set in the engagement. Nota: This field sets the value as one day plus the planned start date for fieldwork by default. |
   | Fieldwork planned duration | Number of days and hours planned for fieldwork. The duration and planned start date of fieldwork are used to calculate the planned end date. If audit tasks are defined, this field is populated with the longest planned duration from the audit tasks. |
   | Fieldwork actual start | Actual start date of the fieldwork. If audit tasks are defined, this field is populated with the earliest actual start date from the audit tasks. |
   | Fieldwork actual end | Actual end date of the fieldwork. If audit tasks are defined, this field is populated with the latest actual end date from the audit tasks. |
   | Fieldwork actual duration | Duration of fieldwork start date and end date. |
   | Results ||
   | Result | * Satisfactory * Adequate * Inadequate {#t_CreateEngagement__ul_r5c_ctj_mv} |
   | Opinion | Justification for the selected result. |
   | Report ||
   | Knowledge base | Knowledge base to be used. |
   | Report template | Template to be used to generate the knowledge base article reporting the engagement results. |
   | KB article | Recently generated knowledge base article containing the engagement results |
   | Activity ||
   | Additional comments | Customer-viewable comments. |
   | Work notes | Comments that are viewable by the admin audit manager. |
   | Confidentiality ||
   | Confidential | Option to enable confidentiality of the record. Only the assigned users or groups of users can access the record. For more information on the confidential option, see [Confidentiality flag for audit and compliance records](https://www.servicenow.com/docs/ncVXgj5ik9zpuw_B6QD6dQ "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."). |
   [Tabela 1. Engagement form]

   {#t_CreateEngagement__table_nht_mjj_mv}
3. Select Submit.
{#t_CreateEngagement__steps_zt4_dkj_mv}