> 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/workflow-checks/glossary.md).

# Glossary

This glossary explains terms you may encounter when working with Workflow Checks in Sprinto.

<table><thead><tr><th width="137.9375">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Workflow Check</strong></td><td>A time-driven compliance task that requires evidence submission at scheduled intervals.</td></tr><tr><td><strong>Automated Check</strong></td><td>A system-driven compliance check that runs continuously against integrated services without manual intervention.</td></tr><tr><td><strong>Active Check</strong></td><td>A Workflow Check that is currently enabled and will trigger according to its defined schedule.</td></tr><tr><td><strong>Due</strong></td><td>A status indicating that a Workflow Check is ready to be completed.</td></tr><tr><td><strong>Critical</strong></td><td>A status indicating that a Workflow Check deadline is approaching and immediate action is required.</td></tr><tr><td><strong>Failing</strong></td><td>A status indicating that a Workflow Check has not been completed within the defined timeframe.</td></tr><tr><td><strong>Passing</strong></td><td>A status indicating that a Workflow Check has been successfully completed, with evidence approved or marked as a special case.</td></tr><tr><td><strong>Special Case</strong></td><td>A resolution type for checks that are irrelevant or cannot be completed. The check is marked as “Passing” but categorised separately for audit purposes.</td></tr><tr><td><strong>Evidence</strong></td><td>Documentation submitted to prove that the requirements of a Workflow Check have been met (for example, reports, screenshots, or policy updates).</td></tr><tr><td><strong>Reviewer</strong></td><td>A user assigned to validate evidence for a Workflow Check. Reviewers can approve, reject, or mark submissions as special cases.</td></tr><tr><td><strong>Owner</strong></td><td>The user responsible for completing and submitting evidence for a Workflow Check.</td></tr><tr><td><strong>Frequency</strong></td><td>The interval at which a Workflow Check is scheduled to run (for example, monthly, quarterly, or annually).</td></tr><tr><td><strong>Zones</strong></td><td>Custom segments in Sprinto to which Workflow Checks can be mapped, usually reflecting organisational structures such as departments or regions.</td></tr><tr><td><strong>Custom Fields</strong></td><td>Organisation-specific metadata that can be added to Workflow Checks to capture additional details.</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/workflow-checks/glossary.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.