> 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/data-library/vulnerabilities/dashboard-actions/run-and-monitor-workflow-checks.md).

# Run and Monitor Workflow Checks

Workflow checks in Sprinto ensure that critical vulnerability-related activities—such as code scans, network reviews, or external audits—are completed and documented on time. Once a workflow check is due, the assigned stakeholder must run the check by submitting evidence that confirms the action was completed.

Sprinto then updates the check’s status and logs it for compliance verification.

***

### Before You Begin

Make sure:

* The workflow check is already created and active (see: [Create and Manage Workflow Checks](https://chatgpt.com/g/g-p-682c1aeced3481919aef33cebb2d490f-sprinto-documentation-overhaul/c/686e0f92-5a1c-8006-b421-407af2e29ff7#)).
* You are assigned as the responsible stakeholder or have administrator access.
* You have the required evidence ready (e.g. screenshot, scan report, mail confirmation).

***

### Procedure

#### 1. Navigate to the Workflow Check

1. Log in to the Sprinto dashboard.
2. Go to **Data Library > Vulnerabilities > Workflow Checks**.
3. Locate the check under the **Due**, **Critical**, or **Failing** tab.

{% hint style="info" %}
Use filters to search by status, assignee, or due date if needed.
{% endhint %}

4. Click the workflow check you want to run.

***

#### 2. Upload Evidence

1. Click **Upload Evidence**.
2. Choose the evidence submission type:
   * **File**: Upload a screenshot, scan report, or document from your device.
   * **Link**: Paste a shareable link (e.g. internal documentation or audit logs).
3. Select the **Evidence record date** (the date the check was performed).
4. Click **Finish**.

{% hint style="info" %}
Ensure the file format is supported and evidence clearly reflects completion of the check.
{% endhint %}

***

#### 3. Monitor Workflow Check Status

* Once submitted, the workflow check status changes to **Passing**.
* If evidence is missing or incorrectly formatted, the check may remain in *Due* or *Failing* status.
* You can revisit any check to update or re-upload evidence before the expiry date.

***

### Status Definitions

<table><thead><tr><th width="161.5703125">Status</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Due</strong></td><td>Check is open and awaiting evidence submission</td></tr><tr><td><strong>Critical</strong></td><td>Less than 7 days remain before SLA deadline</td></tr><tr><td><strong>Failing</strong></td><td>Due date has passed without submission</td></tr><tr><td><strong>Passing</strong></td><td>Valid evidence was submitted and check has been marked as complete</td></tr></tbody></table>


---

# 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:

```
GET https://docs.sprinto.com/data-library/vulnerabilities/dashboard-actions/run-and-monitor-workflow-checks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
