Create a compliance export

Compliance exports are temporary CSV or ZIP files built from a snapshot of source records. Export generation runs in the background, so you can keep working while it completes.

Before you start

Open your organisation → Quality → Exports.

You need the correct export permission (history read, create, cancel, download, trail).

Roles with full export access are usually owners, administrators, and quality managers. Decide scope and sensitivity first: date range, site, equipment status, evidence type.

Export types

Type	Includes
Equipment compliance register (CSV)	Current equipment, assignments, requirements, due status, open investigations, latest approved calibration context
Calibration history (CSV)	Event history, structured measurement evidence, certificate metadata
Out-of-tolerance history (CSV)	Investigation flow, disposition, assignee, timestamps, corrective actions, current status
Equipment evidence pack (ZIP)	For selected equipment: procedures, executions, measurements, uncertainty, conformity, evidence, checksums

For ZIP-only workflows that need the full evidence selection, use Generate an equipment evidence pack.

Requesting an export

Select export type.
Enter date range if needed.
Select a site and equipment status filter.
For calibration history, include non-final work only when needed.
Click Request export.

You will see Export requested and the job appears in Export history. The server freezes filters and IDs at request time. Later data changes are not included in that job.

Track progress

Refresh Export history to check state:

State	Meaning	What you can do
`pending`	Waiting for worker	You can Cancel (if allowed).
`processing`	Build is running	Wait and refresh.
`completed`	Ready to download	Use Download (if allowed).
`failed`	Build failed with safe code	Fix source data and request again.
`cancelled`	Cancelled before start	You can request again.
`expired`	Download window passed	Request a fresh export.

processing jobs are recoverable after worker interruption; only one completed artifact is accepted. Temporary internal attempts do not replace successful request history and are reconciled automatically after a safety grace period. The history list is paginated.

Download and retention

Confirm completed status and check requester, times, row count, file size, and expiry.
Click Download.
Store the file per your evidence handling policy.

Exports are always authenticated through Metra.

Generated files are available by default for 7 days.
Expiry removes the generated file and marks job expired.
Source records, job metadata, checksums, and audit history remain.
A new request starts a new snapshot; it does not restore old expired artifacts.

Fixing failures

Read displayed failure code.
For date range errors, correct the range and retry.
For calibration history, decide whether non-final work is really needed.
For evidence packs, fix missing or invalid certificate integrity first.

Do not submit the same failing request repeatedly without understanding why.

Expected end result

You should get a private CSV/ZIP from a frozen snapshot, while Metra history keeps request metadata, status, and checksums.

Next steps

Traceability references

Evidence packets can include fixed reference-standard evidence, usage, traceability chain, and hashes. Use this with Reference standards in ISO 17025 dossiers.