2 min read
Updated Apr 13, 2026
Drafts are meant to be resumable. Reopening a prepared package preserves context, keeps sender work together, and reduces the chance of fragmenting the same process across several versions.
A draft that has already been created
A reason to continue rather than replace the package
Clarity on whether the original PDF and recipients are still correct
Existing drafts reopen through the same wizard tree used for new documents.
That means you can resume metadata, recipients, and delivery choices without rebuilding the package from scratch.
Before resuming, confirm the source PDF, recipient list, and delivery assumptions are still valid.
If the document changed materially, consider whether a new package is cleaner.
When you return to an older draft, use the review step carefully rather than assuming earlier choices are still right.
That is especially important if reminder, expiration, or routing expectations have changed.
Rename stale drafts before you resume them so teammates know they were intentionally reactivated.
If a draft sat for a long time, recheck the recipient list carefully.
Resume existing drafts whenever the workflow continuity matters.
Use this as a quick signal while the public knowledge base is static.