> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/audits/dashboard-actions/create-a-custom-audit-with-a-lign.md).
# Create a Custom Audit with A-LIGN
If you work with A-LIGN as your external auditor, you can create a custom audit in Sprinto using an existing A-LIGN engagement. Sprinto automatically imports the requests from the selected engagement as audit requirements, allowing you to collect evidence in Sprinto while keeping it synced with A-LIGN.
### Before you begin
Before creating an A-LIGN audit, ensure that:
* You have integrated A-LIGN with your Sprinto account. For setup instructions, see the [A-LIGN Integration](/integrations/overview/a-lign-integration.md) Doc.
* You have an active A-LIGN engagement.
* You have the required permissions to access the A-LIGN engagement.
### Create a custom audit with A-LIGN
1. Log in to your Sprinto account.
2. Go to **Audits**.
3. Click **Plan new audit**.
4. Select **Custom audit**.
5. Enter an **Audit name**.
6. Select the **Audit type**:
* **External**
* **Internal**
7. Configure the **Evidence collection** period:
* Select a **Start date**.
* Choose one of the following collection periods:
* **12 months**
* **6 months**
* **3 months**
* **Custom**, and specify an end date.
8. Under **A-LIGN engagement**, select the engagement you want to use for the audit.
9. If required, enable or disable **Auto-schedule next audit**.
10. Click **Start audit**.
Sprinto creates the audit and automatically imports the requests from the selected A-LIGN engagement as audit requirements.
{% hint style="info" %}
#### Note
The **A-LIGN engagement** section is available only after you integrate A-LIGN with your Sprinto account.
{% endhint %}
### Verify the synced audit requirements
After the audit is created, Sprinto syncs the requirements from the selected A-LIGN engagement automatically.
1. Go to **Audits** and open the newly created audit.
2. On the **Summary** tab, review the audit details, including:
* Audit name
* Audit type
* Evidence collection period
* Number of synced requirements
3. Select the **Evidence** tab to view the imported audit requirements.
Sprinto automatically creates audit requirements from the requests available in the selected A-LIGN engagement. You can now begin collecting and attaching evidence for each requirement.
{% hint style="info" %}
#### Note
* Requirements are automatically imported from the selected A-LIGN engagement during audit creation.
* Any evidence you attach to a requirement in Sprinto is automatically synced to the corresponding request in A-LIGN.
* The request IDs displayed in Sprinto correspond to the request identifiers in the selected A-LIGN engagement, making it easier to reference the same request across both platforms.
{% endhint %}
### What happens next?
After the evidence collection period ends, you can:
* Assign an auditor to the audit.
* Share the audit dashboard with the auditor.
* Collaborate with the auditor throughout the review process.
* Complete the audit after all review activities are finished.
For more information, see [**Understand Audit Milestones**](/audits/dashboard-actions/create-an-audit-plans-3-and-4.md#understand-audit-milestones)**.**
---
# 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://docs.sprinto.com/audits/dashboard-actions/create-a-custom-audit-with-a-lign.md?ask=&goal=
```
`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.