Manage engagements

The audit engagement process involves creating, planning, scoping, and conducting engagements as well as reporting on engagement findings.

Engagement process

The base system audit engagement process includes steps for scoping, validating, conducting, and approving engagement results. It also contains steps for following up on open audit tasks and issues, and finally closing out the audit engagement.

Table 1. States of the engagement process

State	Description
Scope	During the Scope state, audit managers define which entities are involved in the audit engagement. For example, for a financial audit, one may include all business services that the finance department relies on and the finance department itself. See Add entities to an engagement scope.
Validate	After an engagement has moved to the Validate state, all the risks, controls, and test plans associated with the entities in the engagement's scope will be associated with the audit. Indicator results that were collected during the audit period of the engagement will also be associated with the audit. Audit managers can review the risks, controls, test plans, and indicator results, and update the scope of the engagement, if necessary. Audit managers can also begin creating and planning audit tasks for the engagement. To move an engagement into the Validate state, click Validate on any engagement currently in the Scope state.
Fieldwork	Auditors complete their assigned audit tasks during the Fieldwork state. These tasks include control testing, interviews, walkthroughs, and other activities. Issues that are found during control testing are associated with the engagement. Auditors can also create general issues associated with the engagement. Audit managers can create additional audit tasks as needed. When the audit is done, audit managers specify the result of the engagement, whether it's satisfactory, adequate or inadequate, and provide details on their opinion. To move an engagement into the Fieldwork state, click Advance to Fieldwork on any engagement currently in the Validate state. See Audit task management.
Awaiting Approval	During the "Awaiting Approval" state, the approvers specified in the Approvers field of the engagement review the results of the audit tasks conducted and the issues that were created. After reviewing the results of the engagements, approvers approve or reject the engagement. To move an engagement into the Awaiting Approval state, click Request approval on any engagement currently in the Fieldwork state. See Approve or reject an engagement.
Follow Up	After an engagement has been approved, if there are any remaining open tasks, issues or milestones, in case of GRC Advanced Audit, associated with the engagement, the engagement automatically goes into the Follow Up state. During this stage, auditors must close out all remaining issues, tasks, and milestones before the engagement are marked as complete.
Closed	Engagements move into the "Closed" state under one of three conditions: The engagement is closed as incomplete during the Scope, Validate, or Fieldwork states. There are no open audit tasks, issues, and milestones after the engagement is approved. In this case, the engagement automatically moves from the Awaiting Approval state to the Closed state. All follow-up tasks, issues, and milestones are closed out. In this case, the engagement automatically moves from the Follow Up state to the Closed state.

• Audit task management
  Audit tasks are completed throughout an engagement and provide documented evidence that the organization is complying with external regulations and internal policies.
• Create an engagement
  Audit managers create engagements to manage audit information and collect entities, controls, and control tests that are relevant to the audit.
• Generate an audit report from an engagement
  Generate an audit report and maintain different versions of audit reports from an engagement in Follow up state.
• Create an engagement from a previous engagement
  Audit managers can create engagements from previous engagements to reduce the need to redefine the scope, auditors, and approvers for similar engagements that are conducted throughout the year.
• Create a control test from an engagement
  After defining a control, audit managers create control tests that run periodically and provide documented evidence of whether the associated control is operating correctly.
• Create an audit task activity
  After defining a control, audit managers create activities that explore and provide documented evidence of whether the associated control is operating correctly.
• Create an interview
  After defining a control, audit managers create interviews with control owners to discuss and provide documented evidence of whether the associated control is operating correctly.
• Create a walkthrough
  After defining a control, audit managers create walk throughs that will be conducted to observe and provide documented evidence of whether the associated control is operating correctly.
• Generate a KB article from an engagement
  Audit managers can generate a KB article that summarizes the findings of an engagement so report findings can be communicated to executives.
• Approve or reject an engagement
  Audit users that are assigned as approvers for an engagement can approve or reject engagements in the Awaiting Approval state.
• Add entities to an engagement scope
  Audit managers can define which entities are involved in the audit engagement. When you add an entity to an engagement, the corresponding risks, controls, test plans, and indicator results of the entity are also added to the engagement.
• Manage Audit Engagements
  The Engagement Workbench provides a timeline view from which you can select an audit engagement to view details or create a new engagement.