Export

Why it matters

flowchart LR
    Record[Governed record] --> Export[Export]
    Export --> Share[Shared output]

Export explains how TrialStack turns governed records or workflow output into something that can be shared, reviewed elsewhere, or delivered downstream.

How it works

flowchart LR
    Request[Export request] --> Output[Output artifact]
    Output --> Source[Trace back to source]

Exports run through shared request flows so teams can track the request, understand what was produced, and keep the result tied back to the source record or workflow.

PDF and Word exports for document and evidence-pack content apply final-document styling: template placeholders are restyled into ordinary black text, non-citation brackets/braces/chevrons are removed, and protocol-style headings use the final export typeface and hierarchy. Submission-oriented exports also use one-inch Letter margins, centered Page x of y pagination, and undecorated single-line table grids so the PDF rendition stays aligned with the source artifact.

When to use it

flowchart TD
    Need[Need deliverable output] --> Export[Export]
    Edit[Need live editing] --> Stay[Stay in product]

This concept matters when the team needs a structured output artifact rather than another live edit inside the product.

What to watch for

flowchart LR
    Export[Export] --> Context[Keep context]
    Context --> Review[Review downstream]

Export should preserve context and traceability. It should not become a hidden side path where important output leaves the governed workflow without review.