stepbase
← All templates

Form template · Compliance checks

Verification Requests

Use this template

Compliance checks with a risk score that decides who signs off.

Verification Request Form: what people fill in.

Request Details

The person or entity being verified.

PDF or image of the identity document, certificate, or attestation.

Anything the reviewer should know: deadlines, prior checks, exceptions.

Nothing is sent — see what happens on submit.

Risk routingEscalation paths

Scenario

Requests are checked against policy by compliance, scored for risk, and escalated to senior compliance when the score crosses the threshold.

How it works

Verification requests route on the risk score compliance records:

  1. Submit verification request: who or what is being verified, the type of check, and the supporting document
  2. Compliance verification: a reviewer checks the submission against policy and records a policy outcome, a risk score from 0 to 100, and their findings
  3. Policy & risk routing: a failed policy outcome closes the request, a score of 70 or above escalates it, everything else is approved
  4. Senior compliance review: escalated requests get a final approve or reject decision, with a required comment
  5. Verified or Rejected: every request ends on one of the two outcomes, with the findings and decision on the audit trail

    6. Who uses this

    • Identity verification
    • Document validation
    • Compliance attestations
    • KYC/AML checks

    Why stepbase

    Verification workflows need clear escalation paths and audit trails for regulatory compliance. The risk threshold lives in the flow, not in someone's head. Change the score that triggers escalation and every future request follows the new rule. Findings, decisions and comments stay on the record for auditors.

Start from the form, the stages, and the routing behind it.

Use this template