Skip to main content

Explain the decision.
Without rebuilding the past.

Keep the policy version, supplied information and assessment bound together in a signed receipt, ready for later review.

See what a receipt records

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

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. Integrity and signature checks together let another party check whether the signed record has changed. Where export is enabled, an independent reviewer can check it with the necessary verification material and trusted keys, without access to MeshQu.

Several receipts can be linked to show the checks behind a larger decision, alongside the human reviews and final approval. Start with the policy your organisation has approved. MeshQu helps you turn it into clear rules, and each recorded assessment against them, whether by people, applications or AI agents, is tied to that policy version.

01 / Context

Which policy
applied?

See the policy version and the rules used for the assessment.

02 / Responsibility

Who did
what?

Follow who acted at each step, as recorded by your systems, with the reviews and rationale.

03 / Evidence

What supported
the result?

Find the information and evidence references used at each step.

Decision Receipts: what the record contains

A Decision Receipt is a signed, replayable record of how a consequential decision was made, created at the moment it happens and verifiable afterwards with the necessary verification material and trusted keys. It records the policy in force, relevant decision context, the outcome and integrity information needed to check later whether the signed record has changed. It does not prove that the inputs were true, that the decision was correct or that the action was carried out.

Machine-readable

Two records. Two different jobs.

An audit log records what a system did, in the order it happened. A Decision Receipt preserves the governed state of one decision, so its basis can be checked after the systems around it have changed.

Audit log

  • Which system or user acted, and when
  • Events in the order they happened
  • Kept by the system that wrote them
  • Read alongside that system and its configuration

Decision Receipt

  • The policy version and rules the decision was assessed against
  • The context supplied, with evidence references and digests
  • The actor identifier your systems supply
  • The outcome, with human reviews as linked records
  • Timestamp, integrity hashes and signature

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)

Follow the chain.
See the final call.

A decision is rarely one check. Linked receipts form a chain: the first assessment, the enhanced review it triggered, the exception that was made, the final call and what a later review found.

This separate fictional supplier onboarding variation explores a different outcome from the home page example. The supplier was sent for review because its tax registration certificate was missing, went ahead by exception and was reviewed again a year later.

Map a decision like this with QuHow decision chains work (opens in a new tab)How responsibility is recorded (opens in a new tab)

Illustrative supplier onboarding · fictional variation

  1. Initial review recordedSystem · Supplier Onboarding Policy v2
  2. Enhanced review requiredTax registration certificate missing
  3. Exception recordedProcurement analyst · Rationale recorded
  4. Final decision recordedJordan Davis · Procurement lead · Rationale recorded
  5. Periodic review linkedTwelve months later · certificate supplied, assessment run again

A question arrives

“Show us how this decision was reached.”

The evidence behind your answer

Policy at the time
Supplier Onboarding Policy · v2
Recorded assessments
Both assessments + the review trigger
Who decided and why
Who acted, and the rationale recorded
Supporting evidence
Linked to the record
Recorded authority
Role, as recorded by your systems

Illustrative decision record

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 verification works (opens in a new tab)

Ask why.
See patterns.

MeshQu keeps the history of the decisions you’ve recorded and the evidence behind them. Explore it in MeshQu, or ask questions through your own agent: which rules keep sending suppliers to review, where evidence is often missing, and which policy each decision was made under. Use what you learn to shape the next policy change.

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 checks that repeatedly fail.

Illustrative questions. What you can ask depends on what your deployment records. Qu, the assistant on this website, explains MeshQu and can help you scope a 30-minute mapping call. It cannot see your organisation’s records.

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

Protect the information.
Verify the decision record.

Keep source documents
with you.

MeshQu can link to evidence through references and digital fingerprints. Source documents stay with your team or custodian. The information you submit for a recorded assessment is stored with its result.

How evidence is bound to a decision (opens in a new tab)

The systems can change.
The proof must remain.

A receipt is tied to the policy version and context it was assessed against, not to the system that produced it. Where export is enabled for your deployment, the receipt and policy snapshot can be exported 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)

Bring one decision that matters.

We’ll show you how MeshQu can put policy, evidence and human judgement around it.

Book a demo (opens in a new tab)