For the complete documentation index, see llms.txt. This page is also available as Markdown.

How Workflow Checks Work

Understand how Workflow Checks are configured, activated, and resolved in Sprinto to maintain compliance and audit readiness.

Workflow Checks in Sprinto operate in two main stages: Configuration and Resolution. This process ensures that compliance activities are scheduled, evidence is collected, and results are tracked against audit requirements.

Stage 1: Configuring Workflow Checks

You can configure Workflow Checks in several ways:

  • Dedicated Workflow Checks tab – navigate to Data Library → Workflow Checks to create and manage checks.

  • Preconfigured checks – some checks are automatically enabled when you activate compliance frameworks in Sprinto.

  • Manual configuration – create new checks by selecting from templates, adding single checks, or bulk uploading via CSV.

When configuring a Workflow Check, you can define:

  • Title and description – identify the purpose and scope of the check.

  • Instructions – specify how evidence should be gathered or presented.

  • Frequency and triggers – define how often the check runs (e.g., monthly, quarterly, annually).

  • Assignment – designate an owner responsible for completing the check and, if required, add a reviewer for evidence validation.

  • Custom fields and zones – capture organisation-specific details and map checks to relevant zones.

Stage 2: Resolving Workflow Checks

Once configured, Workflow Checks activate according to their schedule. They are displayed with statuses such as:

  • Due – the check is awaiting completion.

  • Critical – the check is nearing its deadline.

  • Failing – the check has not been completed within the defined timeframe.

Users can resolve active checks by:

  • Running the check – upload evidence manually or through built-in templates to show that the compliance activity was completed. Evidence can also be provided as file uploads or links.

  • Marking as a special case – when a check is not applicable, it can be marked as a special case. This records the check as “Passing” for the cycle but flags it under special case records for auditors.

  • Submitting for review – if a reviewer is assigned, they validate the evidence and either approve, reject, or mark the check as a special case.

Example Workflow

  1. Configuration – An administrator sets up a quarterly Disaster Recovery check, assigning it to the IT team and enabling reviewer validation.

  2. Activation – On the scheduled date, the check status changes to Due.

  3. Evidence submission – The IT team uploads tabletop exercise notes using the built-in template.

  4. Review – The reviewer validates the submission and approves it.

  5. Completion – The check status is updated to Passing and recorded for audits.

Last updated