Skip to main content

MeshQu Decision Receipts

See how the
decision was reached.

See which policy applied, who decided and what supported the outcome. Keep the record ready for review.

Explore a decision ↓Talk to us

The challenge

More decisions.
Evidence everywhere.

Automation increases the number of decisions an organisation makes. The evidence behind them can still be scattered across systems, documents and people.

When someone asks why, your team has to piece the answer together.

As automation scales

Illustrative growth · Not measured data

The complete picture

What a Decision Receipt
records.

Each recorded policy assessment has a Decision Receipt (opens in a new tab). It links the result to the exact policy version and information used. Its digital signature lets another party check whether the signed record has changed.

Several receipts can be linked to show the checks behind a larger decision, alongside the human reviews and final approval. Start with a policy your organisation has approved, then use its requirements to assess decisions made by people, applications or AI agents.

01 / Context

Which policy
applied?

See the version and requirements used for the assessment.

02 / Responsibility

Who did
what?

Follow the recorded roles, reviews and approvals.

03 / Evidence

What supported
the result?

Find the information and evidence references used at each step.

Works with what you have

Keep your systems.
Add assurance.

MeshQu works with your existing workflows. Use it alongside a process to assess and record decisions, or ask for a policy check before an action proceeds. In both cases, your system controls the action.

01 / Sidecar

Alongside your workflow

Your process continues as usual. MeshQu assesses the decisions you send it and records the results.

Assurance beside the decision.

02 / In the decision path

Before an action

Your application asks MeshQu for a policy result. It then proceeds, requests review or stops according to your workflow.

A check in the hot path. Your system enforces the result.

Read the integration guide (opens in a new tab)

01 / Follow the decision

Follow the checks.
See the final call.

A payment, approval or exception can depend on several checks. Linked records show what passed, what needed review and who made the final call.

Here, an expense exceeds the policy threshold. A reviewer considers the exception before an approver makes the final decision.

How decision chains work (opens in a new tab)How responsibility is recorded (opens in a new tab)

Illustrative expense exception

  1. Evidence linkedSystem · Supporting documents linked
  2. Review requiredPolicy v3 · Amount above threshold
  3. Exception reviewedAlex Lee · Finance reviewer · Rationale recorded
  4. Final approval recordedFinance approver · Supporting steps linked

A question arrives

“Show us how this decision was reached.”

The evidence behind your answer

Policy at the time
Expense policy · v3
Recorded assessments
Checks + review trigger
Who decided and why
Approver + rationale
Supporting evidence
Linked to each step
Recorded authority
Finance approval role

Illustrative decision record

02 / Ready for scrutiny

Have the evidence ready
when the questions come.

When a regulator, ombudsman or auditor asks about a decision, start with its record: the policy, checks, evidence and people involved.

Spend less time chasing documents and colleagues, and more time explaining the case.

How evidence can be independently verified (opens in a new tab)

Decision intelligence

See how policy works
in the real world.

Trace recorded decisions back to the policy that governed them. Look across those decisions to see where the policy needs attention. Teams get a clearer basis for action. The board gets evidence of how policy is working.

01 / Policy in practice

How is policy
being applied?

See which rules allow a decision, reject it or require review.

02 / Blocks & reviews

What keeps needing
review?

Find recurring triggers and the reasons recorded for exceptions.

03 / Gaps to address

Where are
the gaps?

Look for missing evidence, unclear responsibility and requirements that repeatedly go unmet.

Use what happens in practice to inform the next policy change.

Observe policy on real decisions (opens in a new tab)How policy changes are governed (opens in a new tab)

Privacy, protection & proof

Protect the information.
Verify the decision record.

Let another party
check the record.

Export the receipt and policy snapshot for offline verification. With independently trusted signing keys, a reviewer can check the signed record and supporting proofs without access to the live MeshQu dashboard.

What a verification bundle contains (opens in a new tab)
What does verification prove?

Verification checks the signed record and its supporting proofs. It does not establish that the original evidence was true or the decision was correct. Policy replay checks the assessment against the recorded policy and information; it does not explain an AI model's internal reasoning.

Read the full trust model (opens in a new tab)

Start with a decision that matters.

Bring one workflow and the policy behind it. See how MeshQu could connect its checks, approvals and evidence.

Talk to us