2 min read
Updated Apr 11, 2026
The signed PDF is the primary completion artifact for most operational handoffs. Signelio creates it as an immutable asset derived from the source PDF plus collected field values and signatures.
A completed package
Access to the Completed route or the final signing completion view
A reason to export the final document
The Completed archive exposes the signed PDF alongside other generated artifacts.
That is the best place to start when you need the final document itself.
Use the signed PDF action from the archive row or the completion surface when it is available.
Keep the exported file alongside the related certificate and manifest if later review is likely.
The signed PDF is an immutable completion artifact, but it should not be described as cryptographically sealed or trust-service-backed beyond the current implementation.
Use accurate language when you hand it to downstream teams.
Download the signed PDF soon after completion if another system needs it.
Pair the PDF with the certificate and manifest in storage when evidence matters.
Use the audit trail export if the receiving team needs event-level review too.
Use this as a quick signal while the public knowledge base is static.