AI Audit Exchange
Go back

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

How to Prepare for an Independent AI Audit

What is independent audit preparation?

Independent audit preparation is the work an auditee does before and during an audit so an external examiner can test the organisation's records: organising evidence by period, sealing it against later change, engaging an auditor at arm's length, and retaining the resulting record. On AI Audit Exchange that preparation lives in one evidence room per engagement, with a five-step completeness view — engagement posted, auditor matched, evidence filed, manifest exported, retention set — tracking the organisational work.

Start with the duty, not the documents

The first preparation step produces no files at all: establish, with your own counsel, whether an audit duty applies to your organisation, under which regime, and for which period. Platforms — this one included — make no legal determination about any customer's duties, and a room opened for the wrong regime or period is wasted work. Once the duty and period are clear, everything else is logistics. AI Audit Exchange supports two regimes, California SB 1119 and CPPA cybersecurity audits, and each room is tagged with exactly one of them, so the legal conversation and the filing structure stay aligned from day one.

Open the room when the period opens

A room created at the start of the audit period accumulates evidence at the speed the evidence is produced. A room created at the end becomes a reconstruction project. The mechanics are deliberately light: name the room for the engagement, set its regime and period, and note its retention setting. The free plan includes one room that runs with no sign-in, which is enough to learn the pattern on a rehearsal period; paid plans raise the allowance to 10 rooms on Pro and multi-client capacity on Team. Guidance on structuring rooms is in one room per audit period.

File evidence as it is produced

Your evidence already exists — it is the output of the tools around your AI systems. Decision records and notices, safety evidence, provenance records and conformity material are produced by ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock, and each export imports into the room read-only and unchanged, sealed with a SHA-256 hash at intake and badged with its source. Direct uploads cover the remainder and are badged as direct uploads. A monthly import habit keeps every artifact's sealed hash anchored to the file as it existed when it was produced, which is exactly what an auditor hopes to find.

Post the engagement, then grant access — in that order

Preparation includes the auditor's side of the table. Post an engagement brief tied to the room: what is being audited, which period, which regime. Vetted auditors respond; you review and accept one. Acceptance is the moment access exists — it grants that auditor read access to that one room, records them as the auditor of record, and the grant stays revocable for the life of the engagement. Reversing the order — sharing evidence widely while you look for an auditor — gives up the scoping that makes the exchange defensible. Writing a brief that gets good responses is covered in how to write an engagement brief.

Rehearse the auditor's first hour

Before the engagement starts, do what the auditor will do. Open the room, read the manifest, pick three artifacts at random and re-verify their hashes. Run the evidence validation and read its freshness flags — artifacts recorded more than 365 days before the run are flagged stale. Check the completeness view: engagement posted, auditor matched, evidence filed, manifest exported, retention set. Every gap you find in rehearsal is a gap the auditor does not find in the engagement, and most gaps at this stage are ten-minute fixes rather than ten-day ones.

Close out like the record will be read in ten years

Because it may be. The registry framework around these regimes is reported with 10-year audit-record retention, and paid plans allow per-room retention up to 10 years. Close-out is: final manifest exported, questions in the room answered, access grants reviewed and ended or renewed deliberately, retention confirmed, and a legal hold placed on any room whose deletion must be blocked outright. An audit that closes out cleanly makes the next audit cheaper — the next auditor inherits a structure instead of a story.

Five actions to take

  1. Confirm the duty, regime and period with your own counsel before opening anything.
  2. Open the room at the start of the period and import suite exports monthly, sealed at intake.
  3. Post the engagement brief early, accept a vetted auditor, and let acceptance create the scoped grant.
  4. Rehearse: verify three artifact hashes, run validation, and clear the completeness view to 5 of 5.
  5. Close out with an exported manifest, reviewed grants and retention set for the long term.

Worked example

A fictional logistics software firm, Harborline Systems, learns from counsel that its 2028 period will be its first audited one. The compliance owner opens the room in January 2028 and files monthly: by December the room holds 58 artifacts across the four suite sources plus 6 direct uploads. The engagement brief is posted in October; two vetted auditors respond; one is accepted in November and works under a room-only grant.

The owner's rehearsal in September catches the two real problems early: 4 artifacts flagged stale are replaced with current records, and the retention setting — still at the 12-month default — is raised to 10 years while there is time to think about it. When the auditor starts, her first sampling of 10 artifacts verifies 10 of 10 hashes, and the engagement's questions are all raised and answered inside the room. Preparation, spread over twelve months, never once required a weekend.

Frequently asked questions

How early should preparation start?

At the start of the audit period — the room and the monthly import habit are the preparation. Organisations that start at period-end are reconstructing evidence instead of filing it, and reconstruction is slower and weaker.

What does the free plan cover for preparation?

One evidence room with suite imports and direct uploads, the room manifest and 12-month retention — and the free room runs with no sign-in. It is enough to rehearse the full pattern on a practice period.

Who decides whether my organisation owes an audit?

Your own counsel. AI Audit Exchange makes no legal determination about any customer's audit duties and provides no legal advice; it provides the room, the matching and the retention once you know your position.

When does the auditor get access to the evidence?

Only after you accept them for the engagement. Acceptance grants read access to that one room, revocably, and records the match. Nothing is shared account-wide.

What should close-out include?

An exported manifest, all in-room questions answered, grants reviewed, retention confirmed for the long term, and a legal hold on any room that must not be deleted.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: CPPA Cybersecurity Audit: What the Certification Cycle Requires of Your Evidence · Next: AI Audit Evidence Checklist for California Engagements

How Long Should You Keep AI Audit Records? · What Is a Legal Hold on Audit Evidence? · SHA-256 Evidence Sealing, Explained for Audit Teams