> 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/monitors/workflow-check-resolution/how-to-configure-and-resolve-sprinto-workflow-check-for-internal-audit-reviewed-by-management.md).
# How to Configure and Resolve Sprinto Workflow Check for Internal Audit Reviewed by Management
Periodic management review of internal audit findings ensures that leadership is aware of the organisation’s compliance posture, key observations, and corrective actions. This process validates that audit results are acted upon and that management remains accountable for maintaining continuous compliance.
Sprinto’s **Internal Audit Reviewed by Management** workflow check helps document and verify that management has formally reviewed the results of internal audits. The evidence uploaded against this check supports multiple frameworks, including **ISO 27001**, **SOC 2**, and **GDPR**.
***
### Before You Begin
Ensure that you:
* Have **Administrator access** to your Sprinto account.
* Have access to **internal audit reports** and **meeting records** where management reviewed audit findings.
* Know your organisation’s **audit review frequency** (e.g., annual, semi-annual).
***
### Configuring the Workflow Check
1. Log in to your **Sprinto** account as an Administrator.
2. Navigate to **Data Library → Workflow Checks**.
3. Click **Create Check → Add from Template**.
4. Locate **Internal Audit is reviewed by management** and click **Enable**.
5. On the **Add Workflow Check** page, click **Edit** to:
* Set the appropriate **frequency** (default: every 12 months).
* Assign the responsible person and, if needed, a reviewer.
6. Click **Add Check**.
Once added, the check status will appear as *Due* or *Failing* until evidence is uploaded.
***
### Resolving the Check
Here's a short video on how to resolve this workflow check.
{% embed url="" %}
1. Log in to the **Sprinto Admin Portal**.
2. Go to **Data Library → Workflow Checks**.
3. Select **Internal Audit Reviewed by Management**.
4. Click **Upload Evidence**.
5. Enter the **Evidence Record Date**, then attach relevant documentation:
* **File Upload:** Upload meeting minutes, presentation decks, or review summaries.
* **Link Upload:** Add a secure link to a shared folder or document repository (e.g., Google Drive, Confluence).
6. Click **Save**.
Once verified, Sprinto will update the check to *Passing*.
***
### Evidence Requirements
You can provide one or more of the following as valid proof:
* Management review meeting minutes.
* Audit summary reports signed off by leadership.
* Action plan or management response document.
* Screenshots or approval logs showing formal acknowledgment.
***
### Frequency
The default frequency for this check is **annual**. However, you can configure it to align with your internal audit cycle (e.g., **quarterly** or **semi-annually**).
***
### Notes
* Management review is a mandatory step for closing the internal audit loop.
* Ensure all actions discussed during the review are tracked for resolution before the next audit cycle.
***
### Need Help?
If you need assistance with setting up or resolving this workflow check, contact **Sprinto Support** at .
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sprinto.com/monitors/workflow-check-resolution/how-to-configure-and-resolve-sprinto-workflow-check-for-internal-audit-reviewed-by-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
