Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
What Is an AI Audit Evidence Room?
Short answer
An AI audit evidence room is a single controlled space that holds all the evidence for one audit engagement: every artifact filed once, sealed with a SHA-256 hash the moment it arrives, badged with where it came from, and visible only to the owner and to an auditor the owner has granted access to that one room. It replaces the scattered folders, email attachments and shared-drive links that make audits slow and records hard to defend years later.
What is an AI audit evidence room?
An AI audit evidence room is a per-engagement repository for audit evidence. In AI Audit Exchange, a room is created for one of two regimes — California SB 1119 or a CPPA cybersecurity audit — for a stated audit period. Each artifact in the room carries its SHA-256 hash, its source, and its import date in the room manifest, and the room itself carries a retention period and an optional legal hold.
Why evidence needs a room of its own
An independent audit is, at its core, an examination of records. The auditor does not take your word for how a system behaved; they read the artifacts — the decision records, notices, safety evidence and conformity material your tools produced — and test whether those records support the claims your organisation makes. When that material lives in six places, owned by four people, in formats nobody agreed on, the audit spends its first weeks on archaeology instead of examination. A dedicated room removes that waste: one engagement, one room, one manifest that says exactly what was filed, when, and from which product it came.
What goes inside a room
A room holds the evidence produced by the systems that generate it. On this platform those products are ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock: their exports are imported read-only and unchanged, and each one is badged with its source product on its face. Anything else can be filed as a direct upload, badged honestly as a direct upload. The room does not generate evidence itself — it never creates notices, decision traces, crisis-runtime evidence, SBOMs or conformity packs. It hosts, seals and organises what those products produced, which keeps the line between producing evidence and preserving it clean.
How sealing and the manifest work
The moment an artifact is imported or uploaded, the platform computes its SHA-256 hash and stores the artifact immutably. The room manifest lists every artifact with its filename, source product, format, hash, size, import date and any retention note carried from the generating product. That manifest can be exported at any time, and any artifact's hash can be re-verified against the stored record — so if anyone later asks whether a file is the same file that was filed, the answer is a computation, not a recollection. See how SHA-256 evidence sealing works and what an evidence manifest is.
Who can see inside a room
Room contents are visible to the room owner and to nobody else by default. When an auditee accepts an auditor for an engagement, that acceptance grants the auditor read access to that one room only — not to the owner's other rooms, and not to anything else in the account. The grant is scoped and revocable: end it, and the auditor's access to the room ends with it. Every access is recorded in the room's access log, so the owner can see who looked at what. That scoping is what makes it safe to file complete evidence instead of the redacted subset people tend to share over email.
Retention and legal hold
Each room carries a retention period. On the free plan that is 12 months; paid plans can set retention up to 10 years per room, which matches the long record-keeping horizon California's audit regimes are built around. A room can also be placed on legal hold, and a hold blocks all deletion of that room — including through the owner path. Retention and hold are separate controls: retention says how long the record lives, hold says nobody may shorten that life while the hold stands. The difference matters and is covered in legal hold vs retention period.
Rooms, periods and the progress view
The working pattern is one room per audit, per period: a room is titled for its engagement, tagged with its regime (SB 1119 or CPPA) and its period, and filled as evidence is produced. Inside each room, a completeness view tracks the organisational steps — engagement posted, auditor matched, evidence filed, manifest exported, retention set beyond the default — and shows a simple progress count. It is labelled exactly what it is: an organisational checklist, not a legal determination. When the audit closes, the manifest export becomes the room's permanent table of contents. Open a free room and the pattern is visible in minutes.
Five actions to take
- Create one room per engagement and audit period, tagged with the correct regime — SB 1119 or CPPA.
- Import suite exports unchanged so each artifact keeps its source-product badge.
- File direct uploads only for material no suite product produced, and let them be badged as direct uploads.
- Export the room manifest once evidence is filed, and re-verify one artifact hash against it.
- Set the room's retention period deliberately — and place a legal hold on any room that must not be deleted.
Worked example
A fictional mid-size lender, Meridian Row Financial, prepares for its first CPPA cybersecurity audit covering the 2027 period. Its compliance lead opens one room for that engagement and imports 46 artifacts: decision-review exports from ReviewDesk, companion-safety evidence from CompanionGuard and provenance records from ProvenanceGuard. Each import is sealed on arrival; the manifest lists all 46 with hashes and source badges. Four supporting documents that no suite product produced are filed as direct uploads and badged that way, bringing the room to 50 artifacts.
When the independent auditor is matched and accepted, she receives read access to that room only. She works from the manifest, samples 12 artifacts, and re-verifies each hash against the stored record — 12 of 12 match. At close-out the lead exports the manifest, sets retention to 10 years, and the room's progress view reads 5 of 5 steps complete. Two years of email archaeology were replaced by one export the auditor could check herself.
Frequently asked questions
Is an evidence room the same as a shared drive folder?
No. A shared folder can be edited, renamed and deleted by anyone with access, and it keeps no trustworthy record of what a file was when it was filed. A room seals each artifact with a SHA-256 hash at intake, stores it immutably, badges its source, scopes access to one granted auditor, and keeps an exportable manifest of the whole set.
Does the room create the evidence for my audit?
No. AI Audit Exchange never generates notices, decision traces, crisis-runtime evidence, SBOMs or conformity evidence packs. Those are produced by ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock, and imported here unchanged.
Which audits is a room for?
Version 1 covers two California regimes only: SB 1119 audits and CPPA cybersecurity audits. Each room is tagged with one regime and one audit period.
Who can see the evidence in my room?
Only you, and an auditor you have accepted for that engagement — and that auditor sees that one room only, under a grant you can revoke at any time.
How long is evidence kept?
Free rooms carry 12-month retention. Paid plans allow retention up to 10 years per room, and a legal hold blocks all deletion of a held room for as long as the hold stands.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Next: California SB 1119 AI Audit: A Plain-Language Preparation Guide
CPPA Cybersecurity Audit: What the Certification Cycle Requires of Your Evidence · How to Prepare for an Independent AI Audit · AI Audit Evidence Checklist for California Engagements