Skip to content

Superadjust launches June 15

SuperadjustSuperadjust

Archived evidence explained

What archiving means and how exported evidence stays protected in the audit trail.

By Superadjust Team

Exporting & ReportingAll guides

What this guide covers

  • when evidence becomes archived
  • what changes after a ZIP export succeeds
  • what archiving does not do
  • how to trace archived entries through export records

This guide explains what archived evidence means in Superadjust after you generate an evidence pack. It matters because archived entries are still retained, traceable, and part of the export record — they are not deleted from the system.

Important: This guide refers to the main ZIP export flow. The backend documentation confirms that evidence is marked as archived after a successful ZIP pack is created. Single-student shortcut PDFs are separate from that stored ZIP pack workflow.

Step 1: Know when evidence becomes archived

Evidence is marked as archived only after the main evidence pack finishes building successfully. In the backend flow, that happens after the ZIP file is generated, uploaded, and saved as a ready export record.

  1. 1.Generate the main ZIP evidence pack, not just a direct single-student PDF shortcut.
  2. 2.Wait until the export finishes successfully and reaches a ready state.
  3. 3.Understand that the archival step happens after the pack is finalised, not before.
1

Export initiated

ZIP pack generation starts

2

Pack builds successfully

PDFs, attachments, manifest created

3

Evidence archived

Entries tagged with export metadata

Archive Metadata

Status

archived: true

Timestamp

2026-03-15T14:34:00Z

Export Pack ID

EXP-2026-00147

Evidence is archived after the ZIP export completes successfully

Step 2: Understand what archiving changes

Archiving adds export metadata to the included evidence rows. The backend marks each matched entry with archive fields so the system can trace which export pack included it and when that happened.

  1. 1.The evidence row is tagged as archived.
  2. 2.The system stores the archive timestamp.
  3. 3.The export pack ID is attached so the archived entry can be traced back to the pack that included it.

Step 3: Know what archiving does not do

Archived evidence stays in the database. It is metadata archiving, not deletion. That means the evidence remains part of the record and still sits inside a larger audit trail that includes the export history, manifest, and pack hash.

  1. 1.It does not remove the evidence from the database.
  2. 2.It does not erase the export history.
  3. 3.It does not break the trace between the evidence and the pack it was exported in.

Archived evidence helps keep export packs defensible. The system does not just download files and forget them. It records what was exported, when it was exported, and which evidence entries were included, so later reviews have a clear audit trail.

Archived vs deleted

Use this table to understand the difference between archived and deleted evidence.

Archived evidenceDeleted evidence
Still stored in the database
Removed from the database
Linked to an export pack through archive metadata
No export trace unless stored elsewhere
Part of the audit trail
No audit trail available

Step 4: Use export records to trace archived entries

When you need to review archived evidence later, start with the export record and then move to the pack contents. The summary report, manifest, and history metadata help explain which students, dates, and evidence rows were included at export time.

  1. 1.Open the export history to find the relevant pack.
  2. 2.Check the reporting window, student count, and evidence count.
  3. 3.Use the summary report or manifest to confirm what was included in that export.

Common mistake

Archiving is not deletion: The most common mistake is assuming archived evidence has been deleted or hidden permanently. In Superadjust, archived means the entry has been included in a generated pack and tagged with export metadata.

What to do next

After reviewing archived evidence, the next useful step is to open the summary report for pack-level context or open a student PDF for per-student detail. If you need to verify pack integrity, read the audit hash next.