Does an evidence file automatically prove a claim?

No. The organisation determines whether a source supports, contextualises or limits a claim, and the claim remains subject to its approval workflow.

What happens when an approved claim changes?

Hael opens a new draft revision. The previous approved version remains immutable and traceable.

EVIDENCE AND CLAIMS

Turn scattered proof into defensible AI claims.

Import policies, evaluations, certifications and governance records, then connect each source to the specific AI systems and organisation-approved claims it supports, contextualises or limits.

Create free profile Book a demo

Bring existing SOC 2, ISO and Vanta or Drata evidence into an AI-specific context.

Company-level evidence

SOC 2 · ISO 27001 · Policies · Vanta / Drata exports

AI systems

Customer Support Copilot · Fraud Signals · Demand Forecaster

Scoped claims

Human oversight · Data use · Evaluation cadence

Organisation approval

Reviewer decision · immutable record

Buyer-facing release

Assurance Link · Release No. 12

Evidence only matters when it is connected to what you say.

A SOC 2 report, ISO certificate or AI policy may demonstrate company-level controls. It does not automatically prove every statement about every AI system. Hael records where a source supports a claim, where it adds context and where its limitations must remain visible.

Bring proof into one governed source library.

Secure file import brings existing evidence into a single library that connects to the systems and claims it actually supports. Hael does not claim a live integration unless one is genuinely available.

Policies and standards

AI, security, privacy and operational policies with their approval history.

Evaluation and testing reports

Model evaluations, red-team results and internal testing outcomes.

Risk assessments

AI risk and impact assessments recorded alongside the systems they cover.

Governance records

Meeting decisions, reviewer approvals and change records.

SOC 2 and ISO outputs

Reports and certificates imported securely, connected to the AI-specific claims they support.

Incident and monitoring records

Incident logs and monitoring outputs preserved with their limitations.

Supporting, Context and Limitation are different relationships.

Supporting sources provide direct evidence for a claim. Context sources help a reviewer understand its background. Limitation sources record where the claim does not fully apply or where further review is required.

Claim

“Customer data is not used to train shared models.”

System · Northwind Customer Support Copilot

Customer Data Use Policy

Supporting

Customer Support Copilot record

Supporting

Organisation approved2 supporting sourcesLimitation noted

Context: Excludes preview features flagged for internal evaluation.

Approved claims remain controlled records.

Drafts can be revised. Approved claims are frozen with their source fingerprint and approval history. New evidence or wording creates a new draft revision rather than changing the approved record.

Reuse proof without duplicating it.

Hael detects existing imported evidence within the organisation and connects one canonical source to the relevant systems and claim revisions. This preserves provenance without creating duplicate records.

Answers to the questions buyers ask first.

Yes. You can securely import relevant reports and exports, then connect them to the AI systems and claims they support. Hael does not claim a live connector unless one is genuinely available.

Part of the Hael trust layer

One governed record across the entire assurance lifecycle.

Assurance Profiles, Evidence and Claims, Assurance Link, Questionnaires, Continuous Governance and Hael Counsel all work from the same systems, sources, scope and approvals.