Evidence Disclosure Standard (EDS) v1.0
A structured, repeatable framework for documenting AI use in legal proceedings, tribunal applications, and formal evidence contexts. Designed to help individuals and professionals meet the AI disclosure requirements now being mandated across Australian courts and tribunals.
Why this standard exists
Australian courts and tribunals are rapidly introducing mandatory AI disclosure requirements. The Fair Work Commission is mandating disclosure across all forms. NSW Practice Note SC Gen 23 requires disclosure in all affidavits and witness statements. South Australia, Queensland, and Victoria have all issued formal directions or guidelines.
These requirements tell people WHAT to disclose — but not HOW to systematically document and verify their AI-assisted work. The Evidence Disclosure Standard bridges that gap.
Version
1.0.0
Status
Active
Released
February 2026
Last Updated
March 2026
How EDS maps to FWC requirements
The FWC's proposed AI disclosure form requires applicants to verify facts, confirm case law, and include hyperlinks. Here is how each EDS component addresses these requirements.
| FWC Requirement | EDS Response |
|---|---|
| Disclose if you used GenAI | EDS Disclosure Statement Section 1 — AI Tools Used |
| All references to facts or evidence are correct and exist | EDS Evidence Log — records each AI interaction with verification status |
| All case law exists and stands for positions attributed | EDS Disclosure Statement Section 5 — Human Verification confirmation |
| Include hyperlinks to all case law | EDS Evidence Log — source/reference column for URLs and citations |
| Confirm you have checked all details | EDS Disclosure Statement Section 7 — Signed Declaration of accuracy and completeness |
Change Log
| Version | Date | Changes |
|---|---|---|
| 1.0.0 | February 2026 | Initial release: folder structure, naming convention, evidence log fields, integrity checklist |
Folder Structure
All AI disclosure materials should be organised in a consistent folder structure. This makes it easy for reviewers to locate and verify disclosure documents.
ai-disclosure/ ├── 01-disclosure-statement/ │ └── ai-disclosure-statement-[YYYY-MM-DD].pdf ├── 02-evidence-log/ │ └── ai-evidence-log-[YYYY-MM-DD].csv ├── 03-source-files/ │ ├── original/ │ │ └── [original documents before AI modification] │ └── ai-assisted/ │ └── [documents produced with AI assistance] ├── 04-ai-outputs/ │ └── [raw AI outputs, screenshots, exports] ├── 05-integrity-checklist/ │ └── ai-integrity-checklist-[YYYY-MM-DD].pdf └── README.txt
File Naming Convention
Consistent file naming ensures documents can be identified and ordered without ambiguity. Use the following pattern:
[type]-[description]-[YYYY-MM-DD]-[version].[ext]type — disclosure, log, source, output, checklist
description — brief, hyphenated description
date — YYYY-MM-DD format (ISO 8601)
version — v1, v2, v3 (increment on each revision)
Examples:
disclosure-statement-2025-03-15-v1.pdf
log-evidence-interactions-2025-03-15-v1.csv
source-medical-report-original-2025-03-10-v1.pdf
output-chatgpt-claim-summary-2025-03-14-v1.txt
checklist-integrity-2025-03-15-v1.pdf
Minimum Evidence Log Fields
Every AI interaction that contributes to evidentiary material should be recorded with at least the following fields:
| Field | Description | Example |
|---|---|---|
| Entry ID | Sequential identifier | 001 |
| Date | Date of interaction (YYYY-MM-DD) | 2025-03-14 |
| Time | Approximate time (24hr) | 14:30 |
| AI Tool | Name and version of AI tool | ChatGPT-4o |
| Purpose | Why the AI tool was used | Summarise medical report |
| Prompt Summary | Brief description of what was asked | Summarise key findings from Dr Smith report dated 10/03/2025 |
| Output Summary | Brief description of what was returned | 3-paragraph summary of diagnosis, treatment, prognosis |
| Modifications | Changes made to AI output | Corrected medication name, removed speculative prognosis |
| Used In | Which document/submission includes this output | Claim narrative, section 3 |
Evidence Index — Minimum Required Fields
Maintain an index of all exhibits and evidence items referenced in your disclosure:
| Field | Description | Example |
|---|---|---|
| Entry | Sequential entry number | 1 |
| Name | Exhibit name or filename | medical-report-dr-smith.pdf |
| Type | Document, Image, Audio, Video, Email, Spreadsheet, Other | Document |
| Description | Brief description of the exhibit | GP medical report dated 10/03/2025 |
| AI Assisted | Whether AI was used to create or modify | Yes |
| Date Added | Date exhibit was added to the index | 2025-03-14 |
Chain of Custody Log — Minimum Required Fields
Document the handling, transfer, and storage of all evidence materials:
| Field | Description | Example |
|---|---|---|
| Entry | Sequential entry number | 1 |
| Date | Date of custody action | 2025-03-14 |
| Time | Time of action (24hr) | 09:15 |
| Action | What was done | Received original document |
| Handler | Who performed the action | Jane Smith |
| From/To | Transfer details if applicable | Received from solicitor |
| Notes | Additional context | Original sealed envelope |
| Storage | Where item is stored | Secure cloud drive, folder 03 |
Integrity Checklist
Before finalising your disclosure, confirm each of the following:
All AI tools used in preparing evidentiary materials have been identified and documented.
Each AI interaction has been recorded in the evidence log with all minimum fields completed.
Original (pre-AI) versions of all documents have been preserved in the source files folder.
AI-generated outputs have been reviewed for factual accuracy and corrected where necessary.
All modifications to AI outputs have been documented in the evidence log.
The disclosure statement accurately reflects the scope and nature of AI use.
The folder structure follows the prescribed format and all files use the naming convention.
The completed disclosure package is ready to include with the evidence submission.
Start using EDS v1.0
Download the standard and begin documenting your AI use, or explore our scenario-specific disclosure packs.
This platform provides process documentation tools only. It does not provide legal advice, is not a substitute for professional legal counsel, and does not certify the truth or accuracy of any information disclosed. All outputs are for documentation purposes only.