Archiving completed packages
2 min read
Updated Apr 9, 2026
Once a package is complete, the archive becomes the operational home for the record. It is where senders can retrieve artifacts, review package state, and hand finalized work into downstream systems.
Before you begin
At least one completed package
A plan for where finalized records belong after export
Clarity on who owns archive review in your team
Use Completed as the system archive
Completed surfaces the signed PDF, certificate, manifest, and audit actions together.
That route is designed for artifact review rather than sender follow-up.
Export what downstream systems need
Some teams only need the signed PDF, while others want the full artifact set plus audit exports.
Know what your legal, compliance, operations, or finance teams expect before you export.
Review archive hygiene regularly
Completed packages should be easy to understand by title, reference, and artifact availability.
Consistent naming and retention settings make the archive much easier to use over time.
Pro Tips
Treat Completed as the final operational checkpoint before long-term storage.
Store artifacts in a predictable pattern so later retrieval is fast.
Pair archive review with compliance export review if your team handles audits regularly.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.