Exporting an evidence archive — a package you hand to an external auditor
"Give me your evidence" is an expected request from an external auditor or certification body. The "Export results" button in the library packages it for you.
What's exported is what you see
The export inherits your current filters. Filter "Incidents + last year" then export, and only that year's incident evidence comes out. No filters = all your evidence.
Know before you commit
When you press it, you first see a plan summary: how many files and what size. Then you confirm, or narrow the filters. And if the request is larger than your server can handle at that moment, you learn it immediately in a clear message with the filters still in front of you — no waiting then failing.
Preparation runs in the background
Don't wait at the screen: the export builds in the background and a notification reaches you when it's ready. Find it in the "Exports" tab with its status (queued / preparing / ready / failed).
A huge archive is split into several zip volumes, each downloadable on its own — so you don't wait for twenty gigabytes to finish before starting.
An archive stays downloadable for seven days, then it's swept automatically. Re-export whenever you like.
The manifest — the heart of the package
Inside every archive are two files carrying the same data:
manifest.xlsx— for the human. Open it in Excel and you'll find clickable links: one opens the subject in goiso, another opens the file itself from inside the package after extraction.manifest.csv— for machines, if the receiving side wants to parse it programmatically.
Every file × location gets a row: its fingerprint, name, size, upload date, caption, surface, its subject's title, both links, its path inside the archive, and its status.
A duplicate file appears once
A file filed in three places enters the archive once, and the three manifest rows point at it. A smaller package and a more honest manifest.
The status column
It tells you where each file's bytes are:
- "Included in this volume" — the file is here, and its link opens it.
- "In volume N" — the file is in another volume of the same package.
Those are the two states. If you ever see anything else, it's a signal of a fault on our side, not a gap in your archive — send it to us before you hand the package over.