AI Audit Exchange
Go back

Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

AI Audit Evidence Checklist for California Engagements

What is audit evidence completeness?

Audit evidence completeness is the state in which an evidence room holds the full set of artifacts for its engagement and period, each sealed and attributable, with the engagement's organisational steps done. AI Audit Exchange shows it as a five-entry view per room — engagement brief posted, auditor of record matched, evidence filed, manifest exported, retention set beyond the 12-month default — labelled as an organisational checklist, not a legal determination.

The five marks, and why they are the checklist's spine

Completeness has two halves: having the artifacts, and having done the organisational work around them. The room's progress view tracks the second half because it is the half humans forget. A room can hold 80 sealed artifacts and still be unready — no auditor matched, no manifest exported, retention still at the default that will delete the record before the next cycle asks for turning it. Work the five marks in order and the room's readiness stops being a matter of opinion: the view counts them, done over total, as a percentage anyone on the team can read.

The artifact layer: what should be filed

File what your systems produced for the period, from each producing system. Decision-review exports and notices from ReviewDesk — ADMT Decision Review; safety and guardrail evidence from CompanionGuard; provenance records from ProvenanceGuard; conformity-timing material from CRAClock. Each imports read-only and unchanged and is badged with its source product. Supporting material that no suite product produced — a signed internal approval, a scanned attestation — goes in as a direct upload and is badged as a direct upload, so the auditor never has to guess any file's provenance. The regime-specific lists are in SB 1119 evidence and CPPA evidence.

Sealing and badges: the integrity half of the checklist

An artifact that can be silently replaced is not evidence, it is a claim. Every artifact in a room is therefore SHA-256 sealed at the moment of intake and stored immutably, and the manifest records the hash beside the filename, source, format, size and import date. Checking integrity later is mechanical: re-verify the hash and compare. Source badges complete the picture — an artifact's face says whether a named suite product produced it or whether it arrived as a direct upload. When your checklist review reaches integrity, sample it: pick artifacts at random and verify, rather than trusting the count.

Freshness: the item most checklists miss

Completeness is not just presence; old evidence can be present and still fail the room. The validation run applies the platform's stated freshness rule — an artifact whose recorded date is more than 365 days before the run is flagged stale. For a cybersecurity-flavoured audit especially, a room full of last-cycle records demonstrates last cycle's practice. Put a validation run on the checklist itself: run it monthly during the period and always once before the auditor's start date, and treat every stale flag as a filing task with an owner and a date. See the freshness rule in full.

Access and questions belong on the checklist too

Two organisational items sit outside the five marks but decide whether the engagement runs smoothly. First, grants: exactly one accepted auditor of record per engagement, with read access to this room only, and no stale grants left over from earlier conversations. Second, the question channel: the auditor can raise questions inside the room and the auditee answers them there, so the exchange is retained with the evidence. Add both to your pre-engagement review — a room with perfect artifacts and a confused access list still costs the auditor their first week.

Close-out items that finish the record

The checklist ends after the auditor does. Export the final manifest and keep it with the room as its table of contents. Confirm retention — up to 10 years on paid plans — matches the record horizon your regime expects. Place a legal hold on any room under dispute, investigation or any other circumstance where deletion must be impossible; a hold blocks all deletion, including the owner's. Review and end grants that are no longer needed. A closed room should be boring: sealed, listed, retained, and readable by a stranger in nine years.

Five actions to take

  1. Work the five marks in order: engagement posted, auditor matched, evidence filed, manifest exported, retention set beyond 12 months.
  2. File every suite export for the period, unchanged and source-badged; badge direct uploads honestly as direct uploads.
  3. Sample-verify three artifact hashes against the manifest during every review.
  4. Run evidence validation before the auditor starts and clear stale flags with current-period filings.
  5. At close-out, export the manifest, confirm long retention, apply legal hold where deletion must be blocked, and end unneeded grants.

Worked example

A fictional insurance-services firm, Alder & Finch Processing, runs this checklist over its CPPA room for the 2028 period. The room holds 71 artifacts. The progress view shows 4 of 5: engagement posted, auditor matched, evidence filed and manifest exported are done; retention still sits at the 12-month default. The owner raises it to 10 years — a two-minute fix that would have silently destroyed the record's long-term value if missed.

The integrity sample verifies 3 of 3 chosen hashes. Validation flags 5 stale artifacts; 4 are replaced with current records and 1 is confirmed as a legitimately long-lived policy document, noted in the room. Grants review finds exactly one active grant — the auditor of record — and the question thread shows 9 questions, 9 answered. The checklist turns a vague feeling of readiness into eleven verified facts.

Frequently asked questions

Is the room's checklist a legal determination of compliance?

No. It is labelled an organisational checklist, not a legal determination. It tracks whether the engagement's organisational steps are done; what the law requires of your organisation is a question for your counsel and your auditor.

What counts as evidence filed?

At least one artifact in the room — but a useful room holds the period's full production: suite exports from ReviewDesk, CompanionGuard, ProvenanceGuard and CRAClock, imported unchanged, plus any direct uploads, each badged by source.

How do I check integrity during a review?

Pick artifacts at random, open the manifest, and re-verify each artifact's SHA-256 hash against the stored record. A match proves the file is the file that was sealed at intake.

What does the freshness part of the checklist involve?

Running the room's validation and reviewing stale flags — artifacts recorded more than 365 days before the validation run — then filing current-period replacements where the flag reflects genuinely old evidence.

When is retention 'set' for checklist purposes?

When the room's retention has been set beyond the 12-month default — paid plans allow up to 10 years per room. The checklist item exists because the default is easy to forget and expensive to discover late.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Prepare for an Independent AI Audit · Next: How Long Should You Keep AI Audit Records?

What Is a Legal Hold on Audit Evidence? · SHA-256 Evidence Sealing, Explained for Audit Teams · What Is an Audit Evidence Manifest?