Generate the package
- Open Reports and choose Audit packages.
- Select the project and project-wide or batch scope. Select the batch if using a batch scope.
- Choose the retention period for the generated evidence package.
- Decide whether to include raw JSON and whether to redact personal identifiers.
- Choose Generate audit package, then wait for the generation job to complete.
- Open the completed package, review its file list and hashes, and choose Download ZIP.
What is inside
The ZIP bundles available project, scan, planning, governance, execution, and exception evidence for its selected scope. A manifest records the included files and their SHA-256 hashes so a retained copy can be checked for changes.
An audit package records the available evidence at generation time. It does not rerun every recipient acceptance test or guarantee that permissions remain unchanged afterward.
Choose redaction and retention deliberately
- Redaction replaces supported personal identifiers with stable pseudonyms within the package. The original identity mapping is not included.
- Raw JSON provides more detail and should be included only when needed by the intended reviewer.
- Review exported files before distributing them, especially where free text or paths may contain sensitive business information.
- Package retention is separate from licensing. A plan's unused credits do not expire merely because an evidence package has a retention date.
If a download expires
A download action creates a short-lived, read-only link, normally valid for 15 minutes. Return to the completed retained package and choose Download ZIP again to obtain a fresh link.
The package itself must still be available within its retention period. A deleted or expired package may need to be generated again from the evidence still held by the service.