> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/creating-and-managing-audit-programs.md).

# Creating & Managing Audit Programs

Perform tasks assigned to your role to advance requests through the Audit Program Management workflow.

## Workflow Overview

The **Audit Program Management** workflow governs the creation, review, and approval of audit programs before they are prepared for execution.

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FQbFJMQwNNCiQd1cEA8vc%2FAUD-V112-Workflow-3.png?alt=media&amp;token=93d4a486-b7f6-46b8-b7ab-cb9efed61c99" alt="" width="563"><figcaption></figcaption></figure>

***

## Interactive Tour

Explore the **Audit Program Management** workflow and learn how each stage works, with key guidance and best practices along the way.

{% @howdygo/embed url="<https://app.howdygo.com/share/ce8ff24e-3210-4fdd-b999-53b081404f81>" %}

***

## Workflow Stages

The workflow is organized into **three key stages**, each with specific roles and responsibilities.

{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}

{% stepper %}
{% step %}

### Create Audit Program

> **Performed By:** Program Creator (e.g., Audit Associate, Auditor, Lead Auditor)

**Responsibilities:**

* Identify the need for an audit based on compliance requirements, risk considerations, or organizational priorities.
* Provide the necessary details (e.g., audit parameters, organizational context).
* Assign the team responsible for conducting the audit.
* Assign requirements to be evaluated during the audit.
* Submit the program to initiate the workflow.

<p align="center"><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/creating-and-managing-audit-programs/define-audit.md" class="button primary" data-icon="copy">Create Audit Program</a></p>

***

{% endstep %}

{% step %}

### Review Audit Program

> **Performed By:** Assigned Team Leader (e.g., Audit Lead, Audit Supervisor, Engagement Lead)

**Responsibilities:**

* Review the audit program for completeness, clarity, and internal consistency.
* Evaluate whether the audit is aligned with organizational context, supported by appropriate requirements, and ready for execution.
* Provide feedback to the creator if revisions are needed.
* Approve the program or return it for modification.

***

{% endstep %}

{% step %}

### Modify Audit Program

> **Performed By:** Program Creator (e.g., Audit Associate, Auditor, Lead Auditor)

**Responsibilities:**

* Review feedback from the assigned reviewer.
* Make necessary revisions (e.g., update audit parameters, organizational context, team assignments, requirements).
* Resubmit the program for further review.

***

{% endstep %}
{% endstepper %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/creating-and-managing-audit-programs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
