# Workflow Check Resolution

Workflow checks in Sprinto validate whether specific operational and security requirements are being met within your organisation. These checks can be mapped to internal processes, compliance mandates, or system-level configurations.

Sprinto allows you to resolve failed or pending workflow checks by taking corrective action, submitting evidence, or marking them as exceptions. This article outlines how to review and resolve these checks effectively using the Monitoring dashboard.

***

### What is a Workflow Check

A **workflow check** is an automated or manual validation tied to your organisation’s policies and control objectives. Each check appears in the **Monitoring** tab and tracks whether a control is:

* **Passing** – Configured and compliant
* **Failing** – Misconfigured, missing, or non-compliant
* **Pending Evidence** – Awaiting document upload or manual validation
* **Excluded** – Marked as out-of-scope or exception-approved

Workflow checks can originate from:

* Integrated systems (e.g., AWS, Google Workspace, GitHub)
* Manual policy enforcement (e.g., password policy, change management)
* Evidence uploads (e.g., audit reports, screenshots)

***

### How to Resolve a Workflow Check

1. **Navigate to Monitoring > Check History**
2. Filter by status (e.g., Failing, Pending Evidence)
3. Click a failing check to open the details pane

#### A. If the Check is Automated

* Review the platform integration status
* Click **View Monitor Details** to see:
  * Detected misconfiguration
  * Last sync time
  * Platform remediation guidance
* Fix the issue in your source system (e.g., enable encryption in AWS)
* Click **Revalidate** to update the check status

#### B. If the Check Requires Evidence

* Click **Upload Evidence**
* Attach relevant files (PDFs, screenshots, audit exports)
* Add a comment for reviewer context (e.g., “Enforced via Conditional Access policy”)
* Click **Mark as Resolved**

#### C. If the Check is Out of Scope or Temporarily Skipped

* Click **Exclude from Scope**
* Provide a justification (e.g., “Legacy system being decommissioned”)
* Optionally set a review date for re-evaluation

***

### Review Workflow for Admins & Auditors

<table><thead><tr><th width="92.4140625">Role</th><th width="510.72265625">Permissions</th></tr></thead><tbody><tr><td>Admin</td><td>Can resolve, upload evidence, exclude, revalidate</td></tr><tr><td>Auditor</td><td>Can review evidence, leave comments, request more information</td></tr></tbody></table>

After evidence is uploaded, auditors can mark the check as **Reviewed** or change the status to **Needs More Info**.

***

### Best Practices

* Review failing and pending checks **weekly**
* Maintain a repository of **evidence templates** (e.g., screenshots, exports)
* Use **comments** for context on partial compliance or alternate controls
* Tag internal reviewers using the **@mention** feature in Sprinto (if enabled)