Serial Trail Serial Trail | Help Center

Export the compliance report

Generate and verify the checksummed ZIP containing a recall summary and frozen CSV ledgers.

Last updated: July 15, 2026

Contents
Show all sections (11) ▼

The compliance report packages a PDF summary and CSV ledgers into one checksummed ZIP. It is an operational evidence export, not a filing template or compliance certificate.

What you'll accomplish

  • Generate a durable snapshot of the recall case, units, contacts, waves, and audit evidence.
  • Download one archive with a recorded SHA-256 checksum.
  • Verify that the artifact opens and agrees with the case before sharing it.

Requirements

  • The recall must be activated; draft previews are not compliance evidence.
  • Report workers and private storage must be available.
  • You need permission to handle the contact data contained in the archive.
  • Choose an approved encrypted destination before downloading buyer information.

Generate and verify the archive

  1. Open the activated recall case.
  2. Find Compliance report and select Generate report.
  3. Wait until the status becomes Ready. Large cases are generated asynchronously.
  4. Record the displayed generation time and SHA-256 prefix in your case log.
  5. Select Open report and download the signed ZIP before the link expires.
  6. Open the archive and verify the PDF summary and CSV ledgers.
  7. Compare at least three unit rows, contact totals, wave totals, and case identifiers with the on-screen case.
  8. Store the archive according to your organization's retention and access policy.

What the archive contains

  • A human-readable PDF case summary.
  • Affected-unit and workflow ledger data.
  • Contact and outreach outcome data when present.
  • Case audit evidence and generation metadata.
  • A SHA-256 checksum recorded by Serial Trail for the generated file.

CSV cells are hardened against spreadsheet formula execution. The archive remains sensitive because it can contain buyer contact data.

What success looks like

  • The report status is Ready and shows a checksum.
  • The ZIP opens without repair warnings.
  • Expected PDF and CSV files are present.
  • Counts and sampled rows match the activated case snapshot.
  • The archive is stored outside shared or public folders.

Troubleshooting

Generation stays queued

Symptom: The report remains queued or generating.

Likely cause: The recall worker is unavailable or a renderer/storage dependency failed.

Fix: Check system status and worker health. Retry only after the failed run reaches a terminal state.

Confirm: A new run becomes Ready and exposes one download link and checksum.

Symptom: The download link no longer opens.

Likely cause: Signed download URLs are intentionally time-limited.

Fix: Return to the case and open the current report link or generate a new snapshot if the underlying evidence changed.

Confirm: The downloaded checksum matches the report shown in the case.

Spreadsheet software changes a value

Symptom: Long serials or timestamps appear reformatted.

Likely cause: The spreadsheet application inferred a number or date type.

Fix: Import the CSV with serial and reference columns set to text. Keep the original ZIP unchanged as evidence.

Confirm: The imported values match the raw CSV and the case ledger.

Responsibility and retention

The report supports internal review and regulator coordination, but it does not certify compliance or submit anything to an authority. Your organization controls access, retention, legal holds, regulator delivery, and secure deletion of downloaded artifacts.