Export Evidence for a Review

An evidence export is a file of decision events for a date range, as CSV or JSON, or as a compliance report. You hand it to an authorized reviewer, with a digest that proves the file is the one Verdictan produced.

These exports contain decision events only. Administrative changes come from Trail export, and History content and Inbox decisions are separate records.

Before you start

Know the organization, region, and dates that cover your test or incident, and have exports:read and exports:write. Start with a small date range, and store the file only where you are allowed to, because it contains operational metadata.

1. Request a CSV file

1. In the Console, open Trail → Evidence exports.
2. Set Start date and End date. Both days are included.
3. Choose CSV for a spreadsheet, or JSON for another application.
4. Select Request export job and note the job ID.

The export uses only these dates and the format. Filters from the Trail list, History, or Inbox do not apply.

Other export formats

Console format	CLI value	File contents
CSV	csv	Decision event rows
JSON	json	Structured decision event data
EU AI Act (AESIA)	compliance-aesia	JSON report in the AESIA structure
AEPD	compliance-aepd	JSON report in the AEPD assessment structure
ENS	compliance-ens	JSON report in the ENS structure
All compliance	compliance-all	.tar.gz bundle with the reports and manifest.json

A compliance report organizes evidence for a review. It does not prove compliance or replace a review of your application and controls.

2. Wait for completion

Status	Action
queued or processing	Wait. Do not create a duplicate.
completed	Select Download.
failed	Note the job ID and failure_message, and fix the reported problem.
expired	Request a new job with the same dates and format.

3. Examine the downloaded file

Open the file and check its dates, row count, and a few records against your review. If you have a known request ID, find it.

For the integrity check, read the completed job from a signed-in CLI session:

verdictan export-jobs get --job-id JOB_ID --json

Then compute the SHA-256 of your file and compare it with the job's integrity.artifact_sha256:

Linux

sha256sum evidence.csv

macOS

shasum -a 256 evidence.csv

PowerShell

(Get-FileHash .\evidence.csv -Algorithm SHA256).Hash.ToLower()

Matching values prove that your file is the recorded artifact. Compare with artifact_sha256, not manifest_sha256. For an All compliance bundle, also compare the archive with the inventory from GET /v1/exports/jobs/{job_id}/manifest.

4. Add a handoff note

Keep the file together with a short note:

Handoff note

Purpose and reviewer:
Organization and region:
Inclusive start and end dates:
Job ID and format:
Filename and verified SHA-256:
Relevant request/event IDs:
Finding and known gaps:
Storage location and next owner:

Link related Inbox decisions or Trail records separately. Leave out credentials and unrelated personal data.

Verify

The job is completed, the digest matches, and the file contains the records you need. A matching digest does not prove that you chose the right dates or organization.

Request and download from the CLI

Sign in with verdictan auth login, and use dates that contain your requests:

verdictan export-jobs create \
  --start-date 2026-09-01 \
  --end-date 2026-09-02 \
  --format csv --wait --json

Download with the returned job ID:

verdictan export-jobs download --job-id JOB_ID > evidence.csv

Use the same profile and region for every step. If --wait times out, the job can still finish on the server, so check its status before you create another.

verdictan export-jobs covers polling and timeouts.

If something fails

Problem	What to check
The file is empty	Organization, region, dates, and whether the gateway delivers decision events
Job not found	Use the profile and region that created it.
No download	The job must be completed and not expired.
The digest does not match	Download again and compare with the artifact digest of the same job. Record any mismatch.
An administrative change is missing	Use Trail export. Decision event exports never contain Trail records.

Next steps

• Reviewing Alerts and Evidence: connect the records to a conclusion.
• Trail and Audit Evidence: administrative changes.