Skip to content

Compliance

Compliance proves every control holds, from the records the platform keeps as work happens.

Compliance proves every control holds, from Evidence the platform records as work happens.

Outcome

PartThis Process
OutcomeEvery Control has a current passing result, or an open Issue for its failure.
ReadsControl
LeavesIssue
Runs inEach Startup

Accountable

Legal Lead, Legal Team.

Workflows

WorkflowRunsTeam
Control testingevery dayLegal Team

Who does each step

Compliance: who does each step3 steps in 1 Workflow, across 1 Role: Compliance Officer. The table below lists every step.Compliance OfficerCorinWorkflowControl testing1 · Collection.queryQuery the records for each Control’s test.2 · Evidence.createRecord each result as Evidence againstthe published root.3 · Issue.createOpen an Issue for every Control without acurrent passing result.Compliance: who does each step3 steps in 1 Workflow, across 1 Role: Compliance Officer. The table below lists every step.WorkflowControl testingCompliance Officer1 · Collection.queryQuery the records for each Control’s test.Compliance Officer2 · Evidence.createRecord each result as Evidence against thepublished root.Compliance Officer3 · Issue.createOpen an Issue for every Control without a currentpassing result.
Each box is a step, numbered within its Workflow, with the Verb it calls, under the Role it runs as. The table below adds approvals.
WorkflowStepRoleCallsApproval
Control testing1. Query the records for each Control’s test.Compliance OfficerCollection.queryNone
Control testing2. Record each result as Evidence against the published root.Compliance OfficerEvidence.createNone
Control testing3. Open an Issue for every Control without a current passing result.Compliance OfficerIssue.createNone

Events

DirectionWhenWhat happens
InEvery dayStarts Control testing
OutCollection.queriedRaised by step 1 of Control testing
OutEvidence.createdRaised by step 2 of Control testing
OutIssue.createdRaised by step 3 of Control testing

Plays

No Play names this Process.

Controls

Settings

None.

Failure

A failed step retries; when retries run out, the Action goes to the Legal Lead.

Loop

No loop: the path is never randomized, because it serves Continuous control testing.

Code

Text
Turn on compliance

Enable

On by default for every Product Template. Process.pause stops new Actions; Actions in progress finish.

Example

A payroll-data API has 214 controls in scope, 190 of them inherited from its Studio. Control testing runs every night. It finds one control with no Evidence for last week and opens an Issue, closed the next morning.