By team
The decision is half the job. The record is the other half.
Compliance work is judged twice: once when you make the call, and again when someone asks you to prove it. stepbase records who checked what, against which policy, with which document attached, at what time.
Nobody keeps the evidence where the decision was made
The check itself usually goes fine. The findings land in an email, the document sits in a shared drive folder named after a client, and the approval is a reply that says "ok to proceed". Six months later an auditor asks why this one was cleared and that one escalated, and the answer takes two people a day to assemble from three systems. Not because anything went wrong, but because the record was never a single thing.
Today
- A verification request arrives by email with the document attached
- The reviewer checks it against policy and writes findings into a reply
- The risk call is a judgement someone holds in their head, applied unevenly
- Escalation happens when the reviewer thinks to forward it to a senior
- Evidence ends up split across inboxes, a drive folder, and a tracker
- Reconstructing a decision means interviewing whoever handled it
On stepbase
- The request comes in on a form that requires the supporting document
- The reviewer records the policy outcome, a risk score, and their findings in structured fields
- The escalation threshold lives in the workflow, so every case is measured the same way
- Cases over the threshold route to senior review automatically, with a required comment
- Findings, documents, and decisions stay attached to the case they belong to
- The full trail is there on the record: who, what, when, which step, where it went next
How it works
- 1
Make the document part of the request
The intake form asks who or what is being verified, the type of check, and the supporting document. Required fields mean a case can't start half-documented.
- 2
Record the check, not just the verdict
The reviewer fills in a policy outcome, a risk score, and written findings. Those answers are saved against the stage that collected them, so it's always clear who supplied which piece of information.
- 3
Let the threshold decide the escalation
A condition block reads the recorded score: a failed policy outcome closes the case, a score of 70 or above escalates to senior compliance, everything else is approved. Change the number once and every future case follows the new rule.
- 4
Sign off with a reason on the record
Senior review ends on an approve or reject with a required comment, so the escalated cases carry an explanation rather than a bare outcome.
- 5
Reconstruct it whenever you're asked
Every action is timestamped and attributed, including who picked up a task from a team queue. An admin can open any case and read the whole chain end to end.
Start from a template
Every template is fully editable: change the stages, forms, and routing to match how you work.
FAQ