AI audit evidenceCompliance teams, product owners, risk leaders, public-sector teams, legal teams, AI governance staff, and organisations using AI in high-stakes workflows.12 min
Audit evidence checklist
Use this checklist before allowing AI, automation, scoring, recommendation, classification, ranking, triage, or decision-support systems to affect regulated or high-stakes decisions.
The issue is not whether AI is present. The issue is whether the organisation can later show what the system did, what data it used, who approved it, how humans reviewed it, how errors were challenged, and what evidence survives after the decision.
Primary questionCan you evidence how AI affected the decision, who remained accountable, and how the outcome can be challenged?
- Sections
- 6
- Checks
- 18
- Critical
- 8
- Level
- Advanced
Use checklistAuthorship evidenceWriters, creators, researchers, designers, agencies, and anyone sharing unpublished work.8 min
Authorship evidence checklist
Use this checklist before sending, uploading, pitching, submitting, or sharing a draft with another person or platform.
The aim is simple: keep evidence that the work existed in your possession before wider access, feedback, publication, or dispute. This does not prove every legal issue by itself, but it strengthens the evidential position before control starts to spread.
Primary questionCan you show that this draft existed, in your control, before you shared it?
- Sections
- 5
- Checks
- 14
- Critical
- 3
- Level
- Essential
Use checklistDispute-ready evidenceCreators, founders, agencies, researchers, publishers, product teams, legal teams, and organisations that may later need to defend a digital claim.11 min
Dispute-ready evidence checklist
Use this checklist before there is a dispute, complaint, challenge, takedown, authorship conflict, customer claim, regulatory question, or evidence request.
Dispute evidence is usually weakest when it is assembled after the problem appears. This checklist helps preserve the source, timing, custody, context, communications, and claim boundary before pressure begins.
Primary questionIf this were challenged later, could you show what happened without relying on memory, screenshots, or platform trust?
- Sections
- 6
- Checks
- 18
- Critical
- 7
- Level
- Essential
Use checklistEvidence readinessCreators, publishers, agencies, researchers, founders, product teams, and anyone making work public.10 min
Evidence readiness checklist
Use this checklist before making a work, file, article, dataset, media item, report, design, model output, or public claim available online or externally.
Publication changes the evidence position. Once something is public, copied, scraped, embedded, quoted, modified, or indexed, it becomes harder to separate the original record from later circulation. This checklist helps preserve the evidence trail before public exposure.
Primary questionCan you show what existed before publication, what was published, and how the published version connects to the original?
- Sections
- 5
- Checks
- 15
- Critical
- 3
- Level
- Essential
Use checklistVerificationCreators, founders, teams, reviewers, lawyers, compliance staff, and anyone relying on a timestamp as evidence.9 min
Verification checklist
Use this checklist before relying on a timestamp as proof that a file, claim, record, draft, dataset, media item, or decision existed at a particular time.
A timestamp can be useful, but weak timestamps are often overtrusted. The question is not whether a date appears somewhere. The question is whether that date is connected to the exact object, produced by a trustworthy process, preserved against later manipulation, and verifiable by someone else.
Primary questionDoes this timestamp actually prove what you are about to claim it proves?
- Sections
- 5
- Checks
- 15
- Critical
- 6
- Level
- Essential
Use checklist
