Skip to content

Use case

Claim and evidence checks

Check that the statements in a report, disclosure or customer document are backed by your own source documents. Each claim gets the passage that supports it, or a plain statement that none was located.

Who runs it

Who this review is for

Compliance, sustainability and reporting teams who must show the evidence behind what their organisation says, before a report is published or a customer asks.

Requirements

Requirements you can run

You write each requirement in your own words. These are examples of the kind a reviewer runs.

  • “Show the evidence behind the statement that all packaging is recyclable.”
  • “Show the source for the reported year-on-year reduction in energy use.”
  • “Show the policy that supports the claim of annual supplier audits.”
  • “Show where the reported headcount figure comes from.”

Documents it typically reads

  • Annual and sustainability reports
  • Policies and procedures
  • Board and committee papers
  • Data exports (CSV, XLSX)
  • Audit reports
  • Customer questionnaires

How it runs

From upload to decision

  1. Step 1

    Upload the claims and the evidence

    The draft report or document making the statements, and the source documents that should support them.

  2. Step 2

    Turn each claim into a requirement

    Add one requirement per statement (“Show the evidence behind…”) to a programme for the report.

  3. Step 3

    Run it

    Each statement gets a finding: the supporting passage with its file and page or rows, a source that was cited but could not be confirmed, or no supporting evidence located.

  4. Step 4

    A named reviewer decides

    Each finding is confirmed, rejected or marked for follow-up by a person. The decision is attributed and logged, and the run exports as DOCX, XLSX, CSV or JSON with every finding, its sources and the decision.

Key to findings

…certificate valid until 2 March 2028…
Evidence located
A passage DataStruct could support against the requirement, shown with its file, page and section, or its sheet and rows.
…annual review completed…
Cited, not confirmed
A source the answer relied on that DataStruct could not confirm as support. Listed first, so the reviewer opens it first.
…the policy requires an annual test…
Related material
Returned by the search and not used as evidence. Kept apart so it never reads as proof.
[ no supporting passage ]
No supporting evidence located
Nothing in the set supports the requirement. The finding says so and names what is missing.
Confirmed · reviewer

Only a named person can confirm, reject or mark a finding for follow-up. The decision is attributed and logged. Green is theirs alone: no system state is ever shown in green.

The boundary

What it does not do

  • It does not assess whether a claim meets advertising, reporting or legal standards. It shows the evidence it found and says when none was located.
  • It does not detect contradictions between documents, or prefer the current version of a superseded record.
  • It can class related material as support, which is why every finding is reviewed by a person.

Questions

Common questions

Does it rewrite the claim?

No. It reports what supports the statement as written. Changing the statement is your decision.

What if the support is only partial?

A source that was cited but could not be confirmed as support is shown as such and listed first, so the reviewer opens it first. It is never presented as located evidence.

Try claim and evidence checks on your own documents

Book a demo and bring a sample of the documents this review runs on.