Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
What Is an Audit Evidence Manifest?
Short answer
An audit evidence manifest is the structured list of everything in an evidence room: for each artifact, its filename, the product that produced it, its format, its SHA-256 hash, its size, when it was imported and any retention note from its source — headed by the room's own identity: its regime, period, retention months and legal-hold status. Auditors start from the manifest because it lets them sample, verify and navigate the room without rummaging through it.
What is an audit evidence manifest?
An audit evidence manifest is the exportable inventory of an evidence room on AI Audit Exchange. Its room block records the room's public identifier, title, regime and regime label, period, retention months, legal-hold flag and the export timestamp. Its artifact entries record filename, source label, format name, sha256, size in bytes, import timestamp and source retention note — the complete provenance of every file, in one document.
Why auditors ask for the manifest first
An auditor arriving at 200 files needs a map before they need the files. The manifest is that map: it says what the room claims to contain, in a form that can be read in minutes and tested in an afternoon. Sampling becomes rational — choose entries across sources, periods and formats, then verify. Coverage questions become answerable — filter by source product and a gap in one product's filings is visible at a glance. And the room's own administrative facts — which regime, which period, how long retained, whether held — are stated on the face of the same document, so the examination starts from facts the room itself asserts and can be held to.
The room block: identity before inventory
Every manifest opens with the room itself: its public identifier, its title, its regime stored as its code and shown with its label — California SB 1119 or CPPA cybersecurity audit — the audit period it serves, its retention in months, whether a legal hold is in force, and the moment this export was generated. That header does more work than it appears to. It binds the inventory to one engagement, so a manifest excerpt can never drift into a different audit's file unnoticed, and it records the room's preservation state at export time — retention and hold included — which is exactly what a later reader needs to judge the record. See legal hold for the hold flag's meaning.
The artifact entries: provenance in seven fields
Each artifact entry carries seven facts: filename, source label, format name, sha256, size in bytes, imported-at timestamp, and the source retention note the generating product attached. Read across a row and you know what the file is, who produced it, what it is made of, how to verify it, how big the original was, when it entered the room, and what its producer said about keeping it. Read down a column and you can audit the room itself: all sources represented? import dates spread across the period or bunched at its end? Every field earns its place, and the discipline of the format is that no field is decorative.
Source labels and the honesty of badges
The source label is where the manifest keeps the room honest. Suite imports carry their producing product's name — ReviewDesk, CompanionGuard, ProvenanceGuard, CRAClock — because those products generated the evidence and the room received it unchanged. Direct uploads carry their own label, saying plainly that the auditee filed this file themselves. An auditor weighing evidence cares about that difference, and a manifest that blurred it would be worse than none. When you review your own manifest, the source column is the first coverage check: each expected producer should appear, in plausible volume, across the period.
Exporting: when and how often
The manifest can be exported at any time, and exporting is one of the five steps in the room's completeness view — a room whose manifest has never been exported is flagged by its own progress tracker as unfinished business. Practically: export after each major filing round, export at the rehearsal before the auditor starts, and export at close-out as the record's final table of contents. Exports are timestamped, so keeping the close-out export with the engagement file gives later readers the exact inventory the auditor worked from. The export step in context is covered in how to export a room manifest.
Reading a manifest like an auditor
Try the auditor's three passes over your own export. Pass one, coverage: does every expected source appear, for every month of the period? Pass two, integrity: choose three entries at random, re-verify their hashes, and confirm size and import date make sense. Pass three, administration: regime and period correct, retention set for the long term, hold status as expected, export fresh. A room that survives its owner's three passes will rarely surprise its auditor — and the passes take under an hour even for a large room, because the manifest does the organising work that folders never could.
Five actions to take
- Export the manifest after every major filing round, not just at the end.
- Read the source column for coverage: every producing product present, spread across the period.
- Sample three entries and re-verify their hashes against the stored artifacts.
- Check the room block: regime, period, retention months and hold status all as intended.
- File the close-out export with the engagement record as its permanent table of contents.
Worked example
A fictional device-software company, Pinnacle Loop Systems, exports its SB 1119 room manifest at rehearsal. The room block reads: regime California SB 1119, period 2028, retention 120 months, legal hold false, export timestamped that morning. The inventory lists 83 artifacts: 31 from ReviewDesk, 22 from CompanionGuard, 19 from ProvenanceGuard, 6 from CRAClock and 5 direct uploads.
Pass one immediately earns its keep: CRAClock's 6 entries all landed in a single month, revealing that its exports had been batched by hand instead of filed as produced — a habit the team fixes for the next period in one conversation. Pass two verifies 3 of 3 sampled hashes. The manifest turned a vague rehearsal into two findings, one fix and a verified sample, before the auditor had seen a single file.
Frequently asked questions
What format is the manifest?
A structured export generated by the room: a room block (identifier, title, regime, period, retention months, legal-hold flag, export timestamp) followed by one entry per artifact with its seven provenance fields.
Does exporting a manifest change the room?
Exporting records the export on the room — it is one of the five completeness steps — and produces the document. It does not alter any artifact; artifacts are immutable from intake.
Can the auditor get the manifest without full room access?
The manifest is the room's export, available to the owner and within the engagement's access. In practice the owner exports it for the auditor, or the auditor works it inside the room under their scoped grant.
What is a source retention note?
A note carried from the generating product's own retention policy, recorded at import. The Exchange records it from the producing product; it never edits another product's records or their notes.
Why does the export carry a timestamp?
So a reader can tell which inventory they are holding. Rooms keep growing during a period; the close-out export, kept with the engagement file, is the inventory the audit concluded on.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: SHA-256 Evidence Sealing, Explained for Audit Teams · Next: How to Choose an Independent AI Auditor
How to Become a Vetted AI Auditor on AI Audit Exchange · How to Write an AI Audit Engagement Brief That Gets Good Responses · Scoped Auditor Access: How Room-Only Grants Work