Decide under policy.
Prove it afterwards.

MeshQu checks decisions against your policy and records what supported them. See which rules applied, who had authority and what evidence was used.

See how it works Talk to us →

An accountable decision owner holding an evidence folio

More decisions. More to account for.

01Changing rules
Policies change.
You need to know which version applied at the time.
02Fragmented evidence
Evidence is scattered.
Checks and approvals sit across systems, documents and teams.
03Costly reconstruction
Questions arrive later.
Someone has to piece together what happened and why.

The accountability gap

What MeshQu does.

A person in silhouette — the accountability structure software lacks — With a recordYour team has a clear basis for the decision, and a record to return to when someone asks why.

01 · Policy

The policy that applied.

02 · Evidence and authority

The evidence and authority.

03 · Signed recordA record you can inspect.

Sealed

Reviewer: Amina Rahman
Rules: v12 · in force
Evidence: 3 policy checks · passed
Outcome: Reimburse

MeshQu does three things. It checks a decision against the policy that applies. It records the evidence and authority behind it. And it keeps a signed record that someone else can inspect later.

MeshQu never takes the underlying action.

Responsibility boundary

MeshQu checks the policy. Your system takes the action.

MeshQu assurance
MeshQu checks and records.
It assesses the information supplied against policy and records the result.
Your claims or payment system
Your workflow acts on the result.
It proceeds, requests review or stops, according to your process.

Use MeshQu alongside a workflow or before an action. Your application controls what happens next.

See the solution →

Authorised push payment (APP) fraud reimbursement

Must this customer be reimbursed?

Take a fraud reimbursement claim. MeshQu checks the information provided against the applicable policy and shows which requirements still need evidence or human review.

Illustrative research scenarioAPP reimbursement policy3 requirements unresolved

Not ready

Effective customer warning
Warning record returned from the customer journey
Evidence required
Receiving-bank response
Authoritative response received
Awaiting
Vulnerability assessment
Accountable specialist assessment recorded
Human review

Accountable decision owner reviewing a policy requirement

Agent case reviewHuman judgement required

Vulnerability assessment cannot be resolved automatically.

Amina RahmanAccountable decision owner

Authority confirmed

Human judgementAuthorise reimbursement

Policy basis and supporting evidence reviewed.

Decision basisHuman decision recorded

Authority, rationale and policy version preserved.

Human authority where it matters

When judgement is needed, a person makes the call.

MeshQu shows what the policy requires and what evidence is available. The authorised reviewer makes the judgement. Their decision and reasons become part of the record.

A requirement needs human judgement
The reviewer examines the evidence
The reviewer approves or declines
The decision and reasons are recorded

The human decision is recorded alongside its supporting assessments. MeshQu does not infer approval or judgement.

Evidence on demand

Show why the decision was made.

Return to the policy, checks and approval recorded for this claim.

Ask MeshQu · illustrative response

Why was this customer reimbursed?

Locating the claim record
Loading the policy in force
Checking the applicable requirements
Retrieving evidence and authority
Assembling the decision record

Recorded answer · verifiable basis

The recorded decision was to reimburse. The claim passed the policy checks, and the reviewer approved the outcome. The record identifies the policy version, supporting evidence and reviewer's reasons.

Evidence for external review

Hand over proof. Not a reconstruction project.

A Decision Receipt is a signed record of how a decision was made — the policy in force, the evidence and the authority — written at the moment it happens. A reviewer reads what was recorded.

External review package4 checks remaining

Reviewing

Policy in force: Evaluating
Supporting evidence: Queued
Accountable authority: Queued
Decision history: Queued

Signed authorised push payment (APP) fraud exampleInspect the decision recordOpen the identifiers, signing key and transparency record behind a synthetic fraud review.

Signed sandbox exampleAPP fraud review · payment released

This synthetic record captures an analyst-authorised payment release. It is not a reimbursement decision and contains no customer data.

How Decision Receipts work