Roles & workflow

One workflow, clear roles, and a record of who did what.

Vetting touches several people: someone asks, someone sets the rules, someone decides the hard cases, someone is accountable. Traustis gives each of them their own starting point and keeps the lines between them.

The workflow

From request to recorded decision

  1. A request arrivesFrom a teammate in the console, or from the counterparty through the portal.
  2. The right policy is chosenBased on what the counterparty is to you and where it is registered, using rules your owner set.
  3. Evidence is gathered and checkedEach check goes to sources that can answer it for that country. Results become findings with their source attached.
  4. A decision, or a case for a personClear results are decided by the policy. Anything borderline goes to the right review queue with a target time.
  5. The record is keptThe decision, the evidence, the person and the policy version stay together on the case.

Roles

Each role sees its own job first

Permissions decide what someone can reach. The home screen decides what they see first — three numbers that matter to that role, and the actions waiting on them.

Owner

Is vetting working, and is it worth it?

  • Chooses which policy applies to each kind of counterparty
  • Invites people and assigns roles
  • Manages the plan and sees spend
  • Home shows: spend this month, checks run, counterparties held back

Admin

Keep the setup right and the team unblocked

  • Edits and publishes policies — every publish is logged with who and when
  • Sets up review queues, targets and routing
  • Configures the counterparty portal
  • Previews the console as any role before inviting someone

Reviewer

Keep the queue clear and decide consistently

  • Works a board ordered by what needs them now
  • Claims cases, requests documents, records decisions with a reason
  • Cannot decide a check they submitted themselves
  • Sees their own pass rate next to the team's — calibration, not a leaderboard

Requester

Get a counterparty checked and move on

  • Starts a check with name, country and intent
  • Gets a decision straight away or a case sent to review
  • Finds every past result for a company before asking again
  • Can invite the counterparty to confirm their details

Viewer

Read and export, nothing more

  • Sees every decision and its evidence
  • Exports reports for finance, audit or a customer
  • Cannot run checks, so adding oversight costs nothing

The counterparty

Confirm who they are, once

  • Receives a link, no account needed
  • Confirms details as they appear on the official register
  • Uploads the documents you asked for
  • Everything lands on the case for the reviewer

Guardrails

Controls that keep the process honest

Separation of duties

A reviewer cannot pick up a check they submitted. The person chasing the deal is not the one who approves it.

No accidental lock-outs

Nobody can change their own role, and the last owner cannot be removed. Only an owner can create another owner.

Attribution that sticks

Every check records who ran it, every decision who made it, and every policy change who published it, in an audit trail that cannot be edited.

Set-up

Settings that read like questions, not tabs

An owner does not need a manual. Settings are grouped by the question they answer, each area says what to do next, and a built-in Guide reads your actual set-up and shows what is done and what is still waiting.

  • Checks — how is a counterparty checked?
  • Your lists — who do you already know about?
  • People — who does the work?
  • Workspace — how does it look, and what does it cost?

Watch each role at work

Short walkthroughs show the console from the owner's, admin's, reviewer's and requester's point of view.