> 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/frequently-asked-questions.md). # Frequently Asked Questions Find answers to common questions about creating, managing, and completing audits in Sprinto. *** #### 1. What types of audits can I create in Sprinto? Sprinto supports two types of audits: * **Partner audit** – Pre-configured audits based on compliance frameworks (e.g. SOC 2, ISO 27001). These are typically used by organisations on Plan 1 and Plan 2. * **Custom audit** – Fully configurable audits where you define your own requirements. Available for Plan 3 and Plan 4 users. *** #### 2. How do I know which audit creation flow applies to me? The flow depends on your Sprinto plan: * **Plan 1 & 2:** You’ll see a simplified Partner audit setup without an audit type selection. * **Plan 3 & 4:** You’ll see a forking drawer with the option to choose either a Partner or Custom audit. *** #### 3. Can I change the audit type or framework after the audit is created? No. Both **audit type** and **framework** become locked once the audit is created. *** #### 4. Can I edit the evidence collection period after creating the audit? Yes, but only if the audit has not been shared with the auditor. Once shared, the start and end dates become non-editable. *** #### 5. Can I remove a requirement after it is added? Yes, but the method depends on how the requirement was added: * **CSV upload** – Remove the file from the Requirements tab. * **Framework criteria** – Use the delete icon in the edit screen. * **Controls** – Deselect the control and update the audit. Requirements cannot be removed once they are marked **Audit Complete**. *** #### 6. Can I add more requirements after audit creation? Yes. You can return to the **Requirements** tab and select **Add** to include new requirements using any of the available methods. *** #### 7. What actions become restricted after an audit is shared? Once the audit is shared with an auditor: * You can no longer change the auditor or evidence collection dates. * You cannot remove or modify requirements marked **Ready for audit** or higher. * Evidence uploads are locked once requirements are audited. *** #### 8. Can I share the audit multiple times? No. You can only share the audit once. However, you can update the evidence or task owners before sharing, and the auditor will see the latest state. *** #### 9. How do I track audit progress? Use the **Audit Dashboard** to view milestones, and the **Requirements** tab to check the status of each requirement (e.g. Collecting Evidence, Internal Review, Ready for Audit). *** #### 10. Can my auditor make changes in Sprinto? No. Auditors receive a read-only view of the audit. They can leave comments (if enabled), but cannot make edits. *** #### 11. What is an A-LIGN engagement? An A-LIGN engagement is the audit project created in A-LIGN. Sprinto uses the selected engagement to import audit requests as requirements. *** #### 12. What happens if I do not select an A-LIGN engagement? Sprinto cannot sync requests from A-LIGN. To create an audit with automatic requirement syncing, you must select an A-LIGN engagement. *** #### 13. Can I add evidence in Sprinto? *** Yes. Attach evidence to the imported requirements in Sprinto. The evidence is automatically synced to the corresponding request in A-LIGN. *** #### 14. Will updates in A-LIGN automatically create new requirements in Sprinto? Sprinto imports the requests available in the selected engagement when the audit is created. Subsequent syncing behaviour depends on the integration capabilities available for your organisation. --- # 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/frequently-asked-questions.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.