AI Audit Exchange
Go back

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

How to Import Evidence Into an Audit Room

What is evidence import?

Evidence import is the intake path by which an artifact enters an AI Audit Exchange room. Suite imports arrive from the producing products — ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock — and are held read-only and unchanged, hash-sealed at intake and badged with their source. Direct uploads are filed by the auditee and badged 'direct upload'. The Exchange never edits another product's records; retention notes are recorded from the generating product's policy.

The one rule that governs everything: import unchanged

Suite exports are evidence because they are the producing product's own record. The moment someone opens an export, tidies it, renames fields or merges two files 'to help', the artifact stops being that record and becomes a derivative — and its story in front of an auditor gets longer and weaker. The platform enforces the rule mechanically: imports are read-only and unchanged, sealed with a SHA-256 hash at intake, so any later copy can be checked against the sealed original. Your team's part of the rule is upstream: export from the producing product, import the export, touch nothing in between. If an export is wrong, fix it in the producing product and export again — a new artifact, sealed fresh, with the old one superseded honestly.

The workflow, step by step

Open the room for the right regime and period — importing into the wrong room is the commonest filing error, and it is why one room per period matters. Choose the import path for suite exports and select the export file as produced. Confirm the artifact lands in the manifest with its source badge, format, size, hash and import date. Repeat per product, per period. Then glance at the completeness view: 'evidence filed' is one of its five steps, satisfied by the room holding artifacts — but your real check is coverage: every expected product represented for every month of the period. The manifest's source column makes that check a one-minute read.

Direct uploads: for the evidence no product produced

Not everything auditable comes out of a suite product: a signed internal approval, a scanned attestation, a correspondence record. Those are filed as direct uploads, and the room badges them 'direct upload' on their face. The badge is not a stigma; it is provenance. An auditor reading the manifest can see at a glance which artifacts carry a producing product's authority and which the auditee filed directly, and weigh questions accordingly. What direct uploads must never do is impersonate: never re-upload a suite export as a direct upload to dodge a badge, and never edit a direct upload after filing — file a new version as a new artifact.

What the seal records at intake

At the moment of import the platform computes the artifact's SHA-256 hash and records, in the manifest: filename, source label, format name, hash, size in bytes, import timestamp, and the source retention note carried from the generating product's policy. That bundle is the artifact's birth certificate in the room. It is also why import timing matters: an export imported in the month it was produced has an import date that corroborates its story, while a year of exports imported in one December afternoon tells a different story — not a fatal one, but a story the auditor will ask about. File as you produce; the timestamps become a quiet witness in your favour.

Importing across periods without cross-contamination

Period discipline is the filing system's backbone. Each room serves one period; when a new period opens, open its room and import into it — never top up last period's room with this period's exports 'to keep things together'. Together is what the room list and the plan's room allowance are for: Pro covers 10 rooms for auditees, so periods accumulate side by side, each sealed, badged and manifested independently. Where an export genuinely spans periods — an annual summary produced in January covering December — file it in the room whose period it evidences and note the span in your filing log; the artifact's own dates speak inside the file.

After importing: the three quick checks

Close every import session with three checks that take under five minutes together. Coverage: read the manifest's source column — every expected product present for this round? Integrity: pick one just-imported artifact and re-verify its hash; a match confirms the intake sealed what you sent. Freshness posture: if you run validation, note any stale flags your new filings were meant to clear. Those three checks, repeated monthly, are the difference between a room that is filled and a room that is known to be filled — and only the second kind survives an auditor's first hour unchanged. The validation habit is covered in room security companions and in the freshness rule guide.

Five actions to take

  1. Export from the producing product and import the file untouched — fix errors in the product, then re-export.
  2. Import into the room matching the artifact's regime and period; one room per period, always.
  3. Use direct uploads only for material no suite product produced, and let them carry the direct-upload badge.
  4. Confirm each import in the manifest: source badge, format, size, hash and import date all present.
  5. Finish each session with coverage, one hash verification, and a freshness glance.

Worked example

A fictional property-technology firm, Ironwood Estates Software, builds its import rhythm over one quarter. January: 7 ReviewDesk exports and 4 CompanionGuard exports imported, 2 direct uploads (a signed approval and an attestation) — 13 artifacts, manifest checked, 1 hash sample verified. February: 9 imports. March: 11 imports plus a correction — a ProvenanceGuard export is found to have been generated from the wrong configuration, so the team fixes the configuration in ProvenanceGuard, re-exports, and imports the corrected file as a new artifact.

The manifest tells the whole story without commentary: 33 artifacts, import dates spread across the quarter, the corrected export present as its own sealed entry rather than a silent replacement. When the auditor later asks why two similar ProvenanceGuard files exist, the room answers — dates, sources and hashes — before the team has to. That is what 'import unchanged' buys in practice.

Frequently asked questions

Can I edit a suite export before importing it?

No — and the design assumes you will not. Imports are stored read-only and unchanged; editing first would make the artifact a derivative rather than the product's record. Fix the source in the producing product and re-export.

Which products' exports can be imported?

ReviewDesk — ADMT Decision Review, CompanionGuard, ProvenanceGuard and CRAClock. The Exchange never generates their evidence types; it imports them unchanged and badges each artifact with its source product.

What happens to an export's own retention policy?

It is recorded from the generating product's policy as a source retention note in the manifest. The Exchange records it; it does not edit another product's records or policies.

Is there a size limit on imports?

Uploads are capped at 10 MB per file on this platform. Oversize material should be exported in parts from the producing product, each part imported as its own artifact.

How do I know an import sealed correctly?

Open the manifest: the artifact appears with its sha256, size and import date. Re-verify the hash from the room — a match confirms the stored file is byte-identical to the sealed intake.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Running a 10-Year Retention Programme for AI Audit Records · Next: Direct Upload vs Suite Import: How Evidence Provenance Works

What Is an Evidence Completeness Checklist? · Stale Audit Evidence: The 365-Day Freshness Rule Explained · Auditor Questions and Answers Inside the Evidence Room