Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Direct Upload vs Suite Import: How Evidence Provenance Works
Short answer
A suite import is evidence produced by a named product — ReviewDesk, CompanionGuard, ProvenanceGuard or CRAClock — imported read-only and unchanged. A direct upload is a file the auditee filed themselves. Rooms badge each artifact accordingly, and the manifest's source column shows the whole room's provenance at a glance. Auditors weigh the two streams differently, so keep them clean: never route a suite export through the upload path, and never dress a self-made file as a product's output.
What is evidence provenance?
Evidence provenance is the recorded origin of an artifact: which product produced it, or that it was uploaded directly. On AI Audit Exchange every artifact's manifest entry carries a source label — the producing product's name for imports, 'direct upload' for auditee-filed material — alongside its format, SHA-256 hash, size, import date and source retention note. Provenance is recorded at intake and never edited afterwards.
Two streams, two kinds of authority
A suite import speaks with its producing product's voice: the file is that product's own record of what it did — a decision review, a safety evaluation, a provenance record — generated by the system whose behaviour is under examination. A direct upload speaks with the auditee's voice: the organisation asserts this file belongs in the record. Both voices are legitimate; they are not interchangeable. An auditor tests product-generated evidence for what it shows about the system, and auditee-filed evidence for what it shows about the organisation's own processes. Blurring the streams would corrupt both tests, which is why the room keeps them visibly separate from intake to manifest.
How the badges work in practice
At intake the platform knows which path an artifact took, and records it permanently. Imports arrive through the import path from the producing products and are stored read-only and unchanged, sealed with their SHA-256 hash. Direct uploads arrive through the upload path on a room you own or operate as a guest, are likewise sealed, and are badged as direct uploads. The badge appears on the artifact's face in the room and as the source label in the manifest. Nobody edits badges afterwards — provenance recorded at intake is the only provenance that does not depend on someone's later memory of where a file came from.
What belongs in each stream
Suite imports: every export the four producing products generate for the period — ReviewDesk — ADMT Decision Review records and notices, CompanionGuard safety evidence, ProvenanceGuard provenance records, CRAClock conformity-timing material. Direct uploads: the genuinely human residue of an audit — signed approvals, internal attestations, correspondence records, a policy document as adopted on a stated date. A useful test for any file: did a suite product produce this as its own record? If yes, it must travel the import path, untouched. If no product produced it, it is a direct upload and should be proud of the badge, because the badge is what makes it trustworthy as what it is.
The failure modes to avoid
Three mistakes recur. First, the helpful edit: opening a suite export to fix a typo before importing — the file is now a derivative and its import is a small falsehood with a hash on it. Fix sources in the producing product and re-export. Second, the round-trip: downloading an import and re-uploading it, which converts product evidence into a direct upload and destroys its provenance for no benefit. Third, the impersonation: styling a self-made summary to look like a product export. Auditors find these, eventually, and a single provenance failure re-prices every other artifact in the room. The clean streams are not bureaucracy; they are the room's credit rating.
Reading the manifest's source column
The manifest turns provenance into a management tool. Filter the source column and coverage questions answer themselves: is every expected product represented this period, in plausible volume, spread across the months? What share of the room is direct uploads — a healthy minority of organisational documents, or a majority suggesting the suite products are not being exported at all? Those readings belong in the monthly room review beside hash sampling and freshness checks. A room whose provenance profile is understood by its owner never surprises its auditor; a room filed blind can surprise everyone. More on the manifest itself: what an evidence manifest is.
Provenance across retention and handover
Provenance outlives the engagement. The manifest travels with the room through its retention — up to 10 years on paid plans — so a reader in year eight can still see which product produced each artifact and when it entered the room. If the auditor changes, the successor reads the same badges and the same source column; the room's provenance does not live in the predecessor's head. And if a room goes on legal hold, its provenance record is part of what is preserved. Evidence systems earn trust slowly, through exactly this kind of boring continuity: every file, labelled as what it is, forever.
Five actions to take
- Route every suite product export through the import path, untouched, so it carries its product badge.
- File only genuinely auditee-produced material as direct uploads, and let the badge say so.
- Never edit an export before import — correct the source product and re-export a fresh artifact.
- Read the manifest's source column monthly: coverage by product, spread across the period, upload share sane.
- Keep provenance intact across handover: successors read the same badges and manifest you filed.
Worked example
A fictional childcare-platform company, Sunbeam Family Systems, reviews its room of 58 artifacts before engaging an auditor. The manifest's source column reads: ReviewDesk 21, CompanionGuard 14, ProvenanceGuard 12, CRAClock 4, direct uploads 7. The review spots one anomaly — a decision summary the team had exported from ReviewDesk, annotated in a document editor 'to add context', and uploaded directly. Its badge honestly says direct upload, but its contents impersonate a product record.
The fix follows the rule: the annotation is moved into the room's question-and-answer thread where commentary belongs, the original export is imported untouched through the import path, and the annotated copy is left in place as what it is — a direct upload — with the team noting the correction in the room. The auditor later samples both files, reads the story in the manifest and the thread, and moves on in minutes. Provenance handled honestly cost an afternoon; handled otherwise it would have cost the room's credibility.
Frequently asked questions
Is a direct upload weaker evidence than a suite import?
It is different evidence: it speaks with the auditee's voice rather than a producing product's. Signed approvals and attestations are properly direct uploads. What weakens evidence is mislabelled provenance, not the upload path itself.
Can I change an artifact's badge after filing?
No. Source is recorded at intake from the path the artifact actually took, and manifest entries are part of the sealed record. If a file was filed through the wrong path, file it correctly as a new artifact and let the record show the correction.
What if a suite product cannot export a needed record?
File what you have as a direct upload, badged honestly, and answer the auditor's questions about it in the room. An honest direct upload serves the audit; a dressed-up imitation damages it.
Do direct uploads get sealed too?
Yes. Every artifact, import or upload, is SHA-256 sealed at intake and listed in the manifest with its hash, size and import date. Sealing is universal; provenance is what differs.
How many direct uploads is too many?
There is no quota — the test is plausibility. Direct uploads should be the organisational residue (approvals, attestations, correspondence), while the system's own records arrive as imports. If uploads dominate, the suite exports are probably not being filed.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Import Evidence Into an Audit Room · Next: What Is an Evidence Completeness Checklist?
Stale Audit Evidence: The 365-Day Freshness Rule Explained · Auditor Questions and Answers Inside the Evidence Room · How Auditees and Auditors Share Evidence Securely