Curate evidence instead of exporting a working folder
An analyst’s workspace may contain temporary files, credentials, raw datasets, and unrelated material. A customer evidence package should be a deliberate selection. The audit can reference an evidence identifier without exposing internal source paths or access tokens.
Use synthetic data while testing the packaging workflow. This article’s example does not contain real customer information and does not claim a completed professional audit.
A fictional evidence manifest
| ID | File | Purpose | Review |
|---|---|---|---|
| E01 | figures/demo-checkout.png | Illustrates finding F1. | Demo content only. |
| E02 | tables/sample-timings.csv | Explains the calculation example. | Synthetic rows, headers checked. |
| E03 | notes/method.txt | Defines example scope and limitations. | No private paths or credentials. |
For DEMO-498, the report refers to E01 and E02 rather than assuming the buyer will infer meaning from filenames. The manifest states which files are examples, observations, or methodological notes.
Build a customer package
Place the report and manifest at the top level, with supporting files in a small number of clearly named folders. Avoid including source projects or raw recordings unless the purchase specifically includes them and they have passed review.
- Check every manifest entry exists in the final package.
- Remove files that are not listed or intentionally included.
- Verify report references match evidence identifiers.
- Inspect metadata and visible content for unintended disclosures.
- Download and extract a fresh copy of the final archive.
- Open representative files and confirm all required ones are usable.
For a small package, inspect every file rather than relying on a sample. For larger evidence sets, define a review method before promising completeness.
Choose a maintained delivery route
QuickAttach support specifies uploads under 100 MB. If the archive is larger, an approved external destination may be appropriate, but its permissions and availability need separate testing. A folder link can expose extra files added later, so control what belongs in that destination.
Attach the approved package to the relevant order item and tell the buyer to start with the report and manifest. Record the package revision as a unit. If one evidence file changes, update the manifest and explain whether the report’s conclusions changed as well.
Deliver the right file with the right order
See how QuickAttach connects a customer-specific file or link to a Shopify order item.
See the QuickAttach order-to-download walkthrough